The last couple of days, I’ve been running some comparisons between FSX and P3D, especially concentrating on doing it right this time.
I had one and the same OS running in double configuration (cloned it after I installed it completely) and then made a boot manager for two installs. So now, FSX and P3D have each their own environments.
Most importantly, the measurements here reflect the performance differences when addons for FSX are included, I didn’t do much comparing on the default FSX/P3D, as I doubt that people are interested in that, nor are many using FSX without addons.
For me, one question was open which I wanted an answer to: is it worth to change to the P3D now. If you want yes or no, then yes. If you are also OK with maybe, then maybe or “depends”.
The fact is, in terms of FPS, P3D with same addons has no advantage over FSX, and in some scenarios even loses. It even looks the same.
But… in the terms of stability, smoothness and, did I mention stability, P3D has made a huge step forward. Even in terms of better ground textures, at least in one scene, P3D seems to have a bit lower FPS, but the trees and ground (default) look way better.
So, FPS have not been everything, but landing with 22fps in FSX and 22fps in P3D, are two completely different things. I ran my smoothness tests, and after doing some video compares, I can say P3D won’t budge when it comes to smoothness, and FSX will occasionally stutter (of course, this is only with a full tweaked FSX by me).
Some of you might know me as a freak who analyzes stuff to the smallest detail. This is what I did with FSX vs P3D in terms of performance. I checked for smoothness, FPS when running, paused, texture loading, all through various test scenarios I have now in both FSX and P3D.
I can conclude following: P3D is smoother than FSX is with my tweaks (bp=0, vsync tweak etc…). Of course, I tried using the same tweaks as in FSX in P3D, and guess what: they check out! Now I have a smooth sim, just like FSX was with my tweaks.
As of lately, I am running P3D along my FSX, and both are purring nice and slow, with FSX having one annoying bug (which doesn’t present itself in P3D): it sometimes crashes on boot. P3D never crashed yet.
Configuration both sims:
- FSUIPC + FSForce2, same FSUIPC.ini
- same tweaks (listen below in this post)
- UTX Europe
- ORBX PNW
- UK2000 EGLL + EGKK
- Flightbeam KPHX
- PMDG NGX (only for testing purposes, not being used in P3D due to licensing!)
Anyway, here we go:
FPS: both sims 21fps
Test2: Default C172 wideview default scenery
FPS: FSX: 73fps, P3D: 69fps
Test3: UK2000 EGKK, default 737, scenery wideview
FPS: FSX: 50fps, P3D: 52fps
Test4: Flightbeam KPHX, default 737, scenery wideview
FPS: FSX: 42fps, P3D: 45fps
Test5: Flightbeam KPHX, PMDG 737 NGX cockpit
FPS: both sims 32fps
Test6: water reflection test
FPS: FSX: 50fps, P3D: 55fps
Test8: ORBX PNW autogen test
FPS: FSX: 87fps, P3D: 74fps
Test9: water dusk test
FPS: FSX: 141fps, P3D: 82fps
Along of this test, I also tested FSX vs P3D VAS usage, and after waiting of about 1 minute after each scenery load for loading to stabilize, here are the numbers (which kind of explains more often OOMs in P3D more than in FSX):
For those who would like which settings were used, here are links to ALL settings:
Now, couple of notes on how and what:
P3D is basically compatible with any scenery working normally in FSX. With scenery is ment anything that is saved under scenery or texture folder.
Those extra DLLs that FSDT, ORBX and some others have will probably have to be adapted.
I will here only mention that Estonia FSX to P3D Migrator Tool is a great tool for installing native FSX stuff to P3D, usually without a problem, but if a problem arises, all you can do is wait for the developer to update it or take a look in P3D forum here, if there is a solution.
Concerning the tweaks, the only tweaks currently running in P3D (and the same performance tweaks were last in FSX) are:
ForceWindowedVSync=1 (not a performance tweak but simple tweak for windowed vsync)
These are the settings that deliver the results from above.
And no, there are no blurries anywhere, and if you start getting blurries, up the FFTF to 0.2, you won’t lose that many frames.