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