Vehicle initialization has failed....

Not if you reinstalled your content. you need to open up FTX, let it initialize, and set your insertion points.
Sue

Sue,

Apologies for my confusion, but what do you mean by set my insertion points? Since I migrated my FSS purchases over to FTX Central, I needed to download and reinstall all my library over the course of a few days and very long downloads. However, when I started FTX Central after the Global and Regional installs (as I had done before FTX Central appeared..), there was no mention of insertion points of any sort of initialization, sans the regular P3D menu doing it's changes. Does that make sense? Did I miss a step perhaps?
 
Yes - and a very important one.

Nick Cooper


  • Orbx Team
  • Administrators
  • team_admin.png
  • 1,316
  • 15,876 posts
  • Location: York, UK
  • Order #:N/A


Posted Sunday at 01:29 AM


Go to the FTX Central settings page and using the insertion point tool,
set your FTX and OLC icons like this and click on Save.

Untitled.jpg
 
Yes - and a very important one.

Nick Cooper


  • Orbx Team
  • Administrators
  • team_admin.png
  • 1,316
  • 15,876 posts
  • Location: York, UK
  • Order #:N/A


Posted Sunday at 01:29 AM


Go to the FTX Central settings page and using the insertion point tool,
set your FTX and OLC icons like this and click on Save.

Untitled.jpg

Ahhhh, I get your meaning now....yes, indeed I performed that function as I was selecting to install each of the add on's. Sorry for the confusion, I thought you meant something else.

I have ordered a 2 TB SSD HD, as per GMan's suggestion, to dedicate specifically to P3D and all of it's scenery. I have also figured out a way to connect directly to my router and achieve much higher download speeds, should I need to reload any Orbx files again. Once the SSD arrives, I will post an update. Also, I will post a pic of my terrain outside of KTCM (McChord) in the PNW Orbx region, to see if maybe I am just being too harsh a critic of what it should look like.

Thanks all for your suggestions thus far. One thing I have always admired about SOH is their community is extremely helpful.
 
So, wanted to delete the F22 Raptor from the directory, as it's not a very good model and didn't need an abundance of hangar queens residing in my HDD. I stared P3D a few times after installing all addons for now, without a hiccup. I then got the following message:
"Vehicle initialization has failed for: F-22 Raptor - 525th Fighter Squadron. You will now be placed in visualization only mode."

Hello

I see your sorted now.

This specific error In your case by deleting the default Raptor would Indeed give you this Issue as the simobjects.cfg file would be trying to call this plane and not getting a response as you had deleted it from the root folder. By running a repair on the Prepar3D v4 Content (Control Panel) or the Install_Content.msi this action would and did return the default Raptor for you.

If you had (for example) deleted the default Raptor and not understanding what you had done, then you tried to manually edit the simobjetcs.cfg file only to realize that repairing the Content componont does in fact return the default Raptor again, At this stage you would have to undo the edit you made to the simobjects.cfg file or you would have the same error again only this time the situation would be visa vera, A raptor in place but a wrong simobjects.cfg entry. You could also just delete this file and let Prepar3D generate a default file when launched next, Once of course the default Raptor was back in the root folder.

-------------------

For other folks reading this......

With Prepar3D v3, Mostly the "Visualization mode error" was caused by either a corrupt simobjects.cfg or a corrupt VehicleFavorites.xml file. The simobjects.cfg file can of course be manually repaired if you know how but really its just simpler and quicker to delete this generated file and launch Prepar3D and test. The VehicleFavorites.xml file is not there by default and will only generate when you save your first vehicle, this file can also cause this error and can be repaired by deleting it and Launch Prepar3D and test

With the release of Prepar3D v4 this is also the same but some Users reported a similar error "No preview" on the Scenario page when Installing non compatible Add On's into the core Prepar3D v4 folder, Some users resolved this by repairing the Content component, others resolved by uninstalling and reinstalling the Content

------------------------

On the basis that it is just a corrupt simobjects.cfg or a corrupt VehicleFavorites.xml file here is a Short Video of repairing this error in motion

Also if you look at the Video description and click SHOW MORE, You will see details on how to locate these files quickly
 
Back
Top