cancel
Showing results for 
Search instead for 
Did you mean: 

Direct Mode issue out of nowhere!!??

SpyderSi
Level 4
This is typical, got some friends coming over to try the Rift tonight and my Rift has suddenly developed a problem in Direct mode! These are photos of the Demo Scene and IPD Measuring tool :




... Up until tonight I've not had any problems with Direct mode, been playing iRacing with it for the last few weeks! Any ideas??
5 REPLIES 5

cybereality
Level 16
Can you list your OS, system specs, and GPU driver version?

And you wouldn't happen to be using a G-Sync monitor are your?
AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV

SpyderSi
Level 4
Hi, yes I am using a Gsync monitor, bought yesterday, didn't realise that could be a problem? i5 2500k and 780Ti 344.48 and Win 8.1

cybereality
Level 16
From what I can guess, it's some sort of conflict with G-Sync (the other person with a similar issue also had a G-Sync monitor). You can try disabling G-Sync, but I'm not sure that will actually solve anything.

Do you happen to have a normal monitor you can switch in to test? I'd like to see if this is G-Sync related.
AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV

SpyderSi
Level 4
Update: I did manage to get the rig with the Gsync monitor going, kind of! Extended mode doesn't have the misaligned screen that Direct mode does... But when in Direct mode, whilst the Demo Scene doesn't align (as in the photo above) when in iRacing it works absolutely fine! Tested TimeRifters via Steam but that had the misalignment problem... Strange!?

Anyway, did manage to demo ED and iRacing properly so that's the main thing, they guys loved it! Just hope there's a simple fix for my problem 🙂

SpyderSi
Level 4
So it seems to be a problem with 4.3 runtime for me, rolled back to 4.2 and everything is rendered normally: