VR Discussions, Questions & Feedback

I also reverted back to legacy mode in VR with my motion rig...
The new camera physics is nauseating for me in VR, even with every parameter set to 0 whereas Legacy mode is the most wonderful VR experience for me, and I'm really not prone to VR sickness.
Too bad because Daytona could actually become enjoyable.

 

I have the G2 facing my monitor 49" ultrawide and I need no lights on.

 

Same

 

Makes me wonder why Reiza wasted time and resources on a VR feature nobody asked for or wanted when the legacy settings were working sufficiently well. They could've the spent time/resources working on Multiplayer or other aspects of the game, eg: in game DLSS or FSR, or any other feature upgrade people have been begging for.

 

I honestly never touch or play around with it whatever camera they implemented. I read how people reversed to legacy and set certain settings back to 0 and that's what I did...don't want to get dizzy. It was fine before so I definitely don't want to mess with something that ain't broke. I think the camera settings are specifically for those that don't have motion rig so they are designed to help them move or tilt in VR....virtually, not literally.

 

This happens to me with a Quest 2 if the HMD isn't connected correctly so Link doesn't show, or Link just isn't activated - the "solution" has been to reconnect and enable Link, and then start AMS2.

 

So, just to summarize: For VR, especially those of us with VR and motion rigs, is it recommended to set "Use Legacy Mode" to "0"? Or, is the consensus that setting it to "1" is the better option? All other settings to zero as well?

On the subject, is having the camera totally locked to the car realistic? Don't our eyes act as a natural gimbal of sorts, and having the horizon bounce away in the background wrong? Or can we still compensate with our eyes as normal albeit through VR goggles? Just a thought exercise if nothing else.

Lastly, why on earth did Reiza not simply use "Enable"/"Disabled" for the setting name after "Use Legacy Mode"? Using a zero and 1 instead is the laziest piece of UI oversight ever.

 

I never touched the camera settings until after the latest update, not sure how it was before but after that update it felt very weird and the VR center was drifting a lot, also when spinning out the camera would make a sudden correction that really messed up the immersion.

Just saying this to emphasize that I don't have much experience with these settings, however to fix the issues I was getting I set head movement to 50, legacy mode to 1 and all the rest to 0. Head movement to 50 so the car movement and horizon movement are balanced, changing it to either 0 or 100 is unrealistic, like you said in real life our eyes will stabilize the horizon but only to some extent especially in racing cars with harder suspension, so you will always have both movements.

And seems like setting the other ones to zero fixed the weird sensations and sudden corrections I was experiencing.

 

G2 (and other) VR owners - sharper/better performance using original FSR upscaling mod with more extreme upscaling.

TLDR; By using 0.6 factor in mod and 180% SS in steam, you get a far better image than 0.8 factor and 100% in SteamSS (as cost of upscaling is constant, but gains can be much more) - game looks and runs beautfiullly at 90fps... bar as usual the night/wet combo. Any news on this @CrimsonEminence ?

So basically, taking a leaf out of my recent MSFS2020 experiements, it become obvious than upscaling works better when there's a bigger delta between the original and the new (to a point) and going beyond 100% res of the headset nets you a nice gain.

Full details in my updated G2/VR guide here - AMS VR G2 Settings

 

When recording my gameplay with GeForce Experience the recorded material has a huge FOV which distorts the image but in the VR headset it looks normal. Has anyone an idea what causes this?

 

I think Geforce Experience captures the monitor feed, not the headset feed. Or maybe it tries to use both eyes at once? To capture VR, use OBS and its VR plugin that captures straight from the VR image (left or right eye).

OpenVR input plugin

 

Thanks for keeping your guide up to date and continually testing it for all of us! I concur that the new approach of lowering the factor in mod, and raising Steam SS results in a better picture than before. However, I still find disabling the mod altogether is better on my PC.

I'd also like to second @CrimsonEminence providing an update for VR optimization, specifically at night and/or in the wet. Heck, ANY improvement in VR performance would be welcomed wholeheartedly!!!

 

I have to add, AMS2 ran a lot better in VR in challenging weather/day/night conditions a year ago than it does now. After November, I'm occasionally seeing issues with the CPU not keeping up (especially with spray in low light and in time trial for some reason). This wasn't present earlier.

Spoiler: System specs

10900K @ 5GHz (all 10 cores)
RTX 3090
Valve Index

 

Of course VR is demanding but there are already solutions on the market. For VR-headsets with canted displays (like my Pimax 8K+) a small patch (like rFactor2 devs deployed) could eliminate the forced use of parallel projection. This alone would bring a huge FPS-benefit.
Then there is DLSS which could also be used in VR-games and of course all kinds of optimizations which benefits for 2D and VR-users
At the moment I can't find a solution to race at rain and/or night at all in VR with my Pimax. Don't know what happened and if the problem is on my side but the FPS-drop at these conditions is that huge since the latest updates (and maybe the fact that I upgraded to Windows 11?) that I get a stutter-fest even at low settings. Before I could play at 72hz (with fluid 72 FPS) at rain or night when I reduced my FOV in Pimax Pi-Tool to "Potato"-FOV but unfortunately now it's not possible anymore (huge stuttering! making me nauseous...). I have a high-end-PC (RTX3090 and i9 10900k CPU) and get fluid 72 FPS (at low FOV) with full grid and even highest graphics settings at sunny conditions though. So at the moment I can only drive at sunny daylight in VR... It looks gorgeous but it's also a bit sad because Automobilista 2 has this great weather engine and day/night cycle. And it already worked in the past and therefore I know how amazing this looked... :-(

 

This.

 

I don't have any issues. I guess it depends on one side on the graphics settings you use, but if you say it changed recently... I can't say I have noticed.

And I sure as hell am keeping away from Windows 11 until its been out for at least a year to be sure that all the kinks have been worked out.

 

Hey guys,

I appreciate you testing this for us and sharing your findings! Keep up the good work.

I would like to get your recommendations on the following setup as to what settings to use with my specific combination :

I use an HP Reverb G2, D-BOX 4250i G3, and GTX 3090 with 9900k CPU.

Can you please share your thoughts on camera settings suitable for VR+Motion and the best currently available graphic and performance settings for my PC (there’s a lot of info here so…)

Thanks in advance,

D.

 

For some reason since a few days I have zero performance with the game. Time-trial/race it doesn't matter. I have FPS of between 30 en 50. I used to have a performance of 80 to 90.

Specs:
AMD Ryzen 5 5600X Boxed
Gigabyte Aorus B550I PRO AX
Gigabyte GeForce RTX 3060 Ti
G.Skill Flare X F4-3200C16D-32GFX
HP Reverb G2

SteamVr is on 57% Reso. SuperSampling on 1.5

Any suggestions? I'm getting frustrated, while I enjoyed this game really the last few months!

See screenshot when I enter a timetrial, before even going into the pits.

 

As you can see on the right hand side, you are CPU bound. Maybe take a look in Task Manager to see what else is using your CPU. Did you install something new a couple of days ago?