mbucchia

Report this bug to ED. This isn't something I can fix/comment on.

Ah so after all, maybe the utilities aren't so "b.s" huh?

These are the same path. %LocalAppData% is an alias to your user folders AppData\Local. When you type %LocalAppData% in your file explorer, it will take you to that exact same location.

Thx, I probably need to make this the new default for VDXR in QVFR base config

Can you try turning off Turbo in QVFR?

Virtual Desktop with VDXR support is now out of beta and live for everyone, without additional steps to install. Version is 1.29.7.

This issue seems to have nothing to do with OpenXR Toolkit. Are you able to run the game in VR with OpenXR and not OpenXR Toolkit?

@NineLine @BIGNEWY can you look into the conditions that could be causing this for @Dragondal and @IvanG 2023-10-27 19:52:32.635 ERROR SCENERENDERER (17708): Failed assert `depthBuffer.getDims() == dims && depthBuffer.getMSAA() == msaa` at D:\Projects\Buildworker\nevada_testing\build\Projects\render\renderer\Include\rwrappers\inl/FrameBuffer.inl:339 2023-10-27 19:52:32.635 ERROR DX11BACKEND (17708): depth buffer mainDepthBuffer2 (848x872) must be the same size as color targets (752x776) 2023-10-27 19:52:32.635 ERROR DX11BACKEND (17708): Failed assert `false && "depth buffer must be the same size as color targets"` at Projects\render\dx11backend_win8\Source\DX11FrameBufferManager.cpp:101 This condition about depth buffer resolution mismatch only seems to happen when these 2 users are using quad views rendering with OpenXR. The reported resolution do not even match those of the quad views recommended image rect, therefore it's not explainable how a bug in the OpenXR runtime / OpenXR implementation of quad views may be causing it. My suspicion is on an uncommon setting in DCS causing a bug in the engine specifically when the engine uses quad views. Thanks.

Try turning off Hardware Accelerated Graphics Scheduling (HAGS) in the windows graphics settings. Pimax no likey that option.

You have DLSS overlay/developer mode enabled, which isn't related to.QVFR. Open registry at HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NGXCore Set the key ShowDlssIndicator to 0

New Beta update today, 1.29.4, fixes some issues and crashes. Need to go through the same procedure to update both the headset app and the PC app.

Disable Turbo mode in QVFR. This isn't new, it's been like that since day1 of QVFR.

Use OpenXR Toolkit for screenshots. They will be taken after the foveation process, which will therefore include the high resolution rendering as well.

Omg this is NOT THE DLSS THREAD. Please find another place for these discussions.

It only happens for the first 100 frames and can be ignored. If you really want to get rid of it, you can enable Hand Controllers in the DCS menu. Highly doubt this is related to your performance issue (or that QVFR is in general).

yes @recoilfx is correct. With quad views you save a lot of on your GPU, but it requires more CPU to submit the 2 extra views. This can be optimized in the game engine, but not trivial (and it doesn't look like DCS is equipped to do this optimization).

What is Quad Views rendering? · mbucchia/Quad-Views-Foveated Wiki (github.com)

Thanks for the report. We already fixed this issue internally btw. The Oculus compatibility layer thing is also a thing we've added (it's not needed for DCS but it is for some other games).

It would probably help if you could take screenshots (OpenXR Toolkit can capture this effect). Something like looking directly at the sun makes it obvious IIRC?

It doesn't have to be confusing. QVFR will always _output_ to the resolution dictated by the platform (accounting for the focus region supersampling if needed), in this case whatever you have set in Oculus app. You can always check the log file for QVFR, it will tell you exactly what is happening: 2023-09-21 16:06:03 -0700: Recommended peripheral resolution: 720x792 (0.500x density) 2023-09-21 16:06:03 -0700: Recommended focus resolution: 720x712 (1.000x density) 2023-09-21 16:06:03 -0700: Stereo pixel count was: 4561920 (1440x1584) 2023-09-21 16:06:03 -0700: Quad views pixel count is: 2165760 2023-09-21 16:06:03 -0700: Savings: -52.5% (sorry these numbers are ridiculously low but you get the point) About FOV tangent, I can't say for sure whether that works, but you also probably don't need it. QVFR makes your peripheral region low-enough that FOV tangent shouldn't help that much. Monitor resolution shouldn't matter very much unless you have a very old system and a GPU with very low VRAM. I assume your 3090 has 12 GB so it's probably fine to not worry about it.

Yes these issues are only DCS, and as mentioned only ED can fix them. You can try Pavlov VR if you have it on Steam, it works perfectly and it's literally impossible to see the focus area's edges.

NO. The night vision was fixed by ED in 2.9. It is NOT a correct way to tell if eye tracking is working. The correct way is to follow the troubleshooting instructions on the project page.

I'll add some pointers to get started. If you installed the previous "standalone beta 0.6.0", you should uninstall it from Add or remove programs first. Instead grab the latest Virtual Desktop from your app store (1.29.7.). ACTIVATING VDXR Make sure VDXR is selected as the OpenXR runtime in the Virtual Desktop settings. TROUBLESHOOTING If all is working well, you will see VXDR as the runtime in the Virtual: Desktop overlay: VDXR should be compatible with all my other OpenXR mods (such as OpenXR Toolkit and Quad View Foveated). If you are having issues, just do the usual: try Safe Mode, resetting settings, or disabling any mod. Log file for VDXR is created at %ProgramData%\Virtual Desktop (you can copy/paste that directly into File Explorer) and is called OpenXR.log. If you’re going to bring issues to me, you must include this file otherwise no support will be provided. Does it work with other apps? YES, see the list here: Application Compatibility · mbucchia/VirtualDesktop-OpenXR Wiki (github.com)

Do you have Ultraleap by any chance? Their OpenXR support is completely broken at the moment and causes an error with the same signature.

Sorry but can you guys go discuss this on one of the 15 threads about DLSS