VR Discussions, Questions & Feedback

without a doubt, openxrtoolkit will be best.

UI is nice and you can run changes on the fly

I use it with a Q2 but also Pico N3 Link. only issue is some artefacts occurring with the latest openxr implementation it seems, when you apply FOV options

 

@MickT
I did check the log and you were correct, OC is not running. WTF am I doing wrong… I feel a fool to ask but how do I run OC then? Did the bypass DLL, OXR is running with its DLL in AMS/X64 but clearly OC not. Arrggghhh!

 

just did give it a go with my Q2.OC is kicking in and I get openxrtoolkit on display

got a META app update it seems overnight

 

I updated my OC today and now it no longer works. I get the message:

Nothing opens with OC

 

OC system wide install or single dll file in Game folder?
I use the latter and it works still for me

 

single dll in folder.... However, I have already tried to replace them, but unfortunately it didn't work.

 

That’s strange

I remember Meta broke OC few months ago with the oculus v59 update
And there is this 62 release coming in so that might be the issue?

 

It works again, I don't understand why, but it works. I have repaired the files of the respective games in Steam and then replaced the dll files again.

 

But does OC and OXR just start when you start AMS2 due to the DLLs? Are you using the bypass DLL too as I am trying to do this wired?

 

Yes and yes

 

Ok thank you for the confirmation. Perhaps then I need to do a repair as @Lt.Dan_Taylor did and add the DLLs again.

 

Hi, a rather strange issue for this game, I can't get it looking amazing in VR. My system is pretty good, but I have an unreasonable amount of headroom left:

• I7 8700k, overclocked on a Asus Z390a mobo
• MSI 4080 super
• 32gb DDR4 3600 MHz
• Quest 3

So far I have:

• Maxed all the settings out on AMS2, switched between MSAA & SSAA, SS on 2.0 (shadows are off because they look awful)
• Tweeked the sharpness in the config files
• Installed and running on OXR
• Switched to quality link sharpening, 900 dynamic bitrate and H265 in Quest debug
• Ensured quality settings is on in Geforce and link sharpening set to max

I haven't yet played around with the various sharpeners in OXR.

I'm getting a steady 90fps at night, with loads of cars on track but it still seems slightly off and I've seen people struggling to get this FPS on a 4090, so something must have gone wrong somewhere? I'm sure it can look better than this, various artefacts and overal render seems to be off. (posted this as a new thread but realised it should be here)

 

What resolution? Suggest to try resolution override in OpenXR Toolkit. The CAS sharpening at 90% is also good imo, though I am going to try FSR next

 

Hello Quest 2 / 3 users, anyone here used both SteamLink and Virtual Desktop and could tell me if VD is worth paying 20 euros for ? Since SteamLink is free and works great, it would be nice to know of VD is even better or not worth it.
EDIT: I am also connected to my PC with WLAN.

 

My PC is connected via WLAN, whereby the signal only has to pass a few centimeters through a thin inner wall. as far as I know, a wired connection is normally a prerequisite for both VD and SL. I have the feeling that the connection between VD and SL is somewhat more stable and runs more smoothly than SL. Nevertheless, I uninstalled VD again because OC and OpenVR Toolkit no longer worked for me after installing VD, although this could also be a user error.

 

Good point left that out, resolution on the quest 3 is set to max at 90fps

 

Those settings together look strange, no matter what.

So you have the render resolution in the oculus software at max and I guess 90hz is selected there ? (first things first).

I would leave the sharpening tweaks out, those are matter of taste (you can adjust them as last thing, I but I think it eventually just added a bit too much flickering (picture was a bit restless).

H265 seems to be really heavy (earlier it was suggested to use that with the slicing option off, but for me it was way too heavy with 3080), so I would first try to make everything look as good on the H264 as possible. I think with the 40xx cars you had also some third option available to try?

MSAA is max in game. I don't use the SS in game at all.

Now, usually dynamic bitrate off works better according to many. I haven't even tried it on. Set the encoding bitrate to 500 (I didn't notice any gains above that personally). Encoding resolution width is something I'm currently playing with because it seems to actually make impact, currently I have it at 4000 (that means encoding resultion is something like 4000x2260, you can see it from the performance overlay ("oculus link" type). I'm still trying going to try how high it can go and see how it impacts the performance.

AWS "off"

Oh, for me most important thing is to limit the FOV, vertical FOV in the debug tool a lot. Otherwise the performance just isn't there. I see it also a free headroom, because vertically there is so much you don't need to see during racing that it's just waste of fps to have it full.

When I started with the Quest 3 (my first headset), I had the settings in general just too high... and to me it just made worse, not just fps, but also what comes to the picture quality (probably adding compression). I suspect that you have pumped up everything to so high you actually end with worse quality.

Aim for having 30-40% headroom with other cars on track and daytime, then you should have enough headroom when it comes night / raining to avoid fps and other problems much better. Headroom is very important to get stable performance.

You won't ever get rid of all the artificats, flickering, shadow issues etc. so temper you expectations. It won't look as good as on good monitor what comes to fidelity of the picture. I had clearly way too high expections myself.

ps. try having the nvidia side at default values and optimize everything like that first to have some good baseline at least

 

So I had a fiddle with different FFR settings and also CAS vs FSR and found FSR with FFR off to give the best performance. Firstly, with CAS 90% and FFR on, I found that 1/2 and 1/4 res middle ring would give artefacts, but 1/8 or 1/16 work fine, so set 55% inner, 70% outer with 1/8 middle and 1/16 outer res. Even then, appGPU only changed about 0.5ms between FFR on and off, so don't think it's giving much performance benefit. A 3 lap race around Brands starting in early morning for 60x time progression still gave frame drops for the night to day transition with gpu usage at 100%.

Next I tried FSR at 72% with 90% sharpening and could not get FFR to work with any res giving artefacts. However, the image still looked good and gave me much better performance even with FFR off. Running the same race, held 80fps for the opening lap with gpu usage closer to 80% (on average, but very up and down). I didn't try changing render res yet and kept everything at 2500x2161.

So might stick with FSR going forward and forget about the FFR

 

Thanks for the reply on this. I've discovered a stranger issue... No changes to SS, MSAA etc. make any difference to visuals or performance. Looks and performs exactly the same whatever I do, have changed settings on and off on AMS2 and OXR and no difference.

 

agreed.

been a fan of openxrtoolkit for a while but decided to start from scratch vanilla again to push the limits of my 3080 12gb(heavily OCed too) and run some tests this afternoon on my Q2

Quest resolution pushed to MAX and 90Hz in the app

MSSA to High in Game
Car and tracks details High
Shadows Medium

using OTT to set FOV and ASW as shown here


managed to run Races with 30 AI and 12 visible, at night, with 90fps and quite smooth frametimes.
including in cockpit view with all the lights reflection and stuff coming from AI behind me.
so to make long story short, I might pause the continuous openxrtoolkit tweaking and just use these basic settings moving forward