VR Discussions, Questions & Feedback

Hey guys, today I'm getting my quest 2.
Since I find it very difficult to keep track of how best to make which settings, can you give me tips on setting up quest 2 with my 3070ti on AMS2?

so what´s about open xr? does it work with the quest 2?

 

I

i am trying to consolidate something on discord but it might take some days before I get steamvr, in Game and openxr tools best effort

lot of variables and adjustments check needed

I would post here or making a specific thread maybe

 

Hey Guys one question:

what's the matter to edit the "sharpeningstrength" in the graphicsconfigoculusdx11.xml ?
By default it's 0.00 and I've heard that it's make sense to increase it to 1.00, but I can't recognize any difference between 0 and 1.

 

Try 2.0 or 3.0 to see if you notice difference, if not, then something is wrong.

 

what exactly should change? should it be sharper?

 

yes, sharper, a lot sharper than vanilla settings. Don't forget to save your file once you've made the change

 

Has anyone ever achieved an improvement through fewer visible cars? Especially on Daytona in the infield I have severe frame drops in VR.

 

I have yes, when it first released I was gaining 6-8fps depending on the track (sunny clear weather), Daytona is notoriously tough on performance though and I have to lower settings more than other tracks when racing on it.

 

I managed going from MSAA - LOW to MSAA - MEDIUM by limiting car visibility to twelve.

 

In optimal weather conditions or at night or rain?

Doesnt do much in the 2 latters considering the car behind headlights fps killer, to me and i read for others too

 

If the headlights are causing issues then lower your rendering resolution, super-sampling amount or MSAA settings until they don't.

 

Sure reducing MSAA is an Option but given the aliasing inherited from the Madness engine it’s a NO GO for me especially in VR

 

Quest-User-Answer (but it should work for other VR-Headsets too):
I found out that the fov setting in the debug tool (via ocolus tray tool) can bring a lot of performance without noticing any visual limitations. I have my fov at 0.82 / 0.82 and therefore have quite acceptable performance even in Daytona at night with rain with full grid and all visible cars (all settings on medium, high or ultra)
My problem is more the shimmering in the distance, I haven't been able to find any solution to that yet.

-> I will post my exactly settings later

 

I limited my vertical fov as low as 0.3, something that @Ernesto_171 suggested (he uses 0.275 if I remember correctly). It's still more than I have vertically on my ultrawide and you can think it as having helmet where the vertical fov is limited. I have no need to see virtual skinny legs and even with the steering wheel, I just need to look tiny bit lower to see the whole thing. Fortunately this isn't flying simulator, so the vertical fov is really not important and easy way to get more performance out of higher settings. That is number 1 way to increase you performance, what you get with having in game graphical settings lower is minimal compared to limited the vertical fov a lot (btw. in rF2, it's not the same... not even sure yet does limiting it help in that game at all).

As for shimmering in the distance... you won't get rid all of it. Trust me, I tried tons of different things, but from what I understood, major contribution to it is the compression on Quest headsets, which you can't get rid off fully as it's going to be always either wireless or wired using usb (and not display port) and both require compression. AMS2 also seems to be have a bit extra shimmering in any case (more if you increase the sharpness).

The best results I have achieved have been with Quest 3 have been MSAA at high and not using the sharpening (you can find my full settings few pages back). I can also drive at night with headlights behind me, because I have made sure I have enough headroom to take the hit before it starts to affect the fps.

For those with Quest 3, people have told here and elsewhere that with 4080-90 you can get better performance out of it with the link cable (I guess you can run the bitrate at 940 and actually benefit from that without adverse effect then, which should limit the compression more and thus lower the shimmering at distance).

 

That's actually a neat idea and good tip thanks chaps, I already have a smaller FOV with OpenXR Toolkit to help with FPS, but I may try even smaller vertical and see whether I like the illusion of a helmet or not (never really got on with helmet cams in VR in the past).

 

is there a way to set only der vertical fov via Oculus tray tool or you have to edit it every time via oculus debug tool?

 

I at least don't know how, it's annoying (and setting those fov values in Oculus tray tool doesn't seem to work either, so I have to use the ODT to set the fov every time)

 

With glasses, I can set .675 horizontal FOV with Quest 2 without losing any FOV at max IPD setting (3). And I can run any track, no headlights, max grid with fixed 120Hz with a 3060ti. It's a must, max Quest 2 resolution.

 

Hi, is there a way to get more 3d deph in automobilista (madnes engine).
Before you all start that the 3d is good and so on. That is corret. I dont have problems with that.
Also I dont meen world scale.

But some how Automobilista 2(madnes angine) has less deph than ACC and RFACTOR2. And RF2 has the best deph. The problem is that 50m are not feeling like 50m. With Nvidia 3dvision it was called convergence. There was a hack that we could use to get 200%. It means more deph.

Lets say that in 2d you have FOV. And les FOV gives you slower feeling. The same is in VR and I wolud like to set convergence (more deph to mednes engine).

If somebody knows if this is possible, please let me know.

Thank you

Luka

 

What do you meant with "not using the sharpening"? Is it "Link sharpening = quality"?