nbates66

I seem to be matching or beating my R5 class times set 4 months ago in New Zealand fine.

I'll be that guy again, but i disagree. presuming it's not that crazy graphical bug with the rain I've seen screenshots of before.

Repeating an opinion over and over does not make it true.

Doing a VERY brief web search I came across some articles stating the following: which would probably put it in the no go category for me but that's just my personal opinion, don't want latency combined with a racing sim and the low refresh rate + latency would probably be good for making you sick.

Depending on the player a lot of things including using VR itself can shift time performance for better or worse, what is your point?

So I saw your Video and decided to do a quick cold test myself, I didn't seem to have any issues doing a quick run with no practice, but I guess that hardly proves anything... absolutely sure it's not VR fitment related? (time was around 156th-ish position but I had more than a few over or early rotations)

my MSI Armour 1070Ti gets to around 73C when playing and recording in VR on El Rodeo, I have overclocked it somewhat however to try to keep up with the demands of VR.

Do other steamVR games work? (did you hit F11 to centre the view after starting the game in Oculus?, also ensure the Dirt Rally window is active)

This is normal, Ground cover has always incurred a massive performance hit to VR Rendering in DR1.0 and DR2.0, across Occulus, SteamVR and WindowsMR devices.

I dunno, I can consistently make around 7:30 in 3 of the R5 cars and the ghosts of the fastest drivers are usually getting well ahead by the second split (pulling ahead by 4 corners in actually), a quarter of a second per corner adds up to a large difference on a 10km+ stage.

This is currently the case with all VR support on the Windows Store as far as I know - Windows store apps support only Windows Mixed Reality headsets, Since Dirt Rally 2.0's VR support didn't have work done on a layer for Windows Mixed Reality, It makes sense that it would not currently work, how about doing a bit of learning next time instead of flapping your mouth(or fingers).

If possible can you please find out the USB bus descriptions of these devices just for extra info? for example the device I had to disable was called "USB Input Device" but the description revealed it was related to the motherboard RGB controller:

Curious as to if that's also related to USB input devices I mentioned in the last post here: Does your issue also clear if you go through the USB input devices and disable them?

I've noticed this happen intermittently, I can get control back by alt+tabbing the game but if the bug occurs I won't be able to rename until I start a different event I believe.

Steam VR has two, one for all apps and then an override that works on a Per-app basis, I'm not sure it really matters however if you change both, as long as you pay attention to the final application resolution: