I spent a few hours again last night troubleshooting this issue where opening the Task Manager improves performance. This typically becomes a problem when I’m in an area that is graphic intensive, or CPU intensive… lots of buildings, traffic, etc. Last night, it was Tokyo (with storm clouds) and I was getting drops to 11 FPS with MR. If I opened Task Manager and brought it to the foreground, the FPS jumped back up to 22.5, and then 30 FPS and stayed there. Well this sucks, cuz I need the mouse to click around in the cockpit… simply click on the MSFS window to interact with the cockpit (which sends the Task Manager to the background) and… 11-17 FPS.
Even looking at the GPU utilization history, when the chart line is at 50%, I’m getting 11-17 FPS, switch to Task Manager and bring it to foreground, it jumps to 70% (straight up) and my MR is “locked” back up to 30 FPS. So in the spirit of this thread’s main topic, the Task Manager is a thing.
So I started playing around with CPU affinity. I set MSFS to CPU0 only. Yup, getting 2 FPS LOL!! Set processor affinity to 0 and 1. FPS got better. 0,1,2,3 and was back to 30 FPS. I learned that MSFS for sure is using 4 threads (cores loosely speaking) at the very least, and I believe it’s actually upwards of 6. 4 pretty heavily and another 2.
So I set MSFS to use my top performing cores (which happens to be 0,1,2,3 and 12,13) and then I set the DWM.EXE process to use everything OTHER than those cores. The reason I did this is, because DWM (Desktop Window Manager) is what WMR (Windows Mixed Reality) is also tied to as a system process. This actually had a positive effect. I was able to fly around Tokyo at 30 FPS almost everywhere at 30FPS MR, and it was glorious. It did drop to 22.5 in the most dense part of the city. And this actually worked pretty well, even with the Task Manager closed.
Sort of…
So I loaded up the achilles heel of my system, which is Las Vegas with FlyTampa scenery. This area kills my machine with that scenery. I did get an improvement in performance, but was back to needing the ■■■■ Task Manager open again to get 22.5 FPS. And even then, it would regularly drop to 17 FPS at certain areas over the strip.
So I went to OpenXR and disabled Motion Reprojection. And then Disabled it in the Toolkit just to see where my frames were at without MR. (Thinking CPU utilization to run MR is just nuts in certain areas in MSFS) And my frames were at 45-50FPS without MR. The MOST I could get the framerate to drop was down to 30.
^^ This doesn’t make sense to me guys. If the lowest I could get my frames to go was 30 with MR off, then why am I dropped to 17 with MR on? OH and again, why having the ■■■■ task manager open makes a substantial difference on performance when trying to use MR? If I fly in a less dense, more normal area, I can run MR at 30 for hours and it’s just fantastic.