What's Going to be in the Next Update

[CptLucky8]

@sarpouli

The main reason why XP would always win when it comes to FPS is that it’s just inferior to the MSFS in case of the maxed out graphics, hence the threshold at which your CPU ever gets tired is way too higher with it.

I believe you’re wrong for many reasons about this.

You might want to read this first:

and follow the included links in order to understand what I’m talking about precisely

Terrible VR performance with top end Ryzen / 3080 system

Do you mind providing some pointers agreeing with this? Because as far as I know, and I should know, XP11 multi-core tasking system is actually a reality and one of the many improvements XP11 benefits from (and not just for VR and Vulkan). Quickly found with my search engine: And here is the main developer blog “Threading” articles:

Then this:

@CptLucky8

It is true it is a bottleneck but there is not much other ways to do either. Maybe FS2020 could benefit from a task scheduler using more cores and spreading the work tasks a little more as well, but in the current state it is not using much core. But how much?

I suspected it needed a minimum of 2 cores itself (main thread and render thread) and probably 1 more (DX11 thread) for a total of 3, and I’ve just tested:

And once done, you might want to further think about this:

@CptLucky8

An example: In FS2020, like any other simulator since FS9 (at least), whatever the operating system and the computer I’m running it with, whenever I’m in short final there is a small stutter when I reach a certain distance to the runway. This is happening with all these simulators and this is the worst moment to stutter.

The only explanation I’ve found over the years is that at this particular distance, the simulator is loading the OMI Markers sounds and this loading event is making the stutter. If it is not the sound, it is more likely something else they only load once below a certain distance threshold and whatever it is in the end, it is causing a stutter and this is happening since FS9…

This is not the case in X-Plane (please no debate, just comparing how it runs) where the internal task scheduler has been greatly improved upon and does a good job at balancing the tasks, but more importantly in how X-Plane is pre-loading all necessary assets “intelligently” so that when these are needed (either being rendered on screen or played on the speakers) it won’t stutter the simulator.

Makes you wondering.

On a positive note, Sebastian did address this specific question and did say, albeit indirectly, they are indeed revamping the task scheduler. They have already started if I’m not mistaken with the tessellation (and it is WIP and could be part of what is now causing less performance since WU3), and I also believe they won’t have any other way of doing in order to fully support DX12 multi-threading optimization opportunities, unless when he is saying “don’t expect a fps boost because of DX12”, it might not provide them the same optimization path which benefited XP11 with Vulkan (DX12 and Vulkan are very similar - just at the higher level of viewing this - about this specific optimization opportunity).

---

I believe the necessity of supporting Linux, macOs and Windows are compelling reasons to build your own instead of relying of the OS provided per-app thread pool and this definitely gives an advantage to XP11 for this matter. I don’t know if FS2020 is implementing their own or if they are using the OS provided ones only:
Thread Pool API - Win32 apps | Microsoft Docs
User-Mode Scheduling - Win32 apps | Microsoft Docs