Varjo Aero Issues and Workarounds
I am having same issues as reported in the other thread posted by @DKay114. I tried to reply to same thread, but Message would not go through -hence new thread. So did bunch of testing to hopefully help devs and other people having issues with Varjo Aero
So to get the game running at all I run the Varjo Base 3.10.3.25. Also in the Varjo Base settings "Compatibility: OPEN XR" must be enabled ( I have enabled both OPEN VR and OPEN XR - that is fine). If you don't enable OPEN XR the game will launch through OPEN XR and there the tracking is VERY stuttery and unplayable even in menus. When downgrading Varjo Base - after removing the newest version I had to manually delete all the Varjo USB drivers with USBDeview and only after that install the Varjo Base 3.10.3.25. I was also having issues with Eye tracking on first launch of Varjo Base after downgrade @Pumo_fin , but after getting that error and restarting computer it started to work for me.
Additionally you must download and install the OpenXR-InstanceExtensionsWrapper just like @DKay114 mentioned in previous post. If you don't do this you will have a black box in front of your view. This disables Varjo Quad view rendering (Quad views rendering would be great if it would work. It works in DCS with some tinkering and the clarity and the performance is great!)
Last step - if you use OPENXR Toolkit unselect WRC executable from the list or disable OPENXR Toolkit completely.
With all above you should get game running.
Now I did bunch of tests to see if OPENXR toolkit would work and it actually seems to partially work and would be very beneficial for the performance here. Following is my observations for any game devs reading this:
If I enable OPENXR toolkit and launch the game I can navigate the menus just fine. In OPENXR settings in-game I can also enable Eye tracking and foveated rendering and that works flawlessly. The issues start when I start loading stages. First I would get a full game crash when I start loading a stage and the "3D stage reveal" would load up. When I disable "3D stage reveal" I can enter the service area like normally and start the stage. I can also start driving the stage just fine (Note: My view would be above the car at start and shortcut to center VR view would not work. Only by pausing the game and using "Reset VR view" button would work. However when I would pause the game I would get full game crash so at the point when the Pause menu would load. Few times after starting the stage I could enter the PAUSE menu once and resume driving, but on the second pause the game would crash. When finishing the stage the game would crash fully. So effectively I would get a game crash reliably after loading into a stage and trying to open a menu.
Another note about menus. When disabling OPENXR Toolkit and running a stage and opening the PAUSE menu the menu would interact with the blurred background in a weird way. There is a video clip here. Seems like the menus are rendered in some way in the VR environment that causes issues (after loading in to stage, before and after stages menus work flawlessly).
General note about foveated setting in WRC settings: When enabling the setting the accurately rendered areas seem to point slightly in opposite directions. When I look directly ahead the accurately rendered area should be the road ahead. However with left eye I see accurate area bit to the left of the road and with right eye I see the accurate area on the right side of the road. For both eyes there is a bit of road that is accurate and most of it not. this leads in a unnatural weird feeling as one eye sees accurately and second does not and the whole image looks slightly off. The foveated render areas should overlap more with the view ahead.
I would recommend contacting Matthieu Bucchianeri (mbucchia in github) who is the author of OPENXR Toolkit. If we can get compatibility with that software, you could remove the existing foveated render option and have a working foveated rendering though OPENXR toolkit and even better eye tracking for headsets that support it. All that works already now for one stage perfectly until a menu is opened.
Hopefully this helps someone and I am looking forward of seeing improvements on next VR update!
Hopefully this helps someone and I am looking forward of seeing improvements on next VR update!
