VR Discussions, Questions & Feedback

I use h264 with link cable.

 

I'm glad you posted that. I've been dealing with that since I got the quest3 (May 2024) where both displays would just turn off for a split second and come back on and I didn't know why.

Over the past few months I've moved over to virtual desktop and recently over to hard wired network and I found I get slightly better frames using h.264+ and I haven't had this issue since.

It didn't even ring any bells in my head till you posted this.

 

Mine does the second black screen for as long as I have it. Link cable, all sims. Gonna try the h246 in debug tool tho.

 

Same for me. I use h264+ for a while now and did not have the issue since.
(Quest 3, Virtual Desktop, wired via Ethernet-to-USB-adapter, 400 Mbit/s)

 

Has the (small) issue of VR Shadows in the Cockpit "moving with the HMD" been reported does anyone know? Example; Some cars (SuperV8, McLaren GT to name two) I get shadows moving in the cockpit flooring area when I look around, like the sun is bleeding through the dashboard, thing is all other shadows are working just fine so it's not a major problem but is certainly a bug of sorts. (hard to fully describe without a video I'm aware!)

 

I can confirm that I noticed the same moving/flickering shadows inside the cockpit (especially the footwell) when moving my head in VR after v1.6.9. But I did not report as I was not sure if they have always been there.
Don't have any video evidence tho as I am too dense to record in VR and I am away from my rig at the moment.

 

Another one confirming this issue here.

 

Following a reinstall of oculus , i was relooking at my settings and i am not sure the VR Supersampling setting is working.

I usually have this at 1.2 , but if i crank it up to 2 i would expect to see some reduction in headroom and fps, but I am seeing no chance using the oculus debug tool to measure fps/headroom.

What i have noticed is that if i crack the option to two , restart and run game, if i go back to setting it is saying 2 BUT the slider is back at one .- see screenshot

Not sure if I am missing something here but it doesnt seem right?

 

This setting was kinda buggy in the past as well. I had to apply via vr settings xml in the Documents. Even then i had to open the game twice to get it applied. I use OTT per-game settings for supersampling and work flawlessly.

 

Yep that setting is notorious for not sticking after you leave the page/restart, mine is currently working correctly and I don't dare touch it or I'll have to faff about with it again

 

Definitely something up with the SS slider. Always had mine on 2.0 and couldn't work out why recently the game was looking average. After seeing this I changed the slider to 1.9 as a test, game looks great again. It might be 2.0 setting that isn't sticking, who knows.

 

If you click on arrows to change ss it will stick (well it does for me )

 

Cheers. I did the arrows to change it up to 2.0, back down and back up. It did not seem to activate at 2.0, but when I stopped at 1.9 and rebooted the game, SS activated,

 

Do not adjust super sampling in the game, only use the super sampling in your VR set and the ODT if you have guest

 

For my Quest 3 I have the resolution slider all the way to the right in Quest link and just use Oculus Tray Tool to slightly crop the parts of the image I can't see anyway and also to adjust the bandwidth. I then do a 1.2 Super Sample in game.
I've not used ODT for ages does it allow you to go beyond the maximum resolution set by the slider in the Quest link software?

 

I used to have the quest link all the way to the right also and at 90hz. Something definitely up though as I’ve had to dial back 72hz and slider back to centre on link

 

That's does sound odd.

I used to have a 4080Super and a 5800X3D and I also had the slider all the way to the right and 90hz, then used to use Oculus tray tool to crop the image to .85 on each axis and was fine running high settings in game but no in game supersampling

 

is AMS2 compatible with Oasis driver?

I'm at a loss here. With WMR's being discontinued by Microsoft , the awesome new Oasis driver came out to bring headsets like the HP Reverb G2 back from the brink of death. And it really works. But it's crashing massively after an indeterminate amount of time. I've been trouble-shooting quite a bit, even thought it might be EMI interference from the CSL DD to the headset, but no it's crashing on it's own.

Oasis driver's developer had a look at the Steam VR logs and he determined the crash isn't related to the driver. Is it possible that it could be an incompatibility between AMS2 itself and the Oasis driver?

 

After years using a flat screen monitor for this sim I've finally got myself a VR headset and oh my god! For the first time I raced 1 hour against the AI and wow, it's so freaking good, it all makes sense - the AI battles, the performance, the car feel, it's really just sensational.

I'm new to VR, I was wondering if anyone knew if there's a guide somewhere in the forum that could help me optimise the experience fully? (P.S using a Meta Quest 2)

 

Don't know if theres a guide already, but here a few things I did for my Meta Quest 3 that surely should help with yours too:

• Buy a cable with integrated power input - Doesn't need to be the exanpsive one from meta, the cheap from u-link is fine. The link connection allows a way better bitrate without the compression artifacts
• When linked via cable open in your Program Files\Oculus\Support\oculus-diagnostics folder the debug tool. Set the dynamic bitrate field to 0 and fill in the fixed bitrate field. Start with 200 and move yourself up in +100 until the image becames unstable. 500-600 should be working fine.
• in AMS2 turn off all Antialaising and motion blur. The most important setting is supersampling, you want this a maxed out as possible.

This should lead to really sharp image without compression artifacts and blury looking road textures.

I honestly like VR for a few immersive "being in the car" laps, but overall enjoy mit rig with triples more, the 180° field of view is just so much more helpful for close battles. And I can use all my rig equipment like LED flag, button box, etc