VR Discussions, Questions & Feedback

Before sim racing I played tons of Il2 Stumovik in VR.

Fixed camera to cockpit, and a mess outside with horizon everywhere, looking 360 degrees around at more than 500 km/h at 72 FPS and shaking to keep everything running.

It's my advice to train the brain to VR motion sickness or die in the process.

 

VR combined with motion can have some complex issues for sure. I've been using VR-HMD's since the early days and each VR system has presented different challenges and solutions.

Motion + Oculus Rift worked fairly well using outside-In tracking, as did the Valve Index. In both cases, the tracking sensors were mounted in a fixed position. The timing and proportionate movements seemed to sync pretty well without any special apps or in-game settings so long as they didn't include any g-force emulation effects. These systems were used with a D-box 1.5" Gen1 motion system.

When I switched to the Pimax VR Crystal Light system (Inside-Out tracking - standard), the movements were much more dramatic in the HMD. Some of that can be attributed to the weight and fit of the headset / some of it to the tracking system. During this period, I also changed to the Qubic motion system (more travel) and that also results in considerably increased head movement, however - the Qubic system also has VR Coordiante Mapping that aids in smoothing some of the motion effects within the Headset. Another option is to add fixed sensors for better outside-in tracking.

Beyond those solutions, there are various ways to use Motion Compensation, some 3rd-party apps, some use hardware sensors or both. In some cases, disabling motion-tracking within the HMD software might offer a simple solution while still providing a realistic amount of vertical / lateral movement in the HMD.

 

My problem persists even when my motion system is disabled. I only mentioned it because the solution for the sideways wobbling of the external environment is supposed to be a massively sideways-shaking cockpit, which then clashes with my motion system. As I said, Raceroom manages it without a dancing cockpit, hence my question: why doesn't it work in AMS2? I've been involved with VR since the Oculus DK1 and with sim racing since Indy 500 on the Amiga.

 

Anyone figured out how to get the config file to work again to sharpen the screen a little bit ?...oculus supersample eat too much performance on my system, so its a no go to me

 

If I'm not mistaken, this file is just a sharpening tool. You could also use the Oculus or Virtual Desktop sharpening tools.

 

Any other VR users having new issues with editing their HUDs? Now when I try to rotate its as if the rotation is being cast on to the same flat plane facing the camera. It looks like vertical and horizontal scaling which when taken to extreme levels ends up reversing the HUD image so you can end up with it upside down and/or back to front.

The only way I can now find to scale the HUD and keep it the same distance is using this method. Sadly when doing so it actually does change the axis that the HUD is going to be moved on, making positioning it correctly borderline impossible. I mean I could probably do it given enough cups of tea and anger management courses.

I'm using an xbox controller to do this as is the preferred method for VR players. It wasn't a great experience before but with enough time it was doable. This is another level of pain.

Other than that I'm loving the update! Have a good one.

 

HUB and scandalous

 

Hi all,
After a long period of non-racing, I just fire up AMS 2 in VR with my Quest 3. It starts ok in VR but as soon as I start to drive in a quick race, the view freezes and become unresponsive. I do hear the sounds of the game, but the screen has frozen up. Do I need to do something? is there a change in the way VR works with Meta and Meta Link. (I'm connected via a USB cable and Meta Link)
Is there a new DLL needed to put in the AMS2 folder somewhere?
Any help is appreciated.

it works back again but it is not a smooth experience. I get 90FPS but it stutters like crazy. Strange.

 

In VR it is very difficult to set up HUB

 

Found the issue. The Video codec was set to default somehow. Set it back to H.264 and butter smooth again.

 

As this thread grew quite large, are there official recommendations for optimal VR performance/visual clarity somewhere, or it's completely DIY? When it comes to AMS2, it's a bit difficult to put the pieces together.

 

Indeed, for me it’s way too much information. Because of that, I no longer see what actually matters

 

Visual Clarity in VR is equal to Supersampling. Performance is going from all LOW settings ingame for baseline and going higher until be happy.

The golden rule for performance in racing sims and games running in cockpit view in VR is lower the vertical field of view, you can do it in Steam VR or in your headset software, if it's possible.

 

For those who use the config file to sharpen the VR image and find it's not working with update V1.6.9.1 or are using TAA but find the in game sharpening option has minimal impact, I've found a work around by installing the following VR toolkit:-

VRToolkit | reshade-vrtoolkit

This toolkit has been around for awhile and I've tried it before in AMS2 but when using it with MSAA I didn't like the amount of shimmering it created. However it works really well now with TAA, I see no shimmering and can sharpen the image back to how it was for me in the previous build and more. I am using SteamVR with a Valve Index so I can only say it works with my setup but it's easy enough to install/remove to give it a try.

Also question for those who use a Valve Index and RTX GPU, have you found the latest Nvidia Driver 591.59 completely removes the motion smoothing support in SteamVR? I've had to roll back to Driver 581.80 to get it back.

 

The trouble with wanting anything "Official" is the requirement from Reiza to own every HMD on the market which is impractical, all they could do is have in game graphical VR Presets but then those would be very basic so would require tweaking thereafter based on your own system.

After all VR has always and no doubt will always be a very DIY procedure when it comes to performance & visuals, your PC specs will determine what you can/can't do as well as the HMD you're using. Of course that's not to say you can't take advice and try settings from others, ultimately though what works best for your system will only be known by you in the long run.

So yes whilst it is a bit of a pain to go through potentially hours of trial & error with various settings, it'll be worth it in the end and it'll be a whole lot better than anything any official guide could tell you.

 

This is still a big issue for VR PC users. Selecting HUD elements is a nightmare which is ruining the game for me.

 

It is a well known thing that you can only select elements that are visible in the screen, which make it impossible to adjust things if your screen resolution is much smaller than the VR headset. There is no need for a video, it has been like that since forever and everyone knows it, I guess it is not something easy to solve if it hasn't been solved yet