handqual Posted October 4, 2024 Posted October 4, 2024 5 hours ago, Gideon312 said: Interesting post on Reddit by mbucchia: His suggestion is to uninstall OpenXR toolkit, a piece of software which isn’t maintained in the last two years. This is very interesting - it's a pity as I use OXRTK to display the time in my headset so I don't lose days! Does anyone know a different way to achieve this?
Marshallman Posted October 5, 2024 Posted October 5, 2024 (edited) On 10/2/2024 at 2:51 AM, Doggo said: Thanks! That tool is very useful. I reinstalled quadviews and its working. I need the openxr support for my accessories. See the screenshot message, anybody else have warnings like that? Yes I have this! Im using Reverb G2 ... and QV works great for me ....just updated and found this thread. Checked that box and same...looks like it wont let me apply it either. I have uninstalled OPEN XR as recommended....will try again Regards Edited October 5, 2024 by Marshallman 3XS AMD RyzenTM 7 9800X3D, AM5, Zen 5, 8 Core, 16 Thread, 4.7GHz, 5.2GHz Turbo, ASUS PRIME X870-P WiFi AM5 DDR5 PCIe 5.0 ATX Motherboard,Nvidia Geoforce RTX4090,Corsair Vengeance Grey 64GB 6000MHz AMD EXPO DDR5 Memory Kit,Windows 10 Pro Reverb G2V2
Marshallman Posted October 5, 2024 Posted October 5, 2024 (edited) 5 hours ago, Marshallman said: Yes I have this! Im using Reverb G2 ... and QV works great for me ....just updated and found this thread. Checked that box and same...looks like it wont let me apply it either. I have uninstalled OPEN XR as recommended....will try again Regards So having deleted XRTK...I can no longer launch DCS via VR options. Have carried out a full repair and still the same Any advice please? Presume there are files still with OXRTK some deepin the program? Regards Edited October 5, 2024 by Marshallman 2d ok NOW 3XS AMD RyzenTM 7 9800X3D, AM5, Zen 5, 8 Core, 16 Thread, 4.7GHz, 5.2GHz Turbo, ASUS PRIME X870-P WiFi AM5 DDR5 PCIe 5.0 ATX Motherboard,Nvidia Geoforce RTX4090,Corsair Vengeance Grey 64GB 6000MHz AMD EXPO DDR5 Memory Kit,Windows 10 Pro Reverb G2V2
sleighzy Posted October 5, 2024 Posted October 5, 2024 2 hours ago, Marshallman said: So having deleted XRTK...I can no longer launch DCS via VR options. What happens when you launch it? What “VR options”? Attach your “C:\Users\username\Saved Games\DCS\Logs\dcs.log” file (may just be named dcs if Windows is hiding your file extensions) for when try to launch DCS. AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
Marshallman Posted October 6, 2024 Posted October 6, 2024 (edited) 12 hours ago, sleighzy said: What happens when you launch it? What “VR options”? Attach your “C:\Users\username\Saved Games\DCS\Logs\dcs.log” file (may just be named dcs if Windows is hiding your file extensions) for when try to launch DCS. Thanks!! The new panel appears for DCS I have Reverb up and ready (viewing the scene for startup) When I select Start DCS I choose VR and the game boots into 2D mode. Here is file as requested dcs.log I have been away for a while and got back yesterday, downloaded the updates and then tried DCS which worked well in both modes to start although problems with VR, so i went on this forum and tried deleting the OXRTK as suggested. now it does the above. Regards Edited October 6, 2024 by Marshallman Added information 3XS AMD RyzenTM 7 9800X3D, AM5, Zen 5, 8 Core, 16 Thread, 4.7GHz, 5.2GHz Turbo, ASUS PRIME X870-P WiFi AM5 DDR5 PCIe 5.0 ATX Motherboard,Nvidia Geoforce RTX4090,Corsair Vengeance Grey 64GB 6000MHz AMD EXPO DDR5 Memory Kit,Windows 10 Pro Reverb G2V2
hsth Posted October 6, 2024 Posted October 6, 2024 In your log file there are still lines referring to the now gone openbeta install. Have you tried with SkateZilla's tool to set all correct paths for both the DCS & saved games directories? You can find the tool here https://forum.dcs.world/topic/134493-the-dcs-updater-launcher-gui-utility-version-20-2023/ . 1
Marshallman Posted October 6, 2024 Posted October 6, 2024 (edited) Thanks utter confusion here...I will check it out! Regards Edited October 6, 2024 by Marshallman 3XS AMD RyzenTM 7 9800X3D, AM5, Zen 5, 8 Core, 16 Thread, 4.7GHz, 5.2GHz Turbo, ASUS PRIME X870-P WiFi AM5 DDR5 PCIe 5.0 ATX Motherboard,Nvidia Geoforce RTX4090,Corsair Vengeance Grey 64GB 6000MHz AMD EXPO DDR5 Memory Kit,Windows 10 Pro Reverb G2V2
sleighzy Posted October 6, 2024 Posted October 6, 2024 (edited) 1 hour ago, Marshallman said: Thanks utter confusion here...I will check it out! Regards Don't worry about the Openbeta thing, it's perfectly fine. Your directories will still be named Openbeta if you already had it, that's normal. Your problem is that you are running an old version of the ReShade plugin, the one that very first introduced OpenXR support. If you uninstall it it will will fine, it's stopping your OpenXR runtime from starting which means it's failing over to 2D instead. You can install this tool and untick the ReShade box in it so that the ReShade API layer is deactivated instead to test this out. You should however download the latest ReShade version and install that if you have to use ReShade, uninstall the old one completely first though. https://github.com/fredemmott/OpenXR-API-Layers-GUI In case anybody else runs across this comment you can identify it from the logs like so: This line shows that the ReShade OpenXR API layer is installed (which is fine for later versions of ReShade) OpenXR: Name=XR_APILAYER_reshade SpecVersion=1.0.0 LayerVersion=2 Description=crosire's ReShade post-processing injector for 64-bit Then you get this error which is the OpenXR runtime failing to start, due to a file access problem, which means it'll start in 2D instead. OpenXR failure XrResult failure [XR_ERROR_FILE_ACCESS_ERROR] Origin: xrCreateInstance(&createInfo, &instance) Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:410 2024-10-06 07:33:31.073 ERROR VISUALIZER (Main): OpenXR exception: XrResult failure [XR_ERROR_FILE_ACCESS_ERROR] This is because older versions of ReShade installed it to a directory it shouldn't, which by default wasn't accessible by OpenXR apps/runtimes to use. Later versions of ReShade changed this directory to make it readable when installed, so they work as expected. Edited October 6, 2024 by sleighzy AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
Marshallman Posted October 6, 2024 Posted October 6, 2024 17 minutes ago, sleighzy said: Don't worry about the Openbeta thing, it's perfectly fine. Your directories will still be named Openbeta if you already had it, that's normal. Your problem is that you are running an old version of the ReShade plugin, the one that very first introduced OpenXR support. If you uninstall it it will will fine, it's stopping your OpenXR runtime from starting which means it's failing over to 2D instead. You can install this tool and untick the ReShade box in it so that the ReShade API layer is deactivated instead to test this out. You should however download the latest ReShade version and install that if you have to use ReShade, uninstall the old one completely first though. https://github.com/fredemmott/OpenXR-API-Layers-GUI In case anybody else runs across this comment you can identify it from the logs like so: This line shows that the ReShade OpenXR API layer is installed (which is fine for later versions of ReShade) OpenXR: Name=XR_APILAYER_reshade SpecVersion=1.0.0 LayerVersion=2 Description=crosire's ReShade post-processing injector for 64-bit Then you get this error which is the OpenXR runtime failing to start, due to a file access problem, which means it'll start in 2D instead. OpenXR failure XrResult failure [XR_ERROR_FILE_ACCESS_ERROR] Origin: xrCreateInstance(&createInfo, &instance) Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:410 2024-10-06 07:33:31.073 ERROR VISUALIZER (Main): OpenXR exception: XrResult failure [XR_ERROR_FILE_ACCESS_ERROR] This is because older versions of ReShade installed it to a directory it shouldn't, which by default wasn't accessible by OpenXR apps/runtimes to use. Later versions of ReShade changed this directory to make it readable when installed, so they work as expected. You are a BLOODY STAR!! thankyou so much!!! Nimbus!! 3XS AMD RyzenTM 7 9800X3D, AM5, Zen 5, 8 Core, 16 Thread, 4.7GHz, 5.2GHz Turbo, ASUS PRIME X870-P WiFi AM5 DDR5 PCIe 5.0 ATX Motherboard,Nvidia Geoforce RTX4090,Corsair Vengeance Grey 64GB 6000MHz AMD EXPO DDR5 Memory Kit,Windows 10 Pro Reverb G2V2
sleighzy Posted October 6, 2024 Posted October 6, 2024 8 minutes ago, Marshallman said: You are a BLOODY STAR!! thankyou so much!!! Nimbus!! Awesome! Also this is a post for Quad Views, but looking at your log you don't have the Quad Views Foveated API layer installed either. What headset do you have? You need to install this for QV to work https://github.com/mbucchia/Quad-Views-Foveated 1 AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
Marshallman Posted October 6, 2024 Posted October 6, 2024 2 minutes ago, sleighzy said: Awesome! Also this is a post for Quad Views, but looking at your log you don't have the Quad Views Foveated API layer installed either. What headset do you have? You need to install this for QV to work https://github.com/mbucchia/Quad-Views-Foveated REVERB G2 Mk2 Definitely works with Quad views. I have Quadviews companion which was working although not eye tracking.. 3XS AMD RyzenTM 7 9800X3D, AM5, Zen 5, 8 Core, 16 Thread, 4.7GHz, 5.2GHz Turbo, ASUS PRIME X870-P WiFi AM5 DDR5 PCIe 5.0 ATX Motherboard,Nvidia Geoforce RTX4090,Corsair Vengeance Grey 64GB 6000MHz AMD EXPO DDR5 Memory Kit,Windows 10 Pro Reverb G2V2
sleighzy Posted October 6, 2024 Posted October 6, 2024 (edited) 8 minutes ago, Marshallman said: REVERB G2 Mk2 Definitely works with Quad views. I have Quadviews companion which was working although not eye tracking.. Quadviews companion is just a third party app for configuring some of the QV settings for the Quad Views api layer. You still have to install the API layer. The tick box in DCS just enables things on the DCS side. The Steam OpenXR runtime and WMR runtime (one of which I'm assuming is what you are using with your G2) does not natively support quad views (only two runtimes do) which is why this API layer is required. You'll know its actually working if you install that API layer, start DCS, and then look at the C:\Users\username\AppData\Local\Quad-Views-Foveated\Quad-Views-Foveated.log file which will show the settings it was using and the pixel savings it's given you. Edited October 6, 2024 by sleighzy 1 AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
Marshallman Posted October 6, 2024 Posted October 6, 2024 Not running Steam at all. but done the above. API layer is showing QViews !!! Thanks rebooting 3XS AMD RyzenTM 7 9800X3D, AM5, Zen 5, 8 Core, 16 Thread, 4.7GHz, 5.2GHz Turbo, ASUS PRIME X870-P WiFi AM5 DDR5 PCIe 5.0 ATX Motherboard,Nvidia Geoforce RTX4090,Corsair Vengeance Grey 64GB 6000MHz AMD EXPO DDR5 Memory Kit,Windows 10 Pro Reverb G2V2
Marshallman Posted October 6, 2024 Posted October 6, 2024 Spot on thankyou back in VR!!!!!! 1 3XS AMD RyzenTM 7 9800X3D, AM5, Zen 5, 8 Core, 16 Thread, 4.7GHz, 5.2GHz Turbo, ASUS PRIME X870-P WiFi AM5 DDR5 PCIe 5.0 ATX Motherboard,Nvidia Geoforce RTX4090,Corsair Vengeance Grey 64GB 6000MHz AMD EXPO DDR5 Memory Kit,Windows 10 Pro Reverb G2V2
mmike87 Posted October 13, 2024 Posted October 13, 2024 I have been playing around with all the "new" configurations that seem to be available ... and I wanted to try NOT using Varjo Foveated or QVFR so I could go back to using Open XR Toolkit. At one point, the FFR worked, and then I changed something and now it doesn't seem to do anything. I reset OXRTK to default, disabled the Varjo Base registry keys, etc. and nothing I do makes FFR work in OXRTK with my Aero. If I launch DCS with the "Quad Views" box checked, and OXRTK enabled, DCS hangs indefinitely. On 10/3/2024 at 8:26 AM, gonvise said: 1. Try disabling turbo mode in QV. The same thing happened to me and by deactivating it it worked again. or 2. Try VRS Foveated Rendering (OpenXR Toolkit). It still works better for me than QVFR and it doesn't matter whether you activate the options within DCS or not. null
sleighzy Posted October 13, 2024 Posted October 13, 2024 (edited) 1 hour ago, mmike87 said: If I launch DCS with the "Quad Views" box checked, and OXRTK enabled, DCS hangs indefinitely. OpenXR Toolkit is not compatible with Quad Views (only if you "hack" around it by installing the Quad-Views-Foveated API layer). This is because enabling Quad Views ensures that DCS sends 4 views (if requested by the runtime or an API layer), however OXRTK only supports the normal 2 views. You can drop a DCS log file here for confirmation that it isn't something else. Edited October 13, 2024 by sleighzy AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
mmike87 Posted October 14, 2024 Posted October 14, 2024 I was able to get it to work last night with Quad Views Foveated (it's known to not work with Varjo Foveated) and everything I tried in OXRTK seemed to work, except FR which makes sense given QVF handled FR itself. The performance wasn't great and the visual quality was worse. I went back to Varjo Foveated to refresh my memory, and it still has the best frame rate and overall visual clarity, but still doesn't seem as smooth (despite the lower frame rate) as just using OXRTK without VF or QVF. What I don't think I tried was forcing "stereo" in Varjo Base and then trying OXRTK. Lots of moving parts - it's fun to tinker with - to a point. LOL.
zildac Posted October 14, 2024 Posted October 14, 2024 OXRTK works fine with Quad Views Foveated on Varjo. This has always been the case. 14900KS | Maximus Hero Z690 | ASUS 4090 TUF OC | 64GB DDR5 6600 | DCS on 2TB NVMe | WarBRD+Warthog Stick | CM3 | TM TPR's | Varjo Aero
Recommended Posts