The A2A Simulations Community

Just for the record because it's certainly easily fixable. Will search, but didn't find yet the missing whatever (font) somewhere.



Stock P3D v5 HF1 installation, with the new A2A v5 installer.

Hello,

this is a P3D issue and Lockheed are aware of the issue. Its due to v5 on your system for whatever reason setting you to have the wrong setting in one of your cfg so any aircraft default or add-on requiring a certain setting for the cockpit will display as crazy as you are seeing there.

Its still worth you posting on the P3D support forums to let the p3d team know.

The manual fix in the meantime;

viewtopic.php?f=108&t=70238#p534103

thanks,
Lewis

Lewis - A2A wrote: ↑07 May 2020, 10:53 Its due to v5 on your system for whatever reason setting you to have the wrong setting in one of your cfg so any aircraft default or add-on requiring a certain setting for the cockpit will display as crazy as you are seeing there.

Whaou, it sounds weird and mysterious. "One" of my cfg aircraft (AI included ?)... a certain setting (?)... The hunt just started from one post to another

Lewis - A2A wrote: ↑07 May 2020, 10:53 The manual fix in the meantime;

viewtopic.php?f=108&t=70238#p534103

Thank you !

Back in this thread. To solve the problem, I had to edit my c:\users\XXXX\AppData\Roaming\Lockheed Martin\Prepar3D v5\Prepar3D.cfg and set "COCKPIT_HIGH_LOD=1" (was originaly set to 0). Don't know what can be the side effect of this.

If you remember from the FSX days the high detail cockpit on or off setting. This was removed from P3D settings menu and always set to ON, but is kept in the sim itself just not used. For some reason v5 is setting some users PC back to high detail cockpit OFF, which is what that cfg thing is doing.

cheers,
Lewis

Thank you for the precision. I just hope the setting is not reset by itself.

You'll probably find the setting resets if you set P3Dv5 back to it's default graphics settings Vincent. However, we're not sure which (if any) other settings changes will prompt this property to change. As mentioned in the other topic, Lockheed Martin are aware of the issue so hopefully they'll be able to fix it with a future update.

Thanks,
Nick