Search the Community

Hi, I am a new Aero user (posted my First Impressions last week) and so far I am really happy with it. But, I enjoy tweaking to achieve the best results. I am currently using Varjo-Foveated for DFR and it's working great. However, it's incompatible with Open XR Toolkit, and I miss some of the features it provided, such as the nicer (IMO) FPS/Latency display, post-processing tweaking, etc. Supposedly, switching to Quad-Views-Foveated instead of Varjo-Foveated allows the continued use of Open XR Toolkit. Before I mess with a working configuration, I wanted to check if anyone is using Quad-Views-Foveated for DFR with the Aero and confirm that OXRTK does indeed work. And, if so - did anyone notice any performance difference (good or bad)? If not, I'll try it when I get back from my trip and report my results back here, but I wanted to check, like I said - before I mess with a working configuration, as we all know how easy it is to end up with hours of troubleshooting. https://github.com/mbucchia/Varjo-Foveated/wiki https://github.com/mbucchia/Quad-Views-Foveated/wiki Thanks, all.

I am using pico 4 with virtual desktop and openxr toolkit and am having consistent crashes when trying to use MT and sometimes with ST. I had some similar issues with a rift s but less frequent. I have deleted shaders etc several times and have done a slow repair. I have also tried running with and without "force VR" etc., and through "injecting" the game in VD. I have attached the last three logs and would appreciate if anyone could offer any advice. 5600x/rx6700/64Gb 3200 RAM/Pico 4/virtual desktop/openxr toolkit. dcs.log-20230402-183248.zip dcs.log-20230402-183139.zip dcs.log-20230402-182258.zip

I have been testing my VR configuration/stability & visual improvements with my Pimax5k Super HMD since DCS provided OpenXR support. At first, tests where KO and could hardly just get to the flight phase. But a recent break through has occurred and has changed the testing results by 180 degrees for the better. The big game changer happened yesterday when I found out that the OpenXR Toolkit was revised to v1.2.4. to improve usability with DCS OpenXR implementation, see note 1. I will spare you the testing details and jump directly to some results/configurations that work for me. Hardware configuration: (if you wish to compare, here are my PC details) Mobo: MSI X570-A PRO/PCIe 4 CPU: AMD RYZEN 9 3900X (12 CORE) GPU: EVGA-RTX 3080Ti RAM: DDR4-32 GB (3200MHZ wt XMP) HMD: PIMAX-5K SUPER Software configuration: DCS World Open Beta v 2.8.2.35759 (latest as of 3 FEB 2023 & wt OpenXR support) PiTool v1.0.1.284v - Version 284 is required as per PimaxXR requirements. See note 1. PimaxXR v0.3.0 - This app is the runtime required for OpenXR to work with PiTool and to bypass SteamVR. PimaxXR runtime is needed to avoid PiTool kick starting SteamVR by default. Install PimaxXR and make sure that PimaxXR is selected as the OpenXR runtime. See note 2. OpenXR Toolkit v1.2.4 – Latest version as of 2 FEB 2023. See note 3. OpenXR Explorer v1.4 - Optional application to analyze OpenXR runtimes & OpenXR Toolkit app that is installed. Not required for success in implementing OpenXR with DCS. See note 4. OpenComposite - This application and its DLL implementation into DCS is not required for success in implementing OpenXR with DCS. However, you may need it for other VR games or simulators that are designed to use the SteamVR app to run them in VR. See note 6. Recommendations: Always make sure that the PiTool app is UP and running regardless of what VR runtime (SteamVR or OpenXR) you use. Otherwise, your Pimax HMD is not available for your VR sessions. If you have configured a DCS game start icon in PiTool and wish to test OpenXR runtime, avoid using that game start icon. Starting DCS from the PiTool/My games/DCS icon will kick start SteamVR. Having DCS started via SteamVR while OpenXR is configure for the game will likely cause undesired results. If you are going to run or test DCS OpenXR VR method (bypassing SteamVR), for safety, just delete the game start icon in PiTool as you will not really need it anymore. Instead, do the following… Exploit the DCS command line features to start the simulator as these will be useful to you. Make yourself some DCS game start window shortcuts to facilitate things. Here are some windows shortcut command line targets that I use. Make a DCS game start shortcut for each of the following shortcut targets & see note 5 for other DCS post link; "your game install path\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_OpenXR - to start DCS with OpenXR support. Make sure that SteamVR is not running. Make sure that OpenXR Toolkit is enabled. At first, use the default Toolkit shortcuts. Also, make sure that active OpenXR runtime is ticked back to OpenXR within the PimaxXR app. This will enable bypassing SteamVR and will avoid SteamVR from being called. "your game install path\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_SteamVR - to start DCS with SteamVR support. If you revert back to using SteamVR, make sure that the OpenXR Toolkit is disabled (tick the disable switch in OpenXR Toolkit) and that active OpenXR runtime is ticked back to STEAMVR within the PimaxXR app (start PimaxXR app and select SteamVR as the runtime). "your game install path\DCS World OpenBeta\bin\DCS.exe" --force_disable_VR – to start DCS without VR so that DCS displays on your primary display screen. This could useful for HOTAS configuration, etc. Without guaranties, this methodology should work for Pimax4k, 5k or 8k HMD owners. Can all these pieces of software & apps co-exist at the same time on your PC. YES, however, configuring the apps correctly is required if you wish to use DCS with SteamVR or with OpenXR. See comments above depending on the shortcut command lines that you are using to start the DCS simulator. You need to experiment with the OpenXR Toolkit settings. Do that using the Toolkit shortcuts while in the game. Settings will likely vary if you have a Pimax4k, 5k or 8k HMD. When your satisfied with your Toolkit settings, share them with the community by writing your own post. Using OpenXR... Generally speaking, I am getting better control of my FPS frame rates, better control of color effects and better control of sharpness inside the cockpits. Since using PimaxXR v0.3.1, stuttering when switching from F1 to F10 and back to F1 views has disappeared. Use OpenXR Toolkit to experiment with OpenXR setting while in the simulator. Use default OpenXR Toolkit shortcut combos to facilitate your setups. So far, multiplayer seems OK. Hope this helps you enjoy OpenXR with your Pimax HMD. Everest…Out! Notes: 1- For PiTool v1.0.1.284v, see https://community.openmr.com/t/pitool-1-0-1-284v/39823 Version 284v is not available for download from Pimax Support site. select the supplied link to Pimax's OpenMR community to get PiTool v1.0.1.284v. 2- For PimaxXR v0.3.0, see https://github.com/mbucchia/Pimax-OpenXR A new (unreleased as of 8 FEB 2023) version of PimaxXR is available, V0.3.1. See the following forum post to download a pre-release version of PimaxXR v0.3.1. GO TO FORUM POST LINK 3- For OpenXR Toolkit v1.2.4., see https://mbucchia.github.io/OpenXR-Toolkit/ 4- For OpenXR Explorer v1.4, see https://github.com/maluoi/openxr-explorer/releases/tag/v1.4 Be aware that this app is not required for OpenXR implementation with DCS. It is included here as reference only and is recommended for folks that do application development work. 5- For DCS news letter regarding OpenXR implementation, see the following forum post: https://forum.dcs.world/topic/318004-dcs-now-supports-openxr-natively/ 6- For OpenComposite & OpenComposite switcher, see https://mbucchia.github.io/OpenXR-Toolkit/opencomposite.html Note that no revision is mentioned for OpenComposite probably because this is actually a DLL which did the work of throwing DCS VR runtimes to PimaxXR before introduction/support of OpenXR in DCS. OpenComposite solution is no longer required to operate OpenXR in DCS.