I’m using G2, I7-8700K at 5 ghz, 32 gb ram, RTX3090 980 Pro nvme, 50 mbs connection, HT off. (HT on has a significant impact on mainthread performance)
I’ve flying for the last few weeks without motion reprojection, getting 28-38 fps using OXR 100 and TAA 80, mostly high and ultra settings. All seems stable and good until I go to EGLC/KLAX/NY and then framerate struggles a little. This weekend I’ve tried to get it working with motion reprojection, accepting there will be a performance hit I’ve reduced my graphic settings appropriately. Got it working well until I tried EGLS/KLAX/KLGA again. Here the mainthread is just swamped with addition of motion reprojection. As an experiment I have reduced TAA to 50% LOD to 10%, OD 10% and all other settings to their minimum, low or off, GPU 60% and CPU 40%. Flying above EGLC in the TBM I get in VR 90fps and main thread 8ms with reprojection off, with it on I get 45fps(limited due to MR) but an increase in main thread time to 23ms.
Clearly there are more buildings in these areas so I imagine even with buildings and trees low there is much work to do on the main thread, however motion projection seems to increase this disproportionally making flying in these areas impossible with any reasonable graphic settings. This isn’t something that can be fixed with a faster single core CPU, so any ideas other than avoid these areas, are you seeing the limitation with MR?
Use the WMR Frmae Time overlay (turn it on in OpenXR dev tools, and it appears in left eye & WMR mirror) - I’ve found the MainThread time in the MSFS overlay seems to include MR GPU time. Won’t fix the underlying problem, but will at least help you dial in the settings to get the best experience that is possible by seeing the real impact on CPU/GPU of each change. I found it’s actually almost all GPU.
i’ve got a 3080 with a 5800x and don’t bother with MR as I’ve got to have the settings so much lower to hit 30fps, it’s just not worth it. When I moved from a 3600x to 5800x, it didn’t make MR any ‘easier’ to dial in.
Make sure you have updated to the latest version of the OpenXR Developer Tools that just came out last week. This has seemed improve things for me a bit.
Also with Motion Reprojection on, the FPS counter isn’t very reliable as it seems to lock your frame rate to 1/3 of your refresh rate. A better check is to watch the overlay box and when it is blue Motion Reprojection is working, when it is red it isn’t.
The thing that has been a game changer for me is to set the refresh rate of the G2 to 60hz, that way you can get full motion reprojection all the way down to 20FPS. Yes there will be a slight flicker, but for me personally, after 10 minutes or so, I don’t even notice the flicker any more. Now I can fly Midtown Manhattan with high/ultra settings, TAA100/OXR100 and it looks and feels amazing.
System Specs:
Ryzen 5 5600x
32GB DDR4-3600 RAM
RTX3090
HP Reverb G2
On my last PC build, with HT off, performance was BAD even in single monitor mode. Turning HT on was night-and-day. I was pretty certain that FS2020 made extensive use of HT so I didn’t even question it when I did my new build - I have HT on.
It certainly looks like so. With reprojection on the main thread time is always GPU time + 2~3ms regardless of settings. It makes sense if the main thread now has to wait for the GPU to finish before it can finish its work. I am just guessing.
HT = Intel Hyper Threading, I think the reason it may help is that MSFS uses 4 key threads, therefore cores over 4 probably add little. So the i7-8700 has 6 cores (12 HT) therefore you probably get more efficiency with a single that splitting it between two threads and sharing resources.
Thanks @MinnMonkey for the info re the dev tools main thread value. I used the OXR numbers instead and was helpful, however I got interrupted with the World Update. I’ve come the conclusion that the MR overhead is not worth it. You need to reduce settings to much so that it works in dense areas, with it off you get significantly higher framerates which are enough to overcome the need for MR in the first place. With MR on you tend to get sudden stutters when fps goes below 30, overall smoother experience without it!