Oculus Rift, Fall Creators update - Black Screen in Oculus and no 3D accelerated display mode

Doogz1970 · Oct 20, 2017

Hi all

I've been playing Elite for many months now - bought an Oculus Rift and X55 HOTAS. Up to date no problems.

Last night I updated Win10 to the Fall Creators update - now I get a Black Screen in Oculus and an error message saying "No 3D accelerated display mode".

I have updated and downgraded my GTX1070 (I always keep a few driver versions handy) - no change with any of them from the very latest to 3-4 versions back. I am still on Rift 1.19. I signed up for the BETA test (so am on a version without a number) - still no change,

I also get no waiting room in Oculus (you know, the one with the fireplace) ...

Would welcome any thoughts?

Cheers

CMDR Doogz

EvilMadcat · Oct 20, 2017

Go to your harddrive : C:\Program Files\Oculus\Support or the HD you install to and go in the Oculus-Driver reinstall the Driver .

EvilMadcat

dape · Oct 20, 2017

also upadted Win10 two nights ago. Everything running fine. So unfortunately no solution to your problem.

Maybe give it a try here... https://forums.oculus.com/community/categories/support

Blaze Stark · Oct 21, 2017

I think the driver re-installation as mentioned above is your best bet (Oculus driver that is). If the method above dont work, you can always go to the devicemanager and delete the oculusdriver there and than just reinstall the software.

And the obvious one: Disconnect and reconnet the Oculus, but i assume you already did this.

Doogz1970 · Oct 21, 2017

Hi all

Thanks for the suggestions ... I tried most of them - ran a repair on the Oculus software, clicked install on the Oculus . INF (not sure if this equals a full reinstall of the driver though, albeith the repair of the Oculus installation should have fixed that).

WIN10FCU (only missing a K, hey

) bought other issues too - it would regularly not start my Corsair Cue software, and bloody User Account Control was annoying too.

So, I rolled back to my previous WIN10 and things are back working. I'll wait a month or three until there are more driver updates. Oh well ....

Cheers

CMDR Doogz

VR Morgan Grimes · Oct 22, 2017

Okay, I'm going to confirm that there does appear to be an issue here.

Prior to the Creators update I could happily shut down the oculus service via oculus tray tool and still run Elite in VR so long as the HMD option was selected in the gfx settings, as of the update if there service is shutdown Elite will no longer show the HMD options under 3d, restarting the olulus service returns the situation to normal.

Not a major issue unless you actually like to have the oculus store running and taking up nearly a GB of ram for no other reason than it can, not sure what has changed but I am currently attempting to see if I can restore the prior behaviour of not needing the oculus service running.

Edit: Or am I imagining that I was able to run it in VR without the service running? I've confused myself lol...

Kerrash · Oct 22, 2017

I've just send my Rift back for the same reason. But support did read my logs so it may have been something else...

CMDR Minion Blob · Nov 2, 2017

This ComputerWorld article has a few solid suggestions on how to keep this mess (Win 10 1709 U) away for up to 1 year. I had to manually remove it, but it wanted to reinstall itself immediately (??). My entire USB device enumeration was screwed up after the update, and ED frame rate had dropped to about the 10th of what it was before (around 10 fps). Reinstalling the latest Nvidia drivers or installing the latest Beta for Oculus Home did nothing to fix this.

Strangely, Oculus Home and Star Trek Bridge Crew performed normally. Looks like it's an ED thing, as far as the Graphics are concerned. The USB device ID parameters had to be manually zeroed out in the Registry to force a renumeration for them to work.

To make matters even more ideal, Thrustmaster's entire website was down, so I couldn't check for new drivers and/or TARGET software updates.

https://www.computerworld.com/artic...-10-fall-creators-update-from-installing.html

"Wushowhide" looks promising to keep this cancer of an update off my SSD for one more year. That should be barely enough for Microsoft and FDev to figure out what's going on.

Mighty Statto · Jan 6, 2018

Hi everyone. Quick question. Has anyone found a solution to this? Not been on Elite for over 2 months, came to it today and get the no 3D driver message from elite and oculus is just showing a black screen (apart from the room guardian grid). It won't even show the oculus home. Done a remove oculus and reinstall. Updated drivers for graphics card. Can't roll back windows from the 1709 fall update as it has been over 10 days. Any ideas before I throw it out the window???

MicoNut · Jan 7, 2018

Work around

Hello,

I have the same problem after upgrading to the Fall Creators update.
The only thing that works for me, so far, is unplugging both signal cables and then plugging them in Oculus first and then the primary monitor.
The work around is reversed after the computer is rebooted. arrrg...

To be clear I unplug the Oculus and the primary monitor (I only have one)
Then I plug in the Oculus and check for video. IF it works then I plug in the main monitor.
This hasn't failed to work so far but its a pain.
Everything works OK until the computer is restarted.

Maybe its a primary monitor detecting conflict thing... idk...
I am still working on it anyway...

MicoNut · Jan 7, 2018

double post

Mighty Statto · Jan 7, 2018

Found the solution on frontiers support site. It was as simple as changing desktop resolution to something other than what it normally is and starting the game. After that return resolution to normal and everything is working as normal. Very strange but not complaining. It's fixed.

ReDsN0W92 · Jan 9, 2018

MicoNut said:
Hello,

I have the same problem after upgrading to the Fall Creators update.
The only thing that works for me, so far, is unplugging both signal cables and then plugging them in Oculus first and then the primary monitor.
The work around is reversed after the computer is rebooted. arrrg...

To be clear I unplug the Oculus and the primary monitor (I only have one)
Then I plug in the Oculus and check for video. IF it works then I plug in the main monitor.
This hasn't failed to work so far but its a pain.
Everything works OK until the computer is restarted.

Maybe its a primary monitor detecting conflict thing... idk...
I am still working on it anyway...

Made an account just to say that this is what finally worked for me after days of frustration. Thank you!

maslan · Feb 24, 2018

The only thing that actually was able to solve the problem (tried damn everything, updating/downgrading usb drivers, nvidia drivers, installing oculus drivers, testing the HDMI on a monitor, reattaching cables to oculus etc.

So the only real thing that solved my problem was rolling back windows back to 1703. FY Microsoft for making me waste entire saturday on trying to fix my oculus not on actually working and playing on it.....

MicoNut · Mar 15, 2018

The recent Oculus cert problem is just a sad thing.
With that said they did manage to fix the problem with a single small patch while also fixing the Repair installation process so no more 5GB downloads to reinstall the Oculus software.
However the update still didn't fix my Black screen problem without resorting to the video cable input trick.
The good news is that I did find something that worked for me.
Instead of using a standard HDMI cable to connect the monitor I used a DVI to HDMI adapter. $8-15 online or at a local store.
After a complete shutdown and restart the headset started working normally....