Thank you mbucchia for giving us your free time for this amazing open xr version. I honestly thought you were getting paid for this.
I have never seen such smoothness, clarity, colour rendition and reliability in any headset in any sim in any weather until now and had almost given up on MR in despair because of the wobbles. Only issue I have is sometimes the Reverb G2 black screens on exiting VR but the sim doesn’t crash. I just pull out the headset USB to finish the sim session in 2D or as someone here said, turn off prefer frame rate in XR tools before exiting VR.
Specs:
W10 4090 on water, 9700k OC 5GHz on water, 32GB XMP DDR4 3200
Open XR tools:
MR on limit 1/3 frame rate
Optical flow on
Prefer framerate on
Custom render off
Windows:
Hags on, game mode on
Rivatuner
30 FPS lock on FlightSimulator.exe
app detection high
frame limit async passive waiting on
Sim:
DLSS performance
TLOD 70,
OLOD 100
VClouds High
Toolkit:
Override Resolution 4414x4320
Post processing adjustments
CAS 50%
MR unlocked
Frame limit off
FOV 100%
FFR off
NCP:
AF 16x
Low latency off
Prefer max performance
Sample optimisation on
Nbias clamp
Texture filtering performance
Threaded optimisation on
Pre-rendered frames 1
Driver version 531.29
Thank you to the people who pointed me to the Rivatuner frame rate limit. It is an incredibly good framerate locking tool they deserve applause!
Thank you to all the people in this thread for some other fantastic optimization tips. The discovery that FOV 100% is essential to prevent MR tearing is awesome!
… not all frame rate locks are created equal nor work at the same layer of the rendering pipeline. The RTSS and NVCP ones work at the driver level, and rtss is much much better at it. Weirdly the older Nvidia CP locks worked better, than the V1 and V2 ones….
I was sitting on 200% res comfortably on a 3090GPU/9700k-5Ghz combo on 30fps LOW clouds and 70% Tlod in the Milviz 310R on DX11 so suggest experiment with settings on a 4080. The combo of hi-res and performance dlss is very good. At Tokyo international flying GA it would drop to 23(45) fps lined up and still does on a 4090 because it is CPU bound . All the 4090 does is allow even higher Gpu settings and better all round consistent experience in DX12 relative to the 3090. But if you can get the frames locked consistently with RTSS even 1/4 MR in the XR tools produces a 90% wobble free image in MR which is very smooth and 200% res should be achievable on a 4080.
I have a problem with my HP Reverb G2 (v2.0).
After barely a few minutes of flying or, sometimes before even getting in the air, my VR headset left eye goes black. After 2 seconds my right eye then goes black. After about 5-10 seconds, both displays come back on again. This cycle again repeats itself continuously after 10 seconds.
I have just received a replacement cable from HP but all to no avail - as it is still happening, so the cable is NOT the cause.
I am a bit concerned that I might have a driver issue here, either with AMD or even OpenXR.
Any held greatly appreciated.
My system is as follows…
CPU: Ryzen 9 3900x
Graphics: AMD Radeon RX 6900XT (MSI)
Memory: 64gb
Motherboard: X570
Length of Use to date: 11 months
I have a similar system, just a different cpu, i had nearly all problems with this g2 you can have
I would recommend to try ALL USB 3 ports you have. Is your motherboard bios up to date?
These 570 mobos were tricky, i have AGESA 1.2.0.8 and all is good now.
I can second this. - 3080 / i5 9600K
Open XR Tools for WMR = 150%
DLSS - Quality
RTSS - 30 FPS
Seeing consistent 30FPS with Motion Reprojection in the G2 and the resolution is greater than ever. My GPU is finally being utilized and not limited by my CPU. (as much)
Was having issues where the WMR desktop would randomly not display in VR on the G2. Tracked it down to two settings which cause it:
prefer frame rate over latency in XR tools,
multithreaded optimisation in NCP.
both need to be OFF to display WMR desktop consistently in vr for me on a 9700k/4090.
I’m in no position to answer/comment on that. I’m just stating that the upcoming store update has no changes to WMR/PCVR.
I know somehow someone will find a way to make a thread “oh did you see there’s an update”, so I’m putting this message out first to avoid any confusion.
Other note: as the preview runtime 113 will be updated, the current stable runtime 112 will remain the same (for people who might be concerned about losing access to 112 - this is not the case).
Are you plugged in via usb-c or c to a converter? Are you plugged in on the back of the motherboard or the front panel? Are you connected to a USB port of your CPU or the chipset of your motherboard?
Depending on your motherboard the USB ports are split to either CPU or chipset. You can look up the specs to see which USB port goes where and try a USB port, either usb-c or use the converter to usb-a on the CPU.
Sorry to dive in with a question here, but I guess someone will know!
Trying to set Riva Tuner SS as described above to see if it solves the annoying hitching I am getting regardless of other settings (resolution, quality, graphics settings), but not sure it is working. How do I know it’s active? I asked for on-screen display but it does not show up. I tried this on Global and then on the FS.exe (screenshot).
I notice that if I close the settings window, it’s gone from the system tray. Does that mean it’s closed itself?? The only way I can get it back to system tray is opening the app again, suggesting that it closed and is having no effect after doing the setup. I guess I should only ever Minimize it after changing anything. But even with the app window open OR in tray, no counter on screen so really not sure if it’s doing anything…
I realise that, but I read elsewhere that RTSS works for Q3 also. But as I say I can’t see that it’s active so was just after some advice on that really.
Enable the MSFS FPS overlay in the Developer mode and you will be able to see your FPS. If you don’t have any other FPS limiters enabled and you will see 40FPS in the overlay - it will probably mean that RTSS FPS limiter works.
You don’t want SSW active if you are limiting the frame rate via Riva tuner - use one or the other. The purpose of both tools is to limit the frame rate to half the display’s native limit. SSW does this by adding in generated frames to fill the gap, using Rivatuner you are effectively displaying each frame twice and not generating fill frames.
SSW may appear smoother, Rivatuner may appear clearer.
