hschuit

Sparkrite, thanks for your advice, I have been aware of the settings you mentioned, tried different values but that did not improve things much. Anyway, I deleted v6 last year, nowadays I mainly use DCS and sometimes MSFS 2024. Thanks, Henk.

I had the same problem, it was caused by interfering Thrustmaster TWCS hat switch bindings. Once I removed these camera bindings from the TWCS, the problem was solved.

I tried v6 and went back to v5.4 because v6 HDR cannot be disabled. The v6 world looks gloomy / brownish as if I am looking through sunglasses, v5.4 with HDR disabled looks much better for me.

You can make the P3Dv2 library scenery.cfg use your FSX scenery addon folders, it is simply a matter of putting in the folder paths. There are a few caviats like older FSX afcad taxiways not showing in P3Dv2 (which can be fixed with ADE) and FS9 scenery objects which work in FSX but do not display in P3Dv2. I have my addon scenery on a separate drive, FSX and P3D are on another drive, sharing the same addon scenery, no duplicates needed.

If you predominantly fly in the UK, you don't need a vector add on because your Orbx FTX EU England/Scotland already includes custom mesh, land class and vector data. If you want more accurate lakes, shorelines, streets, highways, train lines, power lines, streams etc. in the rest of Europe you need to turn on your vector add on.

Does not look like a duplicate, 1 appears to be an airport afcad, the other a traffic file, different beasts, best to be left alone.

You will find that same typo in the old FSX SDK - "Terrain SDK" > "Scenery Configuration File" chapter. The QMID level 4 numbering really is Col-Row, the same numbering is used for the FSX/P3D base scenery folders: 0000-0007, 0101-0107 etc. The FSX SDK explains it correctly in the "Terrain and Scenery" chapter: "The first two numbers refer to the column of data (from 00 to 11) and the second two to the row of data (from 00 to 07). So 0000 contains the default information for the top left hand rectangle in the diagram below, and 1107 the information for the bottom right hand rectangle."

Are you sure you run P3D as administrator? You need to run P3D as administrator, otherwise the FSRecorder menu entry will not show. BTW: I just tested it with the latest hot fix (2.5.12946.0) and it still works.

Removing the [JOBSCHEDULER] and FIBER_FRAME_TIME_FRACTION=0.1 tweaks did solve the blurries for me (I use Orbx FTX England).

Wishful thinking : FTX EU Germany B)

.\Texture\AirportParkingSpace.dds

Go to Menu bar: Options > Settings > General. Then check the "Progam - Use system time for Default Flight" flag. EDIT: Admins please delete this reply - Penz was quicker. B)

Not for most users. FSX/P3D do not need Physics and most if not all modern mainboards have on-board sound chips so you do not need the NVidia GPU sound driver.

To avoid this service getting installed again next time if you run an NVidia Geforce driver update installer, make sure you only select the NVidia driver only option. Do not select these bloatware items: 3D Vision driver/controller; Nvidia update, GeForce experience, Physics.

If you have your mouse pointer "snap-to" setting enabled, the Nvidia CP listboxes do not work. Go to the Windows Control Panel -> Mouse -> Pointer Options and un-check "snap-to".

This has been discussed in several other threads, summarizing: - Only the older FS Recorder v1.331 works in P3Dv2.5 - You need to have the legacy FSX-SP1 SimConnect installed - You need to run P3D as administrator

I prefer fps locked at 30 and vsync/triple buffering disabled (btw, you must use an Aero desktop theme). But if you want unlimited, then adaptive vsync is your best option. And: Forget about 1/2 refresh rate, that only works in full screen exclusive mode (FSX).

In P3Dv2 I believe vsynch is only needed when fps is set to unlimited. As long as you limit game fps below your desktop refresh rate, you can run with vsynch off /triple buffering off. The NVidia Adaptive vsynch mode does that automatically. It enables vsynch when game fps exceeds desktop refresh rate in order to prevent tearing, it turns off vsynch when game fps drops below desktop refresh rate.

Because P3D runs windowed mode, you only need vsync with fps set to unlimited. This way you prevent tearing when game fps exceeds your desktop refresh rate (which usually is 60Hz). If you set P3D fps limit lower than your desktop refresh rate, you don't need vsync. Standard vsync may induce stutter because it throttles down in steps from 60 > 30 >20 >15 fps when game fps drops below desktop refresh rate. Adaptive vsync helps to prevent this stutter because it switches vsync off when game fps drops below desktop refresh rate.

jimcarell is right, Nvidia 1/2, 1/3 etc. refresh rate vsync only works in Full Screen Exclusive mode which P3Dv2 does not have. Try this: Make sure you have selected an Aero desktop theme, set Nvidia Control Panel vsync to Adaptive and enable the sim vsync + triple buffering.

FSRecorder 1.331 needs FSX-SP1 Simconnect. You can find the installer in the Prepar3Dv2 redist folder.

Carlo, thanks but the older FSX SimConnect versions are not listed in the Control Panel - Programs and Features, they are embedded in the FSX uninstaller I guess (which I do not want to run, I like to keep FSX).

Besides the ESP version I have 3 FSX SimConnect versions in the Winsxs folder, how do you remove/deactivate the 2 older ones (v10.0.60905.0 and v10.0.61242.0) ? I could not remove/rename them (system protected). Or is there no benefit removing them?

Right-click on your windows desktop, then select "Personalization" from the popup, then check if your current theme is one of the Aero themes, if not select one from the list.

1/2 refresh rate vsynch is not working in P3Dv2 because it needs FSE (Full Screen Exclusive) mode. FSX has FSE, P3Dv2 does not, it only offers windowed and simulated full screen modes.