sbs9

I found a 9800X3D under the Christmas tree 🙂 I’ll report back soon! As for the diagram from the referenced test, it states "Medium", which makes sense – at ULTRA, even an RTX 4090 at 1080p could start to bottleneck in MSFS24. That’s fine, though, since the sim’s lifespan will likely see the introduction of the RTX 6000 series GPUs 😉

One has to laugh when reading some of the hoaxes posted here. First, only the 1080p test (shown below) makes any sense when comparing CPUs, and this is also clearly explained in the referenced article. Second, consider their testing scenario: "Our benchmark sequence uses the Ísafjörður landing challenge under the 'Epic' settings. But we're not even trying to land — we're just flying over the water in the same path each time." Flying over water, presumably with a default airplane, no photogrammetry, no complex airport, no complex aircraft like the Fenix that would actually tax the CPU. And yet, despite this limited scenario, the results still show a strong advantage for the 9800X3D. That’s actually surprising and impressive—I’m ordering one soon!

My two cents for those with flickering textures. Do you use EZCA? It sets the ClipMode of its cockpit views to 'Minimum'. Try to delete this setting from EZCA camera definitions, which will restore ClipMode to its default value, i.e. 'Normal'. 'Z bias scenery flickering issues' fix could eventually make the sim more sensitive to ClipMode value. The reason for my suspicion is that, when testing v. 3.3 at an ORBX airport, I noticed an unusual level of flickering, but only in the Avatar mode (not affected by EZCA) that has a very low default near clip plane of its camera. I solved it by increasing the NearClipOverride value in the Avatar's sim.cfg file.

980Ti + 4790K at 4500MHz, but the key to successfully utilize 30Hz approach is to establish a balance between YOUR hardware and P3D settings to maintain 30 FPS.

Let me share one more tip to completely kill stutters in P3D - set the monitor frequency to 30Hz in Windows (if your monitor supports it). In P3D: Target frame rate unlimited, VSync On, Triple Buffering enabled. This eliminates all stuttering if your FPS doesn't drop below 30 (strong GPU required).

Pete, do you use ORBX Scenery Library Insertion Point tool? It can be found under Settings>Tools in FTX Central.

Bad news! I remember those old golden FSX days when I had to check terrain.cfg after each ORBX install. P3D is so boring in this respect, not many puzzles, at least on my setup. Will probably buy this Heathrow to have some fun again... )

ORBX installers used to change the entries listed in the file below (it's from my old FSX post related to the anomalies at Aerosoft Tegel). Affected lines are in bold. These "tweaks" caused problems with layering at some airports. As I'm away from my flightsim PC, I cannot say if it's still the case... https://www.dropbox.com/s/ok9mn104nd8dfg7/terrain.cfg.right.values.pdf?dl=0

My two cents - terrain.cfg? Changes in terrain.cfg (made by an ORBX installer) caused trees on runways at Aerosoft EDDT. Would try the default or backed-up version of this file.

I would give version 3.2 one more chance and try that flight without any VAS measurements. Just enjoy it I recommend deleting shaders and also completely switching off the road traffic (it solved OOM problems for me in 3.1). At least on my setup, version 3.2 looks better and performs better.

Was that comparison made ceteris paribus? I mean with the same scenario, weather, date and time, traffic, route, pace etc.?

Richard, I don't say it is now as good as SGSS. But I think it's as good as with Transparency Multisampling + 8x Supersampling in NI and that is some achievement. Only SGSS can completely eliminate shimmering, but the cost is too high for me, with heavy clouds the drop in FPS is just unacceptable, even with a superclocked 980Ti. I look forward to Pascal GPUs

I compared the performance of 3.2 and 3.1 by means of FSUIPC logs. Same scenario, same settings, different results! Ran several times, Windows and P3D always restarted. As you can see, the increase of frame rate is significant. VAS usage is reduced. Used scenario is relatively GPU intensive (4 cloud layers), I have 980Ti. Antialiasing is improved too. I cannot support it with quantitative data, but would bet they switched on Transparency Multisampling and/or Supersampling. In version 3.1, I used Transparency Multisampling ON + 8x Supersampling (not Sparse Grid) in Nvidia Inspector with great results. Now I can switch those off without any loss in picture quality.

Thank you, it works great except for one thing. With PFE, MCE was aware of frequencies and my copilot was able to "switch to delivery", "switch to tower", etc.. With PF3, my copilot is not informed and asks me about the frequencies all the time.

Works great, thank you for the wonderful support!

Thank you in advance. If possible, please consider to look at another small annoyance - red "ctrl-z" info text getting stuck...

David, MCE works in P3D31, the above mentioned crash takes place ONLY when the app closes, thus not directly influencing the experience. P3D31 enables the calibration of controllers - a relevant improvement for many users.

Affirmative. The same error in P3D31 when fsinsider.dll enabled.