VR Discussions, Questions & Feedback

No idea, but the thing that makes cars (or anything else) appear to be touching the ground isn't the ground, or the thing itself, but the shadow it casts.

Hence the various 'floating / flying' optical illusions you can create by putting the shadow in the wrong place :-

This Optical Illusion of Woman Floating on ‘Magic Carpet’ is Not as It Seems

Removing shadows has a similar effect. It makes things look like they're not touching when they are.

One reason I can think of where turning up graphical options removes things is when you start to run out of video ram. Or it could just be that the compression / decompression on quest 3 is making the shadows look wrong.

The more detailed your image, especially dark areas, no doubt the more limitations in the compression algorithm will be apparent. Ever tried to watch Season 8 of GoT? It's all compression artifacts.

 

With Quest 3 I believe darks are better. In Quest 2, compression + the screen itself makes things terrible. To minimize this, I set in Quest 2 itselfs the brightness to the lower level and in AMS2 no post processing (less filter contrast) and expostion to 0.8 or 0.9. Shadows looks much better after this.

A lot of shadows and fences/poles flickering are induced by contrast filter in post processing. With some supersampling and MSAA at high I can't notice It anymore.

In flat screen is hard to see all the benefits in shadows, but it's noticeable too:

 

I had the same issue when using Virtual Desktop via OpenXR/Steam Mode. Looked strange. Now I am using Oculus Link cable via Oculus Mode. For me it's much better looking.

 

For anyone who is interested there is a very good youtube channel called Benchmark Odysseys. he is currently doing testing on AMS 2. It as helped me get my system running alot better after latest update. I t seems the 4070 is now almost to weak to get good results,so iam going to wait for 50 series then upgrade.

 

Game is running with OpenComposite/OpenXR but I cannot get the OpenXR toolkit to open. The toolkit opens fine in other games. The log for the toolkit comes up empty so it must not be detecting OpenXR opening. If anybody could provide or link a solution that would be great.

 

GitHub - rodolZ80/bypass-oculus-detector: Windows Library that simulates not having the Oculus service running and having the VR Headset disconnected.

 

Thank you

 

I run in a 4070 Super in VR with good results in 1.6.

Good results in VR have infinite meanings. VR is a total mess to have a performance standard. What is great for some is terrible for others.

 

I still use flat screen when I want crisp and clear, which I do quite often. AMS2 is a beautiful sim and sometimes I just like to immerse myself in that beauty, which I can't do with my VR headset. Other times, I want to be immersed in the environment around me, then it's a VR day. But on VR day I know there are trade-offs. Someday VR will be as good as a monitor, but we're not there yet. GPU's are already priced out of reach for many, myself included, so I'm happy with what I have now, even if it's not as good as I'd like it to be.

 

Wait until we see the price of the new RTX 5090, I think $2500 is going to end up being too conservative of a forecast.

 

I tend to disagree about VR display not being there yet

take the big screen beyond the latest pimax and even my 2nd hand PSVR2 with its gorgeous micro oled gives my LG C2 a run for its money

i will visit Shiftall company in Tokyo later this month to hopefully test their new MÉGANE X headset to see what it can deliver but on paper it seems amazing

 

Yeah, TBH it seems moot to me. If real life motorsport could stop it raining or going dark then they'd never race in either. It's ruined a ton of race weekends where they can't race at all.

Cricket, cycling, Tennis. None of it would be played in the rain if they had a choice. The only people who want to get wet during sport go to a pool.

Remember those people at the bottom of the Top gear track leaderboard with the (w) next to their time? It just ruined it for them.

So why would you actively make your experience worse in a game by enabling a feature that makes it objectively worse? Especially if you need to spend 3x as much on a graphics card and cpu to make it work? Hey, if that's what people want then go at it, but I wouldn't lament not having a 5090 based on headlights or rain.

Headlights and rain are flaws IRL that didn't really need to be replicated in a game where you don't have to have them. It's like when Carmack said it made no sense replicating flaws with lens in computer graphics because there is no lens and you can create a better image. He was right but every game still does it.

And you can run a field of cars in VR with a 3060 TI in the sun - and it can be sunny all the time in VR with no consequences for the planet. Happy days.

 

lol

How about people who buys into VR because it’s the Uber immersion in Simracing?

sorry but with your reasoning then Games devs would not be motivated to improve the rendering of their Games at all

 

Well, there's a reason the vast majority of people playing in VR are using games like AC or AMS2 and not ACC and why everyone says "ACC sucks in VR" and that's because the game with the better graphics is really bad in VR.

So yeah I've been throwing my money at games that work on my hardware. I don't want Kunos to start improving the graphics in Assetto corsa so that it sucks in VR - and by the sounds of most of the comments neither does anyone else.

Of course what they want is the improved graphics and it runs well. We can all dream but it just seems obvious to me the performance would suck with these options.

As for immersion - you don't lose any not using rain or headlights. This isn't a question of immersion or not. Like I said if real life motorsport could get rid of rain they would. Just like I don't have a hammer next to my chair that I use to smash my head with if I crash - because not crashing and dying is something real motorsport would have if it could - it's not losing immersion if you remove the things IRL that suck, it's just making it better.

Next time you see Mat Anderson with sad face with his car in a ditch or being told the repairs after he ran over the grass were £6k realise that sim racing improves reality in many important respects - and all I'm saying is, for me, not having rain when you want to ride around the track is one - or playing at 9pm in the winter but it's not dark in the game is another.

I mean if you want to buy a really expensive graphics card and cpu and do it - fine.

But the sad tale lamenting in this thread now is that a 4070 super isn't fast enough based upon one guy creating a video. And IMO that's a bit silly because it's based on using game options that really don't make any sense IRL let alone in a game - but they are still there if you want them.

 

I've been playing online in VR on LFM (I recommend it, by the way). The Quest 3 is uncomfortable (I have a BoboVR M3 kit, but it's still uncomfortable), so I tried playing on the monitor again, which is actually a 42" LG OLED TV, and it was a failure. I couldn't make a curve the right way, I would have to relearn how to play on the monitor.

I went back to playing in VR and I've been getting better results. The sensation of speed is better, I can make the turn better, the sensation of space is better. The graphics aren't, but after a while and with the adrenaline of online racing, you stop noticing.

The good thing about playing online in VR is that you can see the results and the wall when they throw you out after a few meters from the start.

 

The thing that really drops performance in Madness Engine is headlights on.

Cars without headlights? I can race full grid in a thuderstorm at night, with track reflections at ultra with 90FPS.

In Quest 2 and 3, 120Hz with 60FPS does an amazing job, because you loose nothing in visuals and fluid action. ASW is nice in dark or rainy mess, closed cockpit.

VR is the art of the possible without bankrupt:

 

I had that problem too. I changed the assigned buttons to the 4 arrow keys (together with the control-key). Suddenly, the menu appeared

 

But you also crop Fov very heavily in addition to the ASW. This also works wonderfully in cars with a cabin. But if you're on open wheelers, this looks very limited. Suddenly the limitation of the Fov becomes very negative.

By the way, I do it the same way as you, only without ASW and in 72hz in the sun. I don't even need to try rain and night. I see it like @Michael3 Rain and night are luxuries in VR. In real life it's great on the TV but in the car it's much less fun. But in a simulation it is different again. We already have a lot of problems programming credible tire physics in normal sunny weather. With aquaplaning there is only a circus on the track. An incredibly difficult thing becomes impossible with today's software and hardware.

 

I lost ZERO visible horizontal "FOV" with these settings with my IPD in Quest 2. Why in hell I need to run rendering pixels that I can't see at ALL?

And in vertical, my "FOV" is bigger than a racing helmet.

So, I'm losing nothing in immersion with these settings, just more FPS for free.

VR FOV have nothing to do with 2D screen FOV. FOV in VR is fixed, and works with facial interface, lenses and display. If you can't see a pixel in display with 90hz or more (no display buffet need), and have the option to not render this pixel, GO FOR IT!

 

Hey guys,
with update 1.6 I'm experiencing frame drops at the end of multiplayer races.
I have the Quest 2 using the Oculus app.
I read some posts talking about OpenXR.
Is there any tutorial that I could guide me to run through OpenXR?
Thanks!