1Sascha Posted October 8, 2024 Posted October 8, 2024 (edited) Slightly unrelated but I'll get this one out of the way first: I used to be able to run Afterburner/Riva-Tuner's monitoring overlay on IL-2's monitor window in VR. Like in this older video I recorded: I found this very helpful as I would let that thing run, record my screen while doing VR and I could then use the recording to see how the system behaved WRT frame-times, temps, load, fan-speed etc by reviewing the footage. Even before I upgraded to the Q3, I noticed that I had lost the ability to show the overlay on that window for some reason. I *think* I finally gave into the nagging screens and updated RT to a newer version and that's when the overlay stopped working. Weirdly enough, it still works fine in all flat games I play (including IL-2 non-VR). Anyone have an idea what could be causing this and if there is a cure? I already took this to the Guru3D forum, but all I got as an answer was getting insulted by a resident grumpy old man. I also tried different resolutions (720p, 1080p, 1440p) and running IL-2 both in windowed and fullscreen-mode. Results were always the same. Anyway: After upgrading to the Q3, I noticed that I was getting similar behavior on it as I was on the G2 when it came to screen-capturing/-recording (using GF Experience). On the G2, whenever I went above 100% render resolution in the OpenXR-Tools for WMR (not OpenXR Toolkit), capturing IL-2's monitor/mirror window would feel like capturing games to an HDD 20 or 15 years ago. FPS would drop considerably on starting the recording and would stay that low until the recording was stopped. Whenever I went back to 100% in OpenXR Tools but then used "Override Resolution" in OpenXR Tool*kit* (God, these names are so confusingly similar!) to set a higher resolution, starting or running the recording had no discernible impact on performance/in-game FPS. The same thing now seems to happen with the Q3: Running 1.4x or 1.5x in Oculus App (5152x2752 or 5408x2912) and setting "Override Resolution" to "No" in OpenXR Toolkit = stuttery performance whenever recording is started/run. Going to 1.0x in Oculus App and then "manually" setting either a resolution equivalent to 1.4 or 1.5x in OpenXR Toolkit .. or even something *higher* than the highest res I can set in Oculus App (I tried both 3030/6060 and now 2900/5800 in there) and starting and running the recording does not result in stutters or reduce FPS. I even still had 10 to 20% GPU headroom left at 2900, 80 Hz with the recording running. Can anyone explain what could be going on here? It seems that even though I'm getting the same (or similar) resolution in-headset (just via different methods), one of the methods of achieving these resolutions seems somehow more taxing on the GPU (or CPU?) than the other. S. Edited October 8, 2024 by 1Sascha
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now