Rfactor2 The VR thread -settings & tips

I'm noticing very high latency on the steering wheel. That is, the in game wheel takes a long time to register movement. The latency on the headset (Quest 2) is around 45ms, but on the wheel it's at least 10 times that. I don't have the same latency when running on my regular display, so it appears somehow related to VR.

Anyone familiar with this and know how to fix it?

I've tried turning of display mirroring and running windowed and borderless, but it doesn't seem to help.
 
mennow said:
Andy, i also have a 3080 card and 16 gig. My processor is an amd but i was also struggling for best quality.
I came across a tip on a site for flightsims and tried it. Now i have all things on high and have no frame troubles.
I tried 60 hz on my G2 reverb but went crazy when watching menus, everything was flickering like crazy..
But there i came across this site where i had to enter this line in steamvr so it was rendered in 45 hz.
Strange thing is that now there is no flickering like in 60 hz in wmr settings.
I am no computer specialist so i have no clue what difference this makes but i’ll post the link so you can try yourself..

https://forums.frontier.co.uk/threads/hp-reverb-g2-impressions-in-elite-dangerous.558854/

on the first page there is a tip to enter a line in steamvr, then it will render in 45 hz.
I tried it and i felt good, no flickering.
On the latest tracks like Lemans it is better than for instance Brianza.
I also tried Dirt Rally 2.0 and there it works too, i can really put all eyecandy on.

Gr Menno
Click to expand...
Thanks for this, will have a look at it later today, see if it works for me
 
hi guys! I am new to rfactor2, I would like to know if there is an updated configuration guide for vr, I am currently running hp reverb g2 + 3080. Thanks!
 
Clemenca said:
Thats not correct, i can use opencomposite also with new UI
Click to expand...

Good morning here!

Could you tell me / us, how you got it to work?
I've toyed around with it too, but got the same error message as your mates. Messed around with a few settings and even replaced the VR DLL in new UI with the one in old UI - nothing worked. I've heard the full branch, not the one Ironwolf provided, did work, but even that I couldn't get to run.

Maybe you could post your settings from the classic rf2 launcher with videocard, resolution settings, and so on?
Even the graphic settings might help here.

I'm also sitting here with a Rift S and would rather not have to use SteamVR in the endurance races I participate in, while OC also had it issues keeping the frames up under certain circumstances.
 
I dont know why three of us have no problem with opencomposite und two have this error. We have all the same settings ingame and we nearly have the same hardware (i9@5GHz, 1080+ and Rift S). Also the NV driver is the same. The funniest part is that opencomopsit worked at one of my two Teammates, and suddenly it stoped working... We tested arround a whole evening without any result. I have reached the end of my wisdom.
 
perhaps it is the parameters in the opencomposite.ini that is messing you up. Mine works fine with this;
supersampleRatio=1.6
enableLayers=true
threePartSubmit=false
useViewportStencil=false
dx10Mode=false
 
We use this parameters:
supersampleRatio=1.6
enableLayers=false
threePartSubmit=true
useViewportStencil=true
dx10Mode=false

For me and 2 Teammembers this parameters works fine. We will try an report here
 
Thats interesting, first i thought threePartSubmit was said is no longer working and was causing issues a few patches ago already.
useViewportStencil should be at "true" in my file, as it was default that way and i've never changed that. (but for me, right now, i'm getting some invalid device id error or something like that upon launching)

Could you guys tell me what your settings were in that old rf2 launcher (resolution, window mode, hz, etc)?
Maybe it's related to one of these.

Which version of OVR are you using?
 
I use this version: https://znix.xyz/OpenComposite/download.php?arch=x64

rf2.JPG
 
Tried that file, fiddled around with the .ini, tried both of you guys settings - getting that 6001 error :-(
are you maybe using older version of that ovr dll file than the one I can download from git?
 
I tried quest 2 with project car 2 (i7 7700 and gtx 2080 s)
in link mode if I go up in resolution my image is no longer fluid

this is normal with a gtx 2080 ?
 
Do you have the official Link cable or some third party cable? In case of the latter it could be the headset not playing nice nice with your USB controller. Link doesn't work well with ASMedia controllers (Oculus cable can work well though) and it can have issues with other controllers as well.

I hade issues with a third party cable (Fasgear from Amazon). Only worked at USB 2 speeds on my ASMedia controller and with the Intel controllers it started glitching - bandwidth issues and it just stopped working with one of the ports (on the same controller). With the Oculus cable I've had no such issues.
 
I succeeded by updating the ndidia driver
the result and best
Are there any specifics graphic settings for quest 2 (in rfactor2 or nvidia inspector )?
 
I remember having performance problems ie not running more than 45fps with FX 8350 in many VR games including Rfactor 2, so i upgraded to Ryzen 7 3800x but i could only run 5-10 cars at 90fps, now with Ryzen 9 5950x i can run 20-35 cars without any problems with the same RTX 2070 Super at 90fps.

But since i dont own any intel CPU's i have no idea about the performance on them (due them being too expensive to be bought and tested)
But atleast it seems the performance seems to improve between all thease 3 cpus quite drastically.
 
I’ve just got my quest 2
PC parts coming this week

I’ll try link cable & WiFi wireless mode

i9 10900k & 3080

after getting back into things I’ll update opening post at long last , it’s overdue
 
Last edited:
A weird graphical thing just started for me today. What I now see while sitting in an open cockpit car is a very thin (one pixel width?) rectangular black border at seemingly at whatever screen size is defined by the graphic resolution I've chosen in the graphics menu. It's like the edge of the menu screens remain when I'm in drive mode. I tried changing from Windowed to Borderless to Full Screen but it didn't fix it. (In fact it seems that Windowed mode is forced on even if I try to set it to Borderless or Full Screen) The upper area is most noticeable where it is silhouetted by a bright blue sky.

(Note: Today I was forced to change to the new UI in order to join an online server.)
 
Ricknau said:
A weird graphical thing just started for me today. What I now see while sitting in an open cockpit car is a very thin (one pixel width?) rectangular black border at seemingly at whatever screen size is defined by the graphic resolution I've chosen in the graphics menu. It's like the edge of the menu screens remain when I'm in drive mode. I tried changing from Windowed to Borderless to Full Screen but it didn't fix it. (In fact it seems that Windowed mode is forced on even if I try to set it to Borderless or Full Screen) The upper area is most noticeable where it is silhouetted by a bright blue sky.

(Note: Today I was forced to change to the new UI in order to join an online server.)
Click to expand...
It's been there for a while. People have reported it before.
 
You must log in or register to reply here.
Back
Top