VR Discussions, Questions & Feedback

The games VR scale is wrong and changes when you switch cars.
Get your world scale to match your real wheel size/body size then pull up near a spectator and you'll see they're about 3ft to 4ft tall.

 

Anyone tested it ?

 

Devs, VR is great in AMS2, but can you pleeeaase make the HUD config work in VR?
I know this has been reported many times already but my HUD is all over the place and it’s barely configurable in VR. Just use a VR headset (Quest3 for example) and try it yourself and you will immediately see what’s the problem… Thanks in advance!

 

It used to be possible to easily move the HUD elements using the gamepad but ever since the new hud was introduced into it's Work in Progress stage it became almost impossible to adjust it that way because the gamepad cursor is no longer visible. Especially when rendering the VR window in lower resolutions (which as a league host i have to as an easy alt-tab to check stuff before a race) it is a pain to edit the HUD.

 

Interesting. For me it is vice versa (use only mouse, no keypad). And now finally the position of hud element frames matches their virtual position, so I do not need to hunt them.

 

Since latest update I suddenly get massive framedrops in VR in AMS2 (can't even hold 72 FPS in Quest3, only around 55 FPS, whereas Beta version works like a charm...). Anyone else has a problem in VR now in NON-Beta version (=normal version)? I already verified Steam-files and let the config-files in the documents-folder generate freshly (deleted them and restarted the game) and restarted my PC and Quest3-headset. Problem stays in original version, and NO problem at all in beta version in VR... Any help/ideas?
Edit: Should I reinstall the whole game? I would like to avoid this in case the update broke the VR so that all the work with a fresh re installation would be senseless. But if anyone could confirm that Quest3 works flawless (Link cable) with latest update then the problem must be on my side and a fresh installation would make sense…

 

Take the screenshots of your VR and other relevant graphic settings from beta and compare to public/original.

I was very close myself from posting a similar "bug" only to discover (during the evidence gathering) that my settings were not quite the same (I think it may have been supersampling set much higher) that were causing the performance difference.

I'm not saying this is 100% the case for you but worth a check.

 

Thank you for your answer. Unfortunately I already did that and didn’t find a difference. I just edited my post above, asking if I should do a fresh re-installation and if someone could confirm that latest update works for him in VR (Quest3 with Link cable).

 

Please guys, does anyone have a hint for me? I only play AMS2 in VR and don't understand why it doesn't work anymore in VR in normal version since latest update (only in beta version it still works perfect as always with permanent 72 FPS in Quest3 with Link-Cable, in 72hz mode).
I even deleted the Automobilista 2 folder in Documents. Instead of 72 FPS, I only get fluctuating 40 or 50 FPS, no matter what graphics settings I use. It can't be a performance problem because my machine is strong enough to keep 72 FPS even with everything maxed to ultra settings. Even without supersampling I don't get my normal 72 FPS only a stuttering mess with fluctuating 40/50 FPS. In beta I have a permanent green line at 72 FPS in oculus tray tool graph. I have really no idea what the problem could be on my side. My only logical solution would be that the latest update broke VR that's why I'm asking if someone could confirm if VR works or is broken. If it's broken, then we all would have to wait for a fix and I could stop trying to find a problem on my side...
I'm really running out of ideas... :-(

 

Running Quest 3 with Virtual Desktop and my performance is basically the same, or slightly better thanks to the much improved smoke effects Reiza made. 72hz mode, 3060 Ti, Ryzen 7 3800x, 64 GB Ram.

 

I am new to VR but I found I got far better framerate and graphics with virtual desktop over wifi than with Oculus airlink (super blurry low res versus "realism"), so maybe the oculus link is bugged?

 

SAME ! Performance and visuals were absolute terrible no matter what i set in the debug tool. Almost gave up on VR entirely but decided to give one more try with a Wifi6 router and Virtual Desktop software. It fixed EVERYTHING for me. Slightly more latency be damned i almost do not feel it at all, visuals are crisp and performance is perfect.

 

Here all still working ok with link cable, but everytime NVIDIA drops a driver update, Meta releases an update with 50/50 chance of broke something that was working nice.

 

Okay, thank you guys. Then my last chance is full uninstall and reinstall from scratch and pray that it will work then…
Just don’t understand what the problem could be as beta version and all my other games work fine in VR…

 

Hi,
I only have a Quest 2 with a RTX 2080 Ti,
but I get top quality with at least 72 fps(without ASW),
also in multiplayer without limiting the number of cars.
Graphics settings for track and car on ultra.
I also use Virtual Desktop, but it’s wired!
Ethernet cable with an Ethernet/USB-Adapter with power injektion.
I have uninstalled Meta Software and turned off updates.
I don't use any other software/tools only VD.
Full bit rate, no latency issues or other problems.

 

Interesting that I'm also in Slovakia and report the same problem. You don't happen to have a gaming machine from Alza do you? I chickened out from building a machine and got one from them (which I'm actually pretty happy with). Just trying to work out what might be in common.

Thanks for that. I now think the scale is correct, just I'm bigger than some of the driver models displayed in the game (in VR you see more of your virtual body and it's weird if it seems smaller than your own real one).

BTW slightly off topic is there a place to say "thanks, bug fixed" for people who reported them? For example I reported the problems with the Interlagos 1976 safety car parking in the wrong place then never returning to the pits. It works now (great!) - in other areas of software the bug ticket closes when the user reports back that it's fine at their end. It also seems strange not to have a place to say thanks. But I suppose it's just unnecessary workflow for you guys.

 

I run a Quest 3 using the link cable. I have it set to 90hz, pretty much everything maxed out (not shadows as they still don't look right). Oculus resolution all the way to the right and 1.2 Supersampling and I use Oculus Tray Tool to slightly trim on the Horizontal and Vertical for the bits of the screen that can't be seen.

Mine has been fine since the latest update, I'm on a 5090 but your 4090 should still have a ton of headroom. My previous 4080super which is far less powerful card also had a a decent amount of headroom with pretty much the same settings apart from the in game supersampling being turned off.

 

Tank you very much. I fear my last chance is a complete reinstall, although I have no clue at all what’s the cause of my problem… As I said beta version and all my other VR games work fine, only AMS2 (non-beta) has this problem now and I don’t know why…

 

Do you have any custom options set in Nvidia control panel for AMS2?

I once had an issue with a different sim where no matter what i changed, nothing was noticeable, and other sims/games ran fine, after using DDU and do a clean install of my GPU driver, all worked as before.