Rfactor2 The VR thread -settings & tips

I could be wrong, but as far as I know this is controlled by what is driving your VR set, not the simulator or game.
Have you already tried the same test in OpenVR and see how it behaves then?
My guess is it will be working as it should, at least that is what I experience.
 
EricW said:
I could be wrong, but as far as I know this is controlled by what is driving your VR set, not the simulator or game.
Have you already tried the same test in OpenVR and see how it behaves then?
My guess is it will be working as it should, at least that is what I experience.
Click to expand...
I haven't tried it in OpenVR, just know it works in direct Oculus mode, for example pCars over steam. rF2 is the first game I played over SteamVR that's why I think the problem is somewhere there.
 
@2ndLastJedi Ok so I was wrong, those CPU numbers are great, lots of headroom. GPU should normally be at 100%, but I can think of two reasons why not. One is that you have FPS locked to 45 or 90 in VR and there is extra power left in the GPU that won't be needed due to the frame rate lock. Second would be a PCI-E bottleneck.
 
stonec said:
@2ndLastJedi Ok so I was wrong, those CPU numbers are great, lots of headroom. GPU should normally be at 100%, but I can think of two reasons why not. One is that you have FPS locked to 45 or 90 in VR and there is extra power left in the GPU that won't be needed due to the frame rate lock. Second would be a PCI-E bottleneck.
Click to expand...
Well VR locks it to 90 by itself but i do have a cap of 93 in RTSS and use Ctrl 1 to remove ASW so framerate can drop as needed without going all the way back to 45 . What would cause a PCI-E bottleneck and how to check that ?
 
Puffpirat said:
I haven't tried it in OpenVR, just know it works in direct Oculus mode, for example pCars over steam. rF2 is the first game I played over SteamVR that's why I think the problem is somewhere there.
Click to expand...

We think the same, and many others I believe.
And wether it's the implementation of SteamVR in RF2, or steamVR on it's own.... up till now it has not been a very good marriage imho.
At least not for my hardware, gtx1070, Older I7 12 core, oculus CV1.
Did some more driving tonight on the DLL and it turned into my absolute favourite.
Still have some low framerates during the starts, but i think I can improve that with the settings.
Overall it is much smoother and very connected.
Great fun
 
Yeah it's great fun. And with ASW forced it's always smooth. Would be cool if the lagginess with ASW auto would be fixed somehow, that would be the best of both worlds :)
 
If your framerate is close to 90 try Ctrl + numpad 1 to unlock the framerate and turn ASW Off !
You won't get the massive dips to 45 and framerate will just do its thing which for me is the smoother option as i generally sit close to 90 so the dips to 45 feel terrible using ASW on .
 
I think that feels even worse personally. I mean I am aiming for a constant 90+ as it's a racing game and more FPS is just better obviously, but ASW is a nice safety net, so it would be cool if it worked how its supposed to. On Sebring for example with some optimized settings it would only really kick in at the race start. From lap 2 on it's at a constant 90 as the field stretches out. That's imo what ASW is for, buffering those worst case situations.

And the dips into 45 fps shouldn't be as bad as they currently are, what you can check if you force 45FPS ASW on, way smoother, than ASW auto. Which really is my only niggle ;)
 
Puffpirat said:
I think that feels even worse personally. I mean I am aiming for a constant 90+ as it's a racing game and more FPS is just better obviously, but ASW is a nice safety net, so it would be cool if it worked how its supposed to. On Sebring for example with some optimized settings it would only really kick in at the race start. From lap 2 on it's at a constant 90 as the field stretches out. That's imo what ASW is for, buffering those worst case situations.

And the dips into 45 fps shouldn't be as bad as they currently are, what you can check if you force 45FPS ASW on, way smoother, than ASW auto. Which really is my only niggle ;)
Click to expand...
I pretty much sit in high 80's or solid 90 so when it does its ASW thing it fell instantly worse and has artifacts that I don't like .
Maybe if ASW worked better it would be a viable solution for me but atm I just Ctrl 1 and don't notice any stutters or artifacts .
Yeah ive tried ASW in all its configurations and having it Off works best for me .
 
Ok I'll try the off setting too :)

I just wanted to point out a flaw in the system, which is either on rFactors or SteamVRs rendering side. I was hoping a dev would read it and acknowledge the problem, because if it's SteamVR related I guess it's easier for a dev to point this out to Valve than for me as a mere player :)

I have friends in my league that play rf2 on not so powerful hardware and they say it drives well (physics) but performance in VR is bad. Which it isn't, it just feels bad. I brought the forced ASW option forward to them and some are way happier now. Constant 90 fps isn't really an option below a 1080Ti sadly.
 
patrickkluiters said:
Whats is ASW?
I don 't have VR but triples. Neverthless it is interessting to get a better fps and get rid of the envorimental stuttering.
Click to expand...

"Asynchronous Spacewarp (ASW) is a frame-rate smoothing technique that almost halves the CPU/GPU time required to produce nearly the same output from the same content. Like Asynchronous Timewarp (ATW), ASW is automatic and enabled without any additional effort from developers."


FYI it's VR only not available for triples.
 
I'm quite late with this. Sorry.... but just to clarify, do I copy openvr_api (32-bit) to bin32 or just to rf2 folder? I understand openvr_api (64-bit) would be to bin64.

Or should it be:
for 64-bit, copy only 64-bit version to both folders: rF2 and bin64,
for 32-bit, copy only 32-bit version to both folders : rF2 and bin32?
 
Last edited:
sherpa25 said:
I'm quite late with this. Sorry.... but just to clarify, do I copy openvr_api (32-bit) to bin32 or just to rf2 folder? I understand openvr_api (64-bit) would be to bin64.

Or should it be:
for 64-bit, copy only 64-bit version to both folders: rF2 and bin64,
for 32-bit, copy only 32-bit version to both folders : rF2 and bin32?
Click to expand...

You just need the 64-bit DLL, placed in the rfactor2 folder overwriting the original (back up first) and the Bin64 folder again backing up the original first.
 
Sometimes ASW doesn't work for me. I get 50-60 fps and therefore stuttering with "forced ASW"- or "Auto"-setting, instead of constant 45fps. This behaviour seems random, sometimes forced ASW does work and I get 45 fps.
This problem only occurs in rF2. It doesn't matter if I use SteamVR or the new OpenComposite dll.
 
elbo said:
https://uploadvr.com/openvr-for-oculus-vr-lets-you-play-steamvr-games-through-oculus-runtime/

Would this work for us oculus folks on RF2 to avoid having steamVR run?
Click to expand...

Well clearly i am doing something wrong. With steamvr i'm getting 90 FPS and 50% clearance. With this ini file i get 45 FPS and -35% clearance. I replace the ini file in the main directory and bin64.
Maybe something to do with opencomposite.ini? I don't understand that part, I haven't done anything with that.

On startup, OpenComposite searches for a file named opencomposite.ini, first next to the openvr_api.dll file, and if it can't find
that, then it looks in the working directory (usually in the same folder as the EXE). If no file is found, that's fine and all
the default values are used.

No idea what they mean.
 
You must log in or register to reply here.
Back
Top