Oculus sensor tracking and greyout flashing issues with Elite Dangerous (Oculus 1.13 & 1.14)

Alonzo Solace

A
I've been having serious issues since 2.3, but I had a lot of things change at once (Windows 10 creator update, 2.3, Nvidia updates, etc) so couldn't pin it down.

My setup is a 3770k, GTX 1070, and the recommended Inateck card. I was getting grey flashes and even complete system hangs / game crashes. I had done what the Wiki suggested, which is to use the Inateck drivers and the powershell script to switch off power saving. No joy.

After reading this thread, I tried disabling hyperthreading in BIOS on my i7-3770k. Bingo! Everything's looking good, and the 3770k @ 4.1ghz is plenty of juice to get stuff to the GPU. No further crashes, no loss of tracking or grey flashes. Not the best solution ever (I paid for those extra CPU threads!) but enough of a workaround now.
 

Strangepork

Strangepork
Talmanes said:
Hello,

I am wondering if anyone else is having this issue, and if they've come across any solutions.

My Oculus headset and single sensor work great in Oculus home, in Chronos, Dreamdeck, and other apps. I only experience problems when running Elite Dangerous. I believe these issues originated after the 1.13 update (I'm currently on version 1.14).

The problems include grey-out flashes, jerky tracking problems, and sensor issues.
I've gotten sensor errors in Oculus, which I've posted an image of here (the USB warning is due to using windows inateck drivers).


Things I've tried:

  • Verified power connected to inateck 4 port USB card plugged into my mobo.
  • I've tried plugging the headset and sensor both into the inateck card
  • plugging the sensor into my onboard USB (both 2.0 and 3.0)
  • I've also tried turning off my USB 3.0 legacy settings in the bios
  • Everything is up to date, including video drivers.
  • I read that using inateck's USB drivers cause problems (and i ran into these problems in the past) so I'm using the windows drivers for the USB card.
  • Observing CPU usage while the issues happen shows it peaking at 55%, so I don't think that's the problem.
  • set USB selective suspend setting to disabled in power management

Oculus Support Recommendations:

I've contacted support, and they requested that I run the compatibility test (which I ran & passed), ensure everything was up to date (which it is), and update to the Public Test Channel program, which updates my oculus software to 1.14 (did this too).

I explained that the problem persisted, and they suggested I re-install elite dangerous, connect the rift to another computer, and if that doesn't reveal the problem, re-install the Oculus software.

I suspect that these last recommendations will not resolve the problem, and just take up a lot of time. My guess is that it's USB related. Does anyone else have any ideas as to what could be causing this?

View attachment 118781

Specs:
Windows 10
Intel Core i7-3770k CPU @ 3.5GHz
16 GB RAM
NVIDIA GTX 1070
Oculus CV1
Click to expand...

It happens to me when my sensor is 5 feet away, not 3.5ft.
 

X-Terminator

Banned
X-Terminator
Just supposing if Inatek had cut a deal with Oculus for the Recommendations Listing and how this would go down in court!
Why do chips work that are said to be non-compatible yet those that are on the said list have problems?
They select Hyperthreading chips instead of the old Xeons and yet disabling this on i5/i7 solves the issues!
USB3 is advised yet USB2 works and even more so with extensions!
They push the "Warning your System is not-compatible" in our faces and can not choose to disable it!
Once we contact support they tell us to buy a new computer!
 
Last edited:

Talmanes

Talmanes
I'll be damned. Looks like disabling hyperthreading has fixed the greyout issue for me too. The one thing I didn't try.

I have noticed a slight drop in performance, though. I guess it's worth it to get rid of that god awful flashing.
 

kiario

kiario
I have a 12 core I7. Disabling hyperthreading, is that done in the Nvidia control panel?

Anyway, my flashes are not so frequent so I cant bother really doing any adjustments.

I hope this will get sorted though by either FD or Oculus
 

mGtRd

mGtRd
X-Terminator said:
Just supposing if Inatek had cut a deal with Oculus for the Recommendations Listing and how this would go down in court!
Why do chips work that are said to be non-compatible yet those that are on the said list have problems?
They select Hyperthreading chips instead of the old Xeons and yet disabling this on i5/i7 solves the issues!
USB3 is advised yet USB2 works and even more so with extensions!
They push the "Warning your System is not-compatible" in our faces and can not choose to disable it!
Once we contact support they tell us to buy a new computer!
Click to expand...

I got the proposed 4 slot inateck pci isb 3 card and the new oculus software doesnt not see it as usb 3!! But when i run the oculus compatibility tool it sees it as usb 3. Not oculus home though during the set up and i just press skip

I play ED just fine but it would be nice to set it up in home as well (any advise??)

I will also try hypethreading as i have the i7 4790k
 

buyback

buyback
Alonzo Solace said:
I've been having serious issues since 2.3, but I had a lot of things change at once (Windows 10 creator update, 2.3, Nvidia updates, etc) so couldn't pin it down.

My setup is a 3770k, GTX 1070, and the recommended Inateck card. I was getting grey flashes and even complete system hangs / game crashes. I had done what the Wiki suggested, which is to use the Inateck drivers and the powershell script to switch off power saving. No joy.

After reading this thread, I tried disabling hyperthreading in BIOS on my i7-3770k. Bingo! Everything's looking good, and the 3770k @ 4.1ghz is plenty of juice to get stuff to the GPU. No further crashes, no loss of tracking or grey flashes. Not the best solution ever (I paid for those extra CPU threads!) but enough of a workaround now.
Click to expand...

Interesting.... to pin it further down (I don't know the cause, it might be multiple I think)...
can you do us a favour and try what happens when you enable hyper threading again (greyouts back I guess) and then then try again with ther the OVRService.exe on (much) higher process priority with "Process Hacker 2" (nice tool, it can save that state also for reapplying everytime it runs automatically)?

I just would like to know if its something PCIe/USB/CPU BUS related or maybe just raw cpu power/hyperthreading stuff maybe more on the ED/Frontier side.
 
Last edited:

Verlaine

V
We shouldn't have to resort to disabling hyperthreading — a 15-year-old feature, which first appeared on Pentium and Xeon processors in 2002 — to get the Rift to playback as advertised. I appreciate the community-driven interim fix, but this is rediculous.
 

X-Terminator

Banned
X-Terminator
Verlaine said:
We shouldn't have to resort to disabling hyperthreading — a 15-year-old feature, which first appeared on Pentium and Xeon processors in 2002 — to get the Rift to playback as advertised. I appreciate the community-driven interim fix, but this is rediculous.
Click to expand...
You mean RIDOCULUS surely? ;)

Nah, I love it seriously! Talmanes, I bought my CV1 secondhand for £450. You need a slower computer LOL!
 
Last edited:

VR Jay Le Chardon

VR Jay Le Chardon
X-Terminator said:
You need a slower computer LOL!
Click to expand...

Says the man with twin xeons :rolleyes:

FWIW: Even though I've stopped playing elite, I was still getting bugged to heck with the sensor issue, so I tried disabling hyperthreading and it seems to have sorted it. [yesnod] Just a pity I've had to disable 50% of my effective processing power to make the CV1 work as intended [blah]
 
Last edited:

CMDR_JAMESONS

C
I spoke too soon with my fix. Flashes back worse than ever. Support contacted, who suggest some re-installlations which have not fixed things.

ED pretty unplayable in VR right now. :-(

Also support said very few people are seeing this despite this thread?
 

Kaltern

Kaltern
I was bored last night, so I installed a completely clean version of Win 10 on a spare SSD I have. I installed just the absolute minimum needed to play Elite in VR, and would you believe I have zero tracking issues, when in my main Win 10 install I do.

I also didn't update the Nvidia driver, I let the one available via Windows Update install. (I don't have that driver number to hand). If anyone has already tried to clean install windows but installed driver and other software etc, I would highly recommend not doing so, and JUST install Oculus Home. See if that helps at all, as it's possible it could be a newer Nvidia driver issue with another piece of software that we install on a regular basis.

As a result, I can play at VR High, with SS at 1.25 and PD at 1.5 with only slight drops in station (I actually don't bother with SS, but I wanted to see how far I could push it.)

If you can, try it, see if it helps.
 

TorTorden_VR

T
Sounds like perhaps a windows update to usb driver set left some hinkyness and junk, wouldn't be the first time.

So yeah if possible I recommend doing a straight reset, especially if you have changed major hardware.

Also between the occasional drivers updates, running ddu cleaner utility can really help.
Not every update but I like running it 4-5 driver updates.
 

Blian

Blian
I have reinstalled Win10 two days ago, and my situation dramatically changed. One thing caught my eye: the number of my USB ports in Device Manager were halved. This means that it is possible that one of the updates borked the usb drivers, duplicating the ports somehow. This might be worth for a look-see. I guess this can be resolved without windows reinstall by removing the USB controllers in Device Manager, then do a search for new hardware and reinstall the drivers.
 

Kaltern

Kaltern
Blian said:
I have reinstalled Win10 two days ago, and my situation dramatically changed. One thing caught my eye: the number of my USB ports in Device Manager were halved. This means that it is possible that one of the updates borked the usb drivers, duplicating the ports somehow. This might be worth for a look-see. I guess this can be resolved without windows reinstall by removing the USB controllers in Device Manager, then do a search for new hardware and reinstall the drivers.
Click to expand...

Knowing Windows... I bet it won't be quite that easy :|
 

Talmanes

Talmanes
Blian said:
I have reinstalled Win10 two days ago, and my situation dramatically changed. One thing caught my eye: the number of my USB ports in Device Manager were halved. This means that it is possible that one of the updates borked the usb drivers, duplicating the ports somehow. This might be worth for a look-see. I guess this can be resolved without windows reinstall by removing the USB controllers in Device Manager, then do a search for new hardware and reinstall the drivers.
Click to expand...

Same thing happened to me - you have to roll back your USB 3.0 drivers in order to have windows detect anything plugged into them.
 
You must log in or register to reply here.
Back
Top Bottom