If the issue really is our nav displays it might be simpler to open an issue with us that the default Cessna has a certain FPS loss when the GPS does something-or-other. It’s simpler for us to test because there’s no way it’s third party code doing something we don’t expect. 30-40 fps less isn’t necessarily a bug. If you have vsync on and were at 91 fps and you open the nav display, the total fps loss might be quite large as you miss vsync. We’d have to see the bug report specifics.

If a plugin is only tagged a few fps in the admin it means the plugin is not affecting you FPS – it doesn’t mean it’s fast. For example, if you are GPU bound, a plugin can burn up all sorts of CPU time and be tagged with 0 fps loss because there was “extra” CPU to begin with. A more useful number is how many ms the plugin takes.

However, did someone else notice that frames are substantially lower with Win 10 2004 as compared to 1909?

Like I said, you guys are awesome to the 5th powahh..

Thanks again for keeping us posted.

And I was FS and P3D for the last 25 years. X-Plane all the way now.

Thanks for that!

I am not surprised – we see GPU Tweak II in the crash logs _all the time_ and I don’t think we can do anything about it because it loads before X-Plane.

No no I was only mentioning it because slow load is _the_ major bug of b10. I mean: the part where it’s missing a pipeline is bad too, but I think of the bugs not only in terms of user impact but in terms of _how much code we have to change_ to fix them. The missing pipeline with HDR + 2-d panels is bad because the sim quits but it’s one line of code to fix and is unlikely to break other stuff.

Sidney fixed the slow load, but at mid-week the new code (which was much faster) would under certain circumstances hang loading completely – now he has fixed that, but we have yet another case where the sim can fail at load time. Sidney’s working on that now; having the loader fixed is basically the last thing holding up b11.

Meanwhile I found the cause of those crashes.

X-Plane crashed and a couple of other tools had also issues, when a tool called ASUS GPU Tweak II was already running.

I had version 1.9.7.1 of that tool installed (it got delivered with my Rog Strix Geforce RTX 2080 graphics card) and it was autostarted.

When the tool is not running, startup of XP succeeds. I have now updated the tool to newest version 2.1.7.1 which again runs ok with XPlane.

I have ryzen 2600x and GTX 1080ti using latest GPU drivers. Since beta 9 from when I started testing using vulkan option I have around 5-8 fps drop and I don’t see any improvement.
I’ve searched around but could not find anyone reporting same. Maybe something I’m doing wrong? If not then I can report the bug through “Bug Reporter”

Sorry Ben wasn’t trying to be Captain Obvious.. 🙂
But as I have been vocal about b10 not starting I thought to say it is starting just takes longer.

We know you guys are awesome to the 5th powahh.