Followed the instructions in Elaine's sticky for a Client Only update.

1. Rebooted after uninstall 3.1 client.
2. disabled antivirus
3. installed client
4. ran V3.2....opened and re-registered, no issues.
5. Open the app, no planes in vehicle window...its just black window where they should display, cursor spinning. app dead.
6. exited, rebooted...NOW....desktop icon nor the .exe in the folder run the app...just see it blip in task manager, then gone.  Running as administrator. 
7. Rebooted, rinse/lather/repeat.  Refuses to open...no errors.

Thoughts and or suggestions?

 

Interesting....

In doing my own additional troubleshooting, I took out some questionable .dlls iin the dll.xml file...no effect.

Then renamed prepar3d.cfg to .old to let it rebuild it.

It did create a new one...but its a zero byte file with nothing in it...like it never got to the point where it could recreate one....

 

The plot thickens, and moving closer to a total wipe and reinstall (the very last option though)

Next steps:

• Deleted shader cache, no change
• Did a content and scenery install (with proper reboots)...no change
• Banged head against desk, and while it made me feel better, it didn't help my "click P3d icon...hourglass for 7 secs, P3d.exe blips on task manager, then poof..nothing"

 

Almost ready for total uninstall/reinstall....but fearful its an external issue that is causing it and going through that will not resolve the issue.

try deleting the prepar3d.cfg file and letting it rebuild.

 

Locate the dll.xml file and disable all entries - add them back one by one

 

see if that helps. Also locate the default.fxml file and delete it.

 

 

Vic

try deleting the prepar3d.cfg file and letting it rebuild.

 

Locate the dll.xml file and disable all entries - add them back one by one

 

see if that helps. Also locate the default.fxml file and delete it.

 

 

Vic

Hey Vic,

Tried deleting the prepard3d.cfg, it creates a zero-byte prepard3d.cfg file in its place, and doesnt open the app.  So I took the original one I had and restored it.

Did the .dll tango....deleted suspect entries, nope, then all entries, same, then delete whole file....recreated one on startup...no joy.

 

Could not locate either a default.fxml or default.xml file....any hints to where it may be hiding?

Could not locate either a default.fxml or default.xml file....any hints to where it may be hiding?

 

There located at the same spot as your Shaders folder 

 

► Computer ► Local Disk (C:) ► Users ► your user name ► AppData ► Local ► Lockheed Martin ► PreparD v3 

There located at the same spot as your Shaders folder 

 

► Computer ► Local Disk (C:) ► Users ► your user name ► AppData ► Local ► Lockheed Martin ► PreparD v3 

Got it...renamed...it did create a new one...but still no joy. 

Missed that you already tried that Steve.

 

Sounds to me like the install got munged somehow. You could try a repair install or you might uninstall and reinstall the client.

 

Getting any error messages in the event viewer?

 

Vic

 

 

Did the .dll tango....deleted suspect entries, nope, then all entries, same, then delete whole file....recreated one on startup...no joy.

 

The dll.xml does not get rebuilt if you delete it or rebuild it.  The o byte P3d.cfg is probably the one that is built when you have an error in P3D.  If P3D does not start up to the startup screen, 99.9% chance it's the dll.xml as all of the modules in this file have to be loaded.  There are several in the dll.xml you had installed for v3.1 that are not compatible with 3.2.  FSDT replaced their module, the Orbx/FTX module does not work, and the ASN modules do not work.  So, that will stop P3D from loading.  Move your dll.xml and exe.xml to a temporary folder and restart P3D (if you still have the .xml files as you indicated you deleted them above but then they were rebuilt which is not possible.  Only the P3D.cfg and scenery.cfg can be rebuilt.

 

Best regards,

Ugh....the "marked as resolved" deletes the text you were typing when you hit it.

 

Anyway.....

 

Looked in the event viewer Vic....It was the file FSLPreloader.dll that was causing the issue.

Yep I have (had) FSL lights installed.  Uninstalled....works perfectly now!

 

Jim I misspoke.  I renamed the dll.xml file in addition to removing entries in the file itself one at a time to see if I could find the culprit.  When it didn't work I whacked my working file and pulled the re-named dll.xml file back in.

 

Heading of the FSL's site now to make sure they know about it in case other customers are pulling their hair out as well.  :smile:

 

Thanks for pitching in guys (and gal) with the suggestions...even with 30 years of troubleshooting experience, you will never see every nuance of an issue that you'll never figure out without some other heads to bang against yours. :im Not Worthy: 

 

I've never had to go to the event log in the past (believe it or not) as I've been pretty lucky in the past to not have many issues with upgrades, installs, etc. 

Hehe, 2nd topic down in the FSL Spotlights forum...same issue, same resolution.

Lefteris suggested the new version just released today....will try it and let both this and their forum know.

 

 

Thanks again folks!