Rfactor2 The VR thread -settings & tips

Sounds good. Looking forward to it.

 

I have a problem that has come up before and I have been able to minimize, but this time there is no way to get to an acceptable point.

What should I disable if in a circuit (ASR Bahrain) there are certain areas where the visual fluidity drops drastically even with the GPU at 50% and the CPU at 45%?

I've tried turning everything off and putting Low on all settings, when on other tracks I can go with medium or high settings.

I have noticed that this is when the circuit lights appear on the screen and it is much more drastic at night when they turn on.

Honestly, I love night racing in rF2 and I'm doing pretty well in my league, but I'm afraid I'll have to give up this race before I get seasick to a critical point.

 

This is a common issues of almost all third party tracks in rfactor2. With my Reverb G2 I can run a smooth 90fps in almost all official contents while with third party circuits it’s impossible. Even if you reduce the graphics settings to low and lower the SS you will have low fps. Lately I decided to run only official tracks .

 

The problem is that I'm in a league where I don't decide the circuits and it's the 6th race out of 10 and I'm well placed in the general classification, so I'd like to run this race anyway to minimize damage.

 

The problem is that I don't understand what I need to improve to avoid those FPS drops

 

Somewhere (I think) in player.json there is a thing that sound like "maximum visible lights" or a similar name, it is especially important at nights because it control headlights and (I think) track streetlights.

 

I found this

"Max Headlights":4,
"Max Headlights#":"Max headlights visible relative to your car.",

"Headlights On Cars":true,
"Headlights On Cars#":"Headlights illuminate other cars.",

But I think this is for car lights, not road lights. It's possible?

 

This is not an official track either!

 

It's this "Max Headlights" but if you have already 4, you already reduced it.

 

Maybe worth investigating if you own a quest 2. I've not tried it yet.
By-passes oculus dashboard and launches directly to steamvr.
https://uploadvr.com/oculuskiller-link-steamvr/

 

It's funny, but I was thinking of doing the opposite, skipping SteamVR and running it directly on Oculus to save that 20% that SteamVR consumes for nothing.

In fact, I already did some tests with the Jabbah Mod but with the problem that the ESC key cannot be used and that I cannot combine it with FSR/NIS Mod which gives me more or less the same extra performance, I decided to leave it for a while until make it finer and more complete.

Tonight I will do all the possible tests and I will go down SS until I see that it is reasonable, that I do not get sick in VR but that I can distinguish the cars around me and tomorrow night, after the race, I will try to forget that version of the circuit to forever.

Thank you all very much for your collaboration.

 

@JParra that circuit has big problems of optimization.
Have you tried to reduce the details and textures to the minimum? Just to see what happens.

 

@JParra Jabbah's latest version has corrected the escape crash bug.

 

Yes, of course, it is my first action against a circuit with performance problems.

It is the usual, the strength and weakness of rFactor, the Mods. One day you are with 20 cars and the settings are High, and the next day you are praying to be able to finish a race with everything to a minimum.

Tonight I will try more things from the player.json, from the SS, from the Nvidia panel, from the NIS or FSR Mod... and we will see.

 

Good news, I'm running to download it, thank you very much, I had reviewed it recently (v0.6.3) and it was still giving me problems.

 

After last night's unsuccessful tests, I give up and leave this. This circuit is impossible for me.

With everything on Very Low or off in rF2 (When I usually run medium/high), with high FSR compression, no SS on Oculus Home (When I usually run 4480x2256 at 72Hz) and with the game more like OutRun than a Sim of the 21st century, it continued with the problems.

In the areas where there are "no problems" everything is smooth, but in the ones that are, no matter what I do, it is horrible in VR.

I leave you a screenshot that does not show how bad it looks, nor how bad it flows, but so you can see the SteamVR graph.

Thanks to all for the help.

https://drive.google.com/uc?id=1OGo...Ehkzh6&authuser=jopame@gmail.com&usp=drive_fs

 

You can reduce rear mirror clipping distance, it help a lot, always.

 

Last night I tried to download the latest version but I couldn't find it and the issue with the esc key is still active, so I understand that the thing is still to be solved.

Also trying to test the latest DLL didn't work properly and broke my Oculus Home App on PC.

Where have you followed this and have the version correctly working?

 

I tried various configurations of the player.json regarding the graphics, I even disabled the mirrors, but nothing seems to be enough, in fact, in the video you can see that most of the time the graphic is yellow, the charge or delay does not exceed the limit of the red line.

I only have to try one thing, change to 90 Hz to see if with ASW of 45 it is more bearable. Although I doubt it's an ASW problem...

 

Not sure why it is not working. You need to disable the OpenXR toolkit for it to work as currently this seems broken.
latest version here;
https://gitlab.com/znixian/OpenOVR/-/tree/openxr