Just updated to 5.3 from 5.2.  Decided to uninstall the whole thing instead of just doing the client and content.  Now it seems that Prepar3d starts but with nothing showing on the screen. I can hear sound and it shows that it's running in Task Manager but only see my desktop.  The only thing I've tried so far is letting the prepar3d.cfg rebuild.  Didn't work.  Any help would be appreciated.

 

Steve Giblin

2 minutes ago, StewCal said:

Just updated to 5.3 from 5.2.  Decided to uninstall the whole thing instead of just doing the client and content.  Now it seems that Prepar3d starts but with nothing showing on the screen. I can hear sound and it shows that it's running in Task Manager but only see my desktop.  The only thing I've tried so far is letting the prepar3d.cfg rebuild.  Didn't work.  Any help would be appreciated.

 

Steve Giblin

Mine did the same thing, I restarted and all back to normal.

Tried restarting several times....No luck yet.

Are you getting a black screen? I've had the issue a couple of times since V4, and have usually managed to fix it by switching between full screen & windowed a few times

8 minutes ago, SimeonWilbury said:

Are you getting a black screen? I've had the issue a couple of times since V4, and have usually managed to fix it by switching between full screen & windowed a few times

Nope, just the desktop.

 

STeve

 

Hello Steve,

Had the same problem. I solved it by taking away some of the addons folder in the documents/Prepare3DV5 addons folder that are not yet compatible with version 3. Putting aside FSlabs did the trick for me and P3D launched normally.

Yann

Hi,

For me, I noticed it happened immediately after the FSLABS non-compatibility error during startup. 

I uninstalled FSLABS, restarted sim and all ok. 

Will reinstall after compatibility is restored.

Thanos

PS. For some unknown reason the upper left information text is red again although the information.html file has text defined white.

Same for me as what Hoshou and Thanos68 reported.  I moved the FSLabs folder out of the V5 Add-Ons folder and that solved the problem.

Thanks guys!  Got the same answer over at the Lockheed Martin forum.  I'll give it a try when I get back from work.

 

Steve

That did the trick!

Use FSLabs with experimental channel until they release their update on the public channel. The new update fixed this issue for me.