Rfactor2 The VR thread -settings & tips

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

 

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.)

 

It's been there for a while. People have reported it before.

 

Looks like this ?
https://forum.studio-397.com/index.php?threads/black-line-in-vr.67960/

 

Yeah. Thanks. Guess we just have to wait for a fix,

 

Yes
It's in the list but we don't knows the priority level.

 

a
anybody have any clue why this gray washed out band progressively appears at the bottom of image (quest 2 + steamvr)

 

not for my config

 

FYI: The gray bar issue with the quest 2 is a result of v.25 of the PC software. Rolling back to v.23 fixes the problem.

 

how can i do for uptade at v 2.5 ?

 

For comparison

Intel Core i7 3770k @4.5GHZ Sebring alone on track 240fps
intel Core i5 9600k @4.8GHZ same conditions 380 fps
Amd 5900x @ stock clock same conditions 440fps

Somehow the new AMD cpus are really fast in rFactor2 ,at least the 12 core verion, maybe caused by the big level 3 cache. rFactor2 is bandwith depending and it could help to reduce data comunication between CPU, GPU and Ram

 

And no crashes in general? I have crashes after max 3 laps now if i´m using opencomposite
Thats quiet bad tbh because SteamVR is just to hungry performancewise

 

No, still no crashes

 

Nvidia Drivers 461.72 with Release Candidate I'm finding that after a lap or so of Spa I start seeing rapid fluctuations in fps, dropping to 72 and back up to 90 causing a jittering experience. The GPU usage remain between 62-70%. Anyone else experiencing anything like this?

 

What's the best way of recording VR?

I've been trying out OBS and using Oculus Mirror, but I don't like the performance hit. Setting rFactor to mirror mode is a bit better, except the field of view is too narrow.

 

Just quoting myself BUT if anybody experiences this issue above I seemed to have resolved it. Not sure which of these fixed it or if it was due to a combination of them:

1. Deleted the contents of the CBash & Shaders folders
2. Deleted the contents of the Cache folder in player/LocalStorage
3. Disbaled Motion Smoothing in SteamVR (I personally think this may have been the culprit)

No longer getting the constant stutters after a lap or 2 of racing. Tested this weeknd on Spa and did about 8 continuous laps without a single jitter, so I think safe to say my issue is resolved.

 

I have been having some issues with Rf2 of late (see above post where I thought I had fixed it).

What I am finding is that on racing I start getting spikes in GPU frame time and these get to the point where they become so consistent that the game becomes a stuttery mess. GPU usage doesn't go beyond 65% and CPU usage around 45% (GPU temp max 70c & CPU 60c). Things I have tried:

• Reinstall rF2 & all mods form scratch
• Lowering graphics details down (GPU usage around 50%)
• Changing XMP profile on Overclock
• Various Nvidia drivers (currently on latest 465.89)
• VR Pre-rendered frames 4 on NCP
• RC version and stable version of rF2 (typing this I realised I have not tries the old UI, so may need to try that to rule the new UI out)
• Adjusting FFB core true/false
• Uninstalling/installing: SteamVR, WMRfSVR, & WMR software
• Removing Fanaleds plugin & software
• Running the game without Simcommander software running
• Updating latest Fanatec drivers
• Uninstalled all RGB software for mobo
• W10 updated and all mobo software/BIOS up to latest versions

I feel like I have pretty much tried so many things just short of reinstalling W10 and have been entertaining the idea of memory or PSU issues. I should point out that rF2 is the ONLY game I am experiencing this BUT I wonder if it was a hardware issue, would it not effect other games? I ran MEMTEST a month or so ago with no issues.

So the game runs well on a monitor but the GPU frametime spikes occur only in VR. The things I have noticed:

• The frametime spikes occur usually after 1-2 laps of the race starting - possible memory leak caused by drivers/software?
• not replicating the HMD on the monitor decreases its prevalence
• If I press Win+Y they are less prevalent but do occur in some instances (see below)
• Even with Win+Y if I spin or crash the car, they will start and persist even when no cars around on re-joining the race
• They have no relation to graphic settings

My test bed is using the Mclaren 720 GT3 at Spa with 21xGT3-AI (all S397 official content), random grid position and starting a race with race time at default.

It's driving me insane finding what the issue is. It's a relatively new issue that I have noticed since rF2 moved to RC but I can't be certain if it was one of those updates, and if it was, surely I would not be the only person experiencing this.

So my feeling is either a driver, plugin or hardware issue is causing the spikes. Now before I look into re-installing W10 &/or investing in a PSU/RAM, I wonder if anybody here has experienced or is experiencing anything like this? I'm using a HP Reverb G1 with Steam VR set at 100% with no reprojection enabled.

EDIT: tested with old UI but issue still persists

 

Do you have all those cars visible in game? If so, try knocking it down to 10
Thats the thing that caused all my problems.

 

maybe this driver issue: https://www.nvidia.com/en-us/geforc...-index-missing-dropped-frames-since-nvidia-d/

 

I have 14 visible. I can also confirm it is occurring on the old UI.
@Manfredk2
I tried various drivers but I believe the issue has now been resolved by Nvidia.