And another test, this time the other way.

Aerosoft Corfu X:

P3D: 24FPS

FSX: 45FPS

 

What I noticed is that P3D offers a small advantage in FPS over some scenery (I couldn't find any that offers a BIG jump), and over default it's a bit more, but when it comes to FPS drop in some sceneries, it can be pretty much, as noticed above. I double and triple checked.

What could cause that impact? Corfu comes with a dedicated P3D installer, right?

 

Some module having trouble with 1.4? Vistamare?

Corfu comes with a dedicated P3D installer, right?

 

Not that I've noticed. I'm using the migrator to automatically install into P3D. All works well, P3D CorfuX is visually same as FSX, yet 25 vs 45.

 

I don't know if it is a module...

I've just looked at the product page and there should be a dedicated P3D installer (or option). I doubt that it incorporates big changes, but it won't need the extra tool I guess. As for the module, that's the thing Aerosoft uses for the traffic around the place.

 

I was just guessing though. Where else do you see the fps dropping that severely? Maybe there's a pattern.

I disabled everything except FSUIPC, EZCA and FSForce. No changes.

 

Same thing with FT Vienna. 28 vs 38.

Thanks for posting those comparisons, bakayoyo. Very informative stuff. :good:

 

I have a question on the colour tone of the videos. Are they different because LM changed the light/shader setup in P3D (I only had 1.2 running back then) or am I looking at e.g. FSX with REX and P3D without it or something of that kind?

 

I have also noticed that the colors have changed a bit from 1.3 to 1.4 (I never had 1.2), a little less brownish, little more fsx like in 1.4. I haven't used REX weather engine in the videos, but I did apply some of the default rex scheme textures to fsx and p3d. The weather was set to clear skies.

 

I can tell you guys that P3D became much like default FSX colorwise, after I applied REX, Shade...

Hmmm, wow.

 

At first I thought P3D was losing on the front with some sceneries, but then again I was testing with ORBX at first, and my tweaks for SOME strange reason had no impact there, so I removed them thinking they had no general impact.

Now I ran the tweaks in the configuration with CorfuX, FT Vienna and saw even better performance than in FSX. These are now with BP=0 and tweaks from my guide.

Performance jumped way over FSX now.

 

Sorry guys, this loading and reloading is really a tedious thing.

 

I'll keep you posted here, as I progress.

Thanks for all that testing K. Talk about bleeding edge.

 

Ha I was doing some overclocking today, and eventually windows wouldn't repair itself. Almost had to reinstall! Until I realise everything had defaulted, meaning my drive setup had swapped from ide! So I know what restarting lots his like..

Srdan,

 

Were the benchmark results you posted peviously standard P3D vs tweaked FSX ? Looking forward to the tweaked P3D ones.

 

Concerning the colours, no wonder it now looks as FSX again. They repaired the bug on the terrain lighting (red and blue channels were inverted causing i.e. snow textures to appear pink on previous builds).

I am along for the ride to wherever P3D takes me. In my less than humble opinion P3D is the only progress in PC based flight sims we are likely to see for awhile. Initially, I understand, and applaud, that LM is getting the program up to the same level as FSX while accommodating the Microsoft contract. Along the way we may see some improvements as well but I see this period, until V2.0, as cleaning up FSX first. Then 2.0 will begin real progress.

 

For $50 I have no criticism of Lockheed Martin. I may be annoyed at times but until 2.0 there will be some rough patches. I accept them. Version 2.0 may be a different reaction. We'll see.

I am along for the ride to wherever P3D takes me. In my less than humble opinion P3D is the only progress in PC based flight sims we are likely to see for awhile. Initially, I understand, and applaud, that LM is getting the program up to the same level as FSX while accommodating the Microsoft contract. Along the way we may see some improvements as well but I see this period, until V2.0, as cleaning up FSX first. Then 2.0 will begin real progress.

 

For $50 I have no criticism of Lockheed Martin. I may be annoyed at times but until 2.0 there will be some rough patches. I accept them. Version 2.0 may be a different reaction. We'll see.

 

Same.. 1.3 ran, and treated me so well LM won a customer for life with that version so I'm thrilled with 1.4. It's stable and requires no tweaking to run right. (for me). FSX I actually never got to run right regardless of how many tweak guides I followed. The awful and inconsistent texture tile loading was an ever persistent thorn in my side with FSX. Nothing like enjoying a flight and looking out the window randomly to see the ground a blurry mess and stay that way until you move on to the next batch of tiles to load. Prepar3Ds texture loading is leaps and bounds better. While I occasionally do get slightly blurries if I switch cameras in certain locations from VC to exterior or vice versa they clear up in a matter of seconds..

Were the benchmark results you posted peviously standard P3D vs tweaked FSX ? Looking forward to the tweaked P3D ones.

 

Correct. My first comparisons were in the PNW around KSEA, as this is the hardest area in the sim on the autogen and blurries, I was lowering FFTF in FSX to see how low I can go until I start seeing blurries - saw that pretty much anything below 0.2 caused blurries to appear after some time.

Then I went with standard P3D and saw the performance was nearly the same, thus my conclusion was that tweaked FSX = standard P3D. But it is not, it was actually a funny reason that BP=0 doesn't help a lot in PNW area.

I went to more normal tests, like CorfuX, but at first omitted the tweaks.

Now, P3D actually destroys every scenery I installed and compared by now. I set simple tweaked P3D, BP=0 AM=14 and FFTF=0.2. With that, even Frankfurt, the scenery which someone reported as worse performing than in FSX, performs better here. We are talking 20% more in the FPS when using default aircraft - but FPS are not a problem with default aircraft.

Things get more even when I introduce NGX, but still, P3D almost always has a nose in the front by 1-3fps over 30. Not much but it does.

Of course, one could argue now the missing of some other addons which would push the performance down those 1-3fps, like GSX, AES... but hey, who knows? The fact is that I mostly fly NGX, and the performance is almost the same.

I am still keeping the FSX for serious flying on VATSIM and P3D as a fun and tryout sim on the side.

Already alone through the missing startup scenario is P3D a complete fail for me, as I need at least 3 reloads when I set up a normal flight. Not something I'm gonna have vs couple of FPS more. With the tweaks we are using now FSX is *almost* as smooth as P3D, with a big question how smooth would it be if it contained ALL the addons FSX contains?

Kostar: great work and careful comparisons. I am a long way from my computer at the moment so it will be another ten days before I install 1.4.

 

But as I found with v1.3 it is smooth that counts.

 

Max fps concerns me not at all. Smooth at 30 fps in cruise at most levels is all I need.

 

It is how smooth the sim remains with the same settings as the fps drops in more complex areas and airports. Here I found P3D to retain its smooth below 10 fps without stutters. Below that, remember it is FSX on vitamins after all.

 

For those concerned about transferring from 1.3 to 1.4, I will copy my existing setup, Main folder, Roaming\Appdata, and Program Data over to external storage. Then I will make sure everything is cleaned out. Not just an uninstall but a delete of all the folders.

 

Then I will reinstall and copy all aircraft and utility files over. But I will reinstall all my Orbx, UTX and GEX scenery on the basis that most of the changes will have to do with scenery processing. Hover the Addon Scenery folder will be copied back so that I can quickly re-connect the folders in the Scenery Library.

 

Make sure your Control XML gets copied across into the Control Folder - why start again?

 

Also the exe.xml and the DLL.xml should come over, even if you delete the content.

 

BUT as others have advised, on reinstall add Nothing until you have taken a default aircraft for a flight in the local area. This gets the cfg file built and seems to settle everything in.

 

Don't forget the old suggestion - Reboot frequently. It is a custom lockin process.

 

 

Warmest regards,

 

Ian McPhail

---------------|1.4s|1.4t|fsxt|

orbx-----------| 1 | 1 | 1 |

Madeira X------| 2 | 1 | 3 | +

Frankfurt X----| 3 | 1 | 2 | ++

Marshall isl.--| 2 | 2 | 1 |

Horizon Gen x--| 2 | 3 | 1 | -

autogen--------| 2 | 2 | 1 |

 

1.4s = standard, 1.4 = tweaked, fsxt = fsx tweaked

 

I also rerun my recordings with the BP=0 AM=14 and FFTF=0.2. OrbX remains a draw. Madeira X gets a slight improvement and still beats fsx. Frankfurt X improves significantly and edges fsx. Marshall Islands sees no change and runs a lot better on fsx. Gen X slightly worsens and runs better on fsx. Autogen sees no change and runs better on fsx.

 

I think some scenery especially aerosoft reacts well to tweaks. It also looks like Orbx has done a good job optimizing their scenery to run well on both fsx and p3d.