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

dape

dape
I can confirm this. beta 1.15 improves performance. ASW kicks definitely in later. Cannot comment on the flashes or greyouts as I never had any trouble with that

Edit:
No fixes witout crashing something... with 1.15 beta OBS Studio is not able to capture the mirror window. Same with Riva Tuner.
 
Last edited:

TorTorden_VR

T
I'm too getting tracking issues now, but I suspect they aren't related to oculus per say, cause I'm also getting random disconnects on EVERY usb device hooked in.
And it starting while playing last night, and without changing anything can't seem to get both sensors and hmd to stay to connected.

Haven't installed the creator update yet, but I'm being nagged about it. For now I managed to get the rift online by unplugging one sensor.

I suspect it might be because I have had to put extensions cables on one sensor and the hub with the Hotas, seperat runs.
It's sort of strange how removing the sensor without an extension cable seems to work.

But I suppose this is more of a windows, Driver issue than solely an oculus problem, and the oculus is the grain breaking the proverbial camel.

Testing with 1.15 as well and it's working for now, I too can somewhat attest to improved performance especially less stutter and judder.
 
Last edited:

mGtRd

mGtRd
Gents did oculus home/runtime updated in auto or did you manually downloaded and installed (removing the previous version)?
 

dape

dape
mGtRd said:
Gents did oculus home/runtime updated in auto or did you manually downloaded and installed (removing the previous version)?
Click to expand...

open Oculus Home, go to Settings -> Beta-Version and tick the Public Test Channel. It will then automatically download the Beta and install it. When unticking the Test Channel it will automatically download and install 1.14 again.
 

mGtRd

mGtRd
dape said:
open Oculus Home, go to Settings -> Beta-Version and tick the Public Test Channel. It will then automatically download the Beta and install it. When unticking the Test Channel it will automatically download and install 1.14 again.
Click to expand...

Great thanks will test later on tonight
 

X-Terminator

Banned
X-Terminator
mGtRd said:
Guys how big is this download?

It seems its taking forever and there is no progress bar in oculus home to know how much it has downloaded
Click to expand...
My Oculus Folder is 15.4Gb! I seen the notification that it download 2hours ago so was within that time plus I have 40Mb Fibre speed to PC via Powerline Adapter.
I also did a RESTART OCULUS in the Beta Menu as this was what got 1.12 to function properly.
However, I also used a power PC down for 30secs (unplug from wall socket) to drain USB memory (some advise you hold Power Button all that time also) just to be totally sure it was ridding the old version without having to un/re-install Oculus again (for me via 1.7Runtime to avoid SS4.2 cpu check).
However, to make sure (I maybe should not have) I Stopped the 2 Oculus Services in Task Manager. Upon Restart I could no longer start Oculus Home and it was telling me "Can't load Oculus Service - maybe it's still loading dude?" - I did not believe that was true SO I used System Restore to the previous day - which failed but upon looking at what I had it now all worked, had the latest Update as it already before the Restore plus the 2 Oculus Services were loaded so I could use VR again.
So perhaps part of this is the reason my 1.15 is running better now but I have had to use similar methods in the past which did not alter the 1.13/14 bug.

Just think if Oculus was your Local Car Dealer...

"I got a problem with the aircon only heating one side. Please fix it thanks"
30days pass after constant g and blinding at them down the phone to get your car back!
Oculus - "Hey there! We have your car ready to collect. Yup, we've put new hub caps on it and gave it a clean. We have added a connector so you can use our new Sat Nav and Rear View Parker Camera if you buy one now on our latest offer of only £500 fitted!"
Get's car back - "What was all that in aid of? Oh, the aircon now works at least!"
 
Last edited:

Talmanes

Talmanes
Verlaine said:
I still get the gray flashes with 1.15.
Click to expand...

yeah, my celebration was short lived. I re-configured my setup to how it was before they began, and lo and behold, they were back.

As mentioned earlier, my fix was to plug my HMD USB into the USB 3.0 mobo slot, and the sensor into my inateck card. I've reverted back to this work-around, and it resolves the grey flashing, but I still get regular sensor disconnects.
 

X-Terminator

Banned
X-Terminator
I've also now swapped a Startech USB2.0 PCI (not PCIe) to a Startech USB3.0 PCI (a rare card) as the former did not get recognized by Oculus and so was using my Motherboard USB2.0 for HMD & Sensor. This one works and I've since ordered Oculus Touch and the 2nd Sensor will use the now available USB2.0 slot. I don't use added SATA to this board and it adds 5Gbps across 4 slots with each getting upto 1.3Gbps. Pricy for PCI but I have no more PCIe available due to X-Fi card using my 2nd slot:
https://www.amazon.co.uk/dp/B00AWP9LMG/ref=pe_385721_37986871_TE_item

The Windows 10 built-in Drivers from July 2016 work fine even after using SLEEP MODE but this was still reported to not have been fixed for the PCIe version with same Driver Version number. It may be that you do require your USB to be cleaned up with a Power Draining as described. Nothing wrong in doing what I did exactly and even used a so called "failed" System Restore which kept the current state but loaded the Oculus 2 Services back into Task Manager (I had Stopped these and it would not run VR) - this is very odd but I can see how for something that needs updating it has to have the old stuff completely STOPPED and even BOOT the System without HMD/Sensors connected as a thorough disconnection to the previous files.

It has performed outrageously and I have had flawless tracking upto 2m away on just 1 Sensor, turning full 360 and at speed without a simply glitch at all. After a couple hours whilst in Group Mode it suddenly started to get bad tracking. I simply Logged OFF/ON and the issue was gone again. So it could be Server issues. I use IPv4 only now as iPV6 never connects yet did in Beta5.
 
Last edited:

kiario

kiario
Could it be a overheating issue of the Rift? Because I first thought yesterday with 1.15 that after 1 hour no flashes. Then they came.
 

Verlaine

V
kiario said:
Could it be a overheating issue of the Rift? Because I first thought yesterday with 1.15 that after 1 hour no flashes. Then they came.
Click to expand...

I never got the gray flashes with 1.12 and earlier but have had them with 1.13, 1.14 and 1.15 beta. My headset hasn't changed, so I don't know how overheating could be an issue. My best guess is it's something to do with the changes Oculus made to better support three sensors and 360-degree roomscale.
 

X-Terminator

Banned
X-Terminator
Hehe, not over-heating. I just discovered why mine went dodgy for a short time then cleared it by logging back in...
I had just received 7 new Win 10 Culmulative and Security Updates ready to INSTALL!
I know it is fixed for me now.
 
Last edited:

kiario

kiario
I got a reply on the Oculus forum saying to launch Elite in Oculus home instead and that will remove the greyouts.
Someone can confirm?
 

X-Terminator

Banned
X-Terminator
Is it easy to Stop Oculus Services - REBOOT - Restart Oculus Services? Worth a try if you can find the management panel for this.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom