Recent Discussions
After 1.9, no longer allows VR on WMR HMD's like HP Reverb and Samsung Odyssey
I'm on a Samsung headset and I'm reading from HP Reverb users that they can longer play in VR either. Why do we have to wait for a prompt? Why can't EA WRC just see if an OpenXR runtime exists on the system and, if so, add an option in the menu to switch to VR? Or allow us to force via command line
VR crashes with Varjo Aero
Ok, looks like no WRC VR soup for me for now. Game crashes with Varjo set to handle OpenXR after the first screen where it's asking if I'd like to play in VR. With SteamVR set to be OpenXR game manages to start, with horrible stutters when turning head, and crashes when I try to start a time trial. In both cases the crash is silent, with no pop-up window messages, simply goes back to Steam. AMD 5900X, 64G RAM, and a 4090. Both DR and RD2 work fine as they used to; so hopefully it's not a problem with my setup. Update: Managed to get it working in SteamVR OpenXR. Horrible stutters when turning head but otherwise it runs, although doesn't look very good. I think disabling the OpenXR Toolkit globally is what did the trick. It still crashes when Varjo Base is set as the OpenXR runtime which is where I'd like it to actually work, as I'm guessing having SteamVR in the middle is the cause of the very bad stutters when turning head.
Native HMD OpenXR
For owners of headsets from Varjo, Pimax, HP and possibly others too their native OpenXR runtimes are not working correctly. Currently the only way for us to get the game running is by switching runtimes and this is sub-optimal for performance. For me using a Pimax Crystal this can result in up to a 20% loss in performance. This also requires a dance of option changes between the different apps I run just to get WRC working and to get everything reset after use. What I would hope is for OpenXR to not be specific to just Steam and Meta. Everything else I run that is OpenXR based works as expected with all OXR runtimes and layers. For what it's worth here are my findings trying to use the native runtime for the Pimax Crystal: The game will start and menus etc in the floating theater show correctly, this actually runs 90fps compared to Steams XR which can be around 70fps and stuttery in this mode, native is far better for these theater modes. When a stage is started the hmd will switch into stereo 3D BUT will flicker between eyes and not react to head position movement with what looks like a window within a window.
Deferred rendering is the wrong choice.
VR beta currently has horrific performance issues and ungodly requirements to present a usable image in VR. This is not VR headset specific, I have access to rift cv1, quest 2, quest 3, neo 3 link and Pico 4 and have been in VR since dk2 headset. Currently, the obvious choice for my own use right now is neo 3 link due to higher resolution than the cv1 and the all important display port capability compared to quests and Pico 4. This is a native steam vr headset, no extra runtime involved, steam vr as openXRruntime performance is near identical to using VDXR from virtual desktop with the heaviest game there is being msfs2020, so this is not a system, runtime or headset issue. No matter the quality that can be achieved with any headset in any other vr situations, the WRC VR beta is woeful in its presentation. Firstly, deferred rendering in unreal engine for a VR title is just a development sin, it will forever have performance issues due to higher VR resolutions and always present a muddy, blurry image that's impossible to solve the horrific aliasing without adding further blur from the only option of UEs temporal Anti aliasing. Upscaling in VR is also just not suitable, as even in the best case situation of making stable 90fps and a high resolution, it will always produce artifacts which undo any of the benefits it may give to lowering frametimes. The issue is twofold, deferred rending the biggest issue, secondly, even if people are currently sacrificing every last bit of visuals to run this title at 90hz, there is a constant stutter presented as GPU framedrop in VR, this seems to be shader compilation or something along the lines of streamed assets as this can be cleared and smooth if restarting the stage and driving the exact same distance. If you back out to main menu and back into same stage, the stutter is still present, this happens in non vr mode also and was a reason I returned game for on release. So right now, I seriously can't recommend anyone ever play this title in VR given the serious optimisation issues with the deferred rendering method and ontop of that, frame drop issues even when running in horrible low resolution, low settings and low refresh rates. My system is a 12700k and 3080ti and as mentioned, no matter which headset and which render resolution set, the VR mode is just unusable visually and not enjoyable, any game settings above ultra low will fill all 12gb of vram for a native render resolution of quest 2 / pico neo 3 link. Attempted corrections and tweaks are useless, forcing dx11 is no better, I've tried everything I can but sadly the only way I see this getting better is simply scrapping the idea of deferred rending in the VR mode. Rant video already made, some swearing but after the fantastic work done elsewhere it's incredibly disheartening to know it's practically doomed if continuing in current state https://youtu.be/c3AQ_S7tvT0?si=k3qPfVOcrq2kmmPrFishbowl effect/misaligned stereoscopic view
When entering a stage, the stereoscopic view is badly misaligned. It looks like the two views for left and right eye are not overlapping correctly - like looking through a fishbowl. The problem occurs when using any upscaler (temporal, fidelity FX, DLSS). Does not occur with uspcalers off. When I use OpenXR Toolkit, I can use upscalers without problem. But the game crashes often, particularly when opening the menu on stage.
OpenXR motion compensation not working
I'm using a motion platform controlled by SimHub, which incorporates motion compensation from an OpenXR API layer. Enabling this layer crashes the game to desktop before it starts. Everything else works, only the OpenXR motion compensation layer doesn't. It's an OpenXR API layer, which works flawlessly in all other titles I've tried it in, so this could likely be an issue with the OpenXR-implementation of WRC. Is the game compatible with OpenXR API layers? Using a Meta Quest 2.OpenXR Toolkit Works When it Feels Like It
Hi, I've been enjoying this title in VR but it takes a fair bit of fiddling to get it to look right. Without OpenXR Toolkit my system struggles to run at 80fps with settings in low. When I have OpenXR running it looks amazing. So far I've found that OpenXR Toolkit runs when I am doing tutorials and when I come out of the tutorial it usually allows me to enter a tine trial stage. After completing a stage I quit and the game crashes. I then re-launch the game and it crashes when I'm loading into a stage. I close the game and repeat and one in three tries will load the stage but it crashes when I finish and quit. Why is this? The game can clearly run OpenXR Toolkit but it's just not working properly. It's a shame because without it the game looks like a PSVR1 title. I'm struggling to play it whilst it's this bad. Do we know if there is any kind of update/patch coming to fix the issues? My PC is a 7900XTX GPU and a 7800X3D CPU with 32gb DDR5
We shouldn't have to use the keyboard in VR
First, we have to select that we want to play in VR, and can only select this with the keyboard it seems; is there no way to default to VR? Then when we get to the first screen, we have to hit Enter to proceed and can only hit Enter. This should be possible with our default input device; wheel button for instance. Thanks!
Anti-Aliasing >= High Makes Game VERY Blury
Issue With anti-aliasing set to low or medium, the game is harsh looking and shimmering is visible along the edges of assets, especially apparent with trees and foliage. With anti-aliasing set to high or greater, everything becomes incredibly blurry. Hardware GPU: 4080 CPU: 13700K Headset: Valve Index Relevant In-Game Settings Anisotrophic Filtering: 4x Foveated Rendering Strength: 1 Upscaller: Off Relevant SteamVR Settings Overall Resolution Per Eye: 100% WRC Resolution Per Eye: 190%
VR still does not work with Reverb G2 in new Patch
I expected the latest patch to fix proper OpenXR (without SteamVR) for WMR headsets but it appears to still be broken. This whole game has been a scam that I can't even get a refund for. Bought it for the announced VR support and played on deck to tie me over and now VR doesn't work for months and it doesn't even work on Steam Deck anymore either. can't even get a refund for this unplayable pile of junk.Pimax Crystal settings (no steamvr)
Well... I made OpenXR toolkit work and had DFR working too but even if I can start a race when I finish it the game crashes so I am back to square one. ☹️ As of now, I am not using steamVR; In openxr toolkit I have WRC unchecked. In PimaxXR app I have PimaxXR selected as the active openXR runtime. Opencomposite can be left as is. In Pimax app set your render resolution to 0.75 ( you won't be able to get decent fps with higher res unless you have a 5090) In game foveated rendering is set to 3 Other In game settings: AA set to High ( anything lower and trees look bad) Upscale OFF!!! Advanced settings; quality preset is set to LOW manually set: Fog ON Ground cover to medium Trees to high Dynamic objects to medium Track to medium If you use steamVR you might be able to run upscaling. DLSS looked the best but it still makes the image blurry so might be better to have this off and just lower the resolution to 0.75 as I mentioned already. I did not experiment with too many other options yet. Feel free to give us your input. I tried to keep a more or less decent visual that's why some settings are manually set to medium-high. Otherwise, the game looks like RBR...