error in P3d.cfg file

[skip d]

I'm really perplexed why the P3D Forum won't let me in.

 To Log-in (which I know I had registered) ,I thought their answer to my question could be solved....because THEY developed the thing !!!

So...I'm hoping to get an answer here....since I know there are a LOT of you guys that know a LOT !!

I'm using Win10 and flying P3Dv5.4

Just about every time I sign on to P3D....my P3d.cfg file has automatically changed.

Under the first topic[JobScheduler]

**Location=-20000,-20000,-18058,-18898,\\.\DISPLAY1    and

**LocationFullScreen=-20000,-20000,-18058,-18898,\\.\DISPLAY1....appear

This .cfg causes my sim to 'go to black screen' after start-up.

After a re-build the NEW .cfg file looks like this

**Location=439,115,1481,909,\\.\DISPLAY1  and

**LocationFullScreen=0,0,1920,1080,\\.\DISPLAY1   

This .cfg works !!!

Why does it keep reverting ???

Thanks for any help !!

Skip d

 

[G-RFRY]

The FullScreen=0,0,1920,1080,\\.\DISPLAY1 . Tells me you are running at 1080p on your monitor which works. The other one will never work in the DISPLAY1 mine reads 2160p as I have a 4K Monitor.

The sim will detect your monitor and show 1 off three possible cfg 1K 1080p 2K 1440p 4K 2160p.

Edited February 20 by G-RFRY

[JonP01]

I have seen this happen if the desktop resolution at the time P3D is launched is different to the resolution selected within P3D itself. The config you show that is working would be the one that should work if the desktop and P3D are both at 1080p. Are you using some settings that cause the desktop to run at a different resolution at the time P3D is launched (with the config file that works)? This can happen if you are using those Nvidia features that use re-scaling.

Apart from that, as a temporary workaround you could setup the config file they way you like it (and you know works) then right-click in Explorer to make it read-only. That way it won't change the next time you launch. However that doesn't solve the problem. There must be something happening that causes P3D to totally misread the resolution between the time you are opening it then shutting it down.

[skip d]

Thanks Ray and Jon...I think?? my monitor is 1080.

I copied the 'old.cfg' and then re-built a new one,and am slowly replacing each tweak I had previously,then

running the sim to see if a tweak is the culprit. Skip d

[G-RFRY]

3 hours ago, skip d said:

Thanks Ray and Jon...I think?? my monitor is 1080.

I copied the 'old.cfg' and then re-built a new one,and am slowly replacing each tweak I had previously,then

running the sim to see if a tweak is the culprit. Skip d

Be carefully not to over tweak the cfg file, the sliders in the sim are themselves tweaks to how the sim displays and runs. And could cause conflicts between the two making the sim unstable. And your scenery addons may also be affected.

[JonP01]

There are also two checkboxes beneath the resolution drop down box that (for almost every user) should remain checked (always) especially when you are troubleshooting something like this. They control the following two values in the config file:

FullScreenBackground=True
FullScreenAutoFill=True

I'm not even exactly sure what the original reason was for LM to introduce the functionality controlled by these variables but when I was experimenting myself last year I noticed that if, for example, I unchecked the box such that FullScreenAutoFill was False, every single time I would run P3D, the screen area would progressively become smaller and smaller and the DISPLAY1 values would correspondingly change. I suspect it probably has something to do with Windows 10 / 11 full screen optimisations and windowed gaming, etc. Bottom line though - for 99% of people (I suspect) if these two values do not remain true (so both checkboxes in the interface checked), all sorts of display related havoc can be unleashed. Or to put it another way, you would only change those values (uncheck one or both of those checkboxes) if you had a specific reason to do so and knew precisely the consequences. 

[JonP01]

One other thing I can recall which has played havoc with DISPLAY1 parameters. And that is if you have any recording software / image capture software running concurrently (intentionally or coincidentally). It usually works fine since obviously simmers make videos all the time but I can recall users in the past complaining about their p3d config files changing the display parameters unexpectantly and the reason was that the resolution settings of the camera / image capture software and or hardware did not match the resolution set for P3D.

[skip d]

Thanks for all the valuable assistance Jon....

I have checked my .cfg changed a few items you suggested....and so far

things are stable now !!!!

I hope they stay that way.

Thanks again !

Skip d

[G-RFRY]

Do you have Addon Organizer I recommend it, once you have a stable working P3D you can create a backup and save. This allows you to roll back to stable working P3D if you add something and it goes wrong.

[vonmar]

This problem was later posed in the P3D forum on Feb 26, 2025:
https://prepar3d.com/forum/viewtopic.php?p=280863#p280863

So, looks like the problem is not resolved.

However the OP has not yet provide requested troubleshooting information on the P3D forum.

Edited March 4 by vonmar