Hi,
When I Choose extend to desktop to the hmd everything works fine, the oculus screen turns on, the resolution is set. But on the configuration utility it says that there is "NO HMD DETECTED, Tracker Connected" and the games also do not recognize that there is a HMD, so I am not being able to utilize the rift. I am using the DK2, i have already updated all of my softwares and I have already reinstalled the oculus utility and drivers and still nothing. I have also switched usb drives from 2.0 to 3.0, turned the headset on and off and still nothing. I am considering formating my pc which is currently 8.1 to maybe windows 7. If anyone can help at all I will be very thankful.
0
Comments
Also, go in the Config Util and save a debug log from the Tools/Advanced menu.
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
Hi Cybereality, thanks for the help! I should also state that in Direct HMD works just fine, it recognizes the oculus, only when i switch it to extended that it stops.
Here is the information, if you need anything else let me know ! thanks agian!
System:
Intel Core i7 - 4700 hq CPU 2.40ghz
24gb ram
Windows 8.1
Nvidia Geforce GTX 780m 4gb
Driver version 347.88
Debug:
In extended desktop "NO HMD Connected" in the Oculus config but in direct to HMD it works fine
Windows 7 x64
Nvidia 347.88
i7 4790K @4.4GHz / Asus Z97 Deluxe / 2 MSI GTX970 4GB in SLI / 32GB DDR3 @2400Mhz
Turning the Rift off and on again doesn't help
Here is my debug info
So after a few hours messing about I couldn't find a solution so I reverted back to the older 0.4.4 runtime and like magic it works again.
Strange that some users report better experiences with the newer 0.5.0.1 runtimes but it fails to work or even detect the hardware for others.
Any help with this one would be appreciated thank you for reading and I hope the information is useful to someone.
i7 4790K @ 4.4Ghz with delid and Liquid metal ultra +Corsair H110i / MSI GTX1080Ti Sea Hawk / 32GB DDR3 @2400Mhz
(All rads running EK Furious Vardar F4 / F5 fans)
Sandisk Extreme for OS and Kingston SSD Now for games
Steam = http://steamcommunity.com/id/xgsdonkyboy
TS3 server = xgs.ts3.nz
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
Can you make sure your video card outputs are not using shared ports? Annnnd that you connect the rift on your primary card?
I find that running the rift in extended mode only works fully properly if you're using non-shared outputs from the display adapter.
The Rift is connected via the primary card and using the HDMI connector on the card with no adapters of any kind.
I also tried with the USB in other ports both USB3 and 2.
I even have tried a powered hub for the USB but no joy.
My main screen is connected via the primary card using the bottom DVI-D connector
With a TV Screen connected the top DVI connector again on the primary card (but when I use the Rift I disconnect the TV)
I have also tried reinstalling the current VGA driver
If you guys need any more information on my system I am happy to run what ever you need to get any answers you need.
i7 4790K @ 4.4Ghz with delid and Liquid metal ultra +Corsair H110i / MSI GTX1080Ti Sea Hawk / 32GB DDR3 @2400Mhz
(All rads running EK Furious Vardar F4 / F5 fans)
Sandisk Extreme for OS and Kingston SSD Now for games
Steam = http://steamcommunity.com/id/xgsdonkyboy
TS3 server = xgs.ts3.nz
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
Nothing like that here.
i7 4790K @ 4.4Ghz with delid and Liquid metal ultra +Corsair H110i / MSI GTX1080Ti Sea Hawk / 32GB DDR3 @2400Mhz
(All rads running EK Furious Vardar F4 / F5 fans)
Sandisk Extreme for OS and Kingston SSD Now for games
Steam = http://steamcommunity.com/id/xgsdonkyboy
TS3 server = xgs.ts3.nz
I occasionally get an explorer crash when I enable direct mode drivers to extended desktop (explorer will literally crash).
I recommend as well, going to get CRU (custom resolution utility) and running its "reset all" exe as administrator. This deletes all active monitor registry cached formats and forces windows to redetect display hardware. Sometimes this helps. Do it with the rift hdmi disconnected. MAke sure the API sees everything but the hmd first.
YMMV, I'm also using an AMD card.
Direct to Rift works fine, but as soon as I switch to extended mode it can't detect it anymore.
My monitor is running @75Hz
I am not able to connect my TV via HDMI.
I will test (and report my findings) at some point with the Rift in the DVI-I port on the primary card with 5.0.1 maybe in the next few days after the week end.
Thankyou for your help.
i7 4790K @ 4.4Ghz with delid and Liquid metal ultra +Corsair H110i / MSI GTX1080Ti Sea Hawk / 32GB DDR3 @2400Mhz
(All rads running EK Furious Vardar F4 / F5 fans)
Sandisk Extreme for OS and Kingston SSD Now for games
Steam = http://steamcommunity.com/id/xgsdonkyboy
TS3 server = xgs.ts3.nz
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
Oculus diagnostic attached
Windows event log attached
No remote desktop / screen sharing apps active
No USB video devices
No large number of monitors. Only using the laptop's built in screen + the Rift via the HDMI out
Tried uninstalling 0.5.0.1, restarting, reinstalling, restarting, with no success. Still getting the "No HMD Detected, Tracker Connected" error.
Thanks
You can enable it in the Windows display settings (extend this display) or in the Nvidia control panel (display->setup multiple display) and AMD should have something similar.
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
Er if the Rift is not detected it wont show up in the Windows display manager cos well its not detected and as such not connected.
Also if the Rift was not turned on it would say in the Oculus Configuration Utility "No Device Attached" in black rather than "NO HMD Detected" in bold red capitals.
So as you can see this is not any thing to do with us not turning our units on (I wish it was something so simple and easy to fix).
Here is screen of problem
Here is screen of Rift turned off
Also donot forget to note that this problem goes away for us if we remove 5.0.1 and reinstall 0.4.4 it works just fine.
i7 4790K @ 4.4Ghz with delid and Liquid metal ultra +Corsair H110i / MSI GTX1080Ti Sea Hawk / 32GB DDR3 @2400Mhz
(All rads running EK Furious Vardar F4 / F5 fans)
Sandisk Extreme for OS and Kingston SSD Now for games
Steam = http://steamcommunity.com/id/xgsdonkyboy
TS3 server = xgs.ts3.nz
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
the Dk2 is selected as extended and it is rotated properly.
I get a service Disconnected message prior to the NO HMD detected message
i'm using iMac with bootcamp using win8.1
after upgrading my display card driver and rift to 0.5.0.1
both direct and extend mode cannot detect HMD
Ty for mentioning this firecutter ! There's no need to downgrade the Oculus Runtime. I just had the Extended desktop issue myself and by following the steps above it was fixed. Only thing necessary was recalibrating the second screen because with the new Runtime the Oculus isn't recognized yet by the computer.
I to am having the same issues. I can run it fine in Direct HMD, but if I extend to Desktop forget about it!
My information as as follows.
Windows 8.1 64bit
GTX 980 version 350.12
24 GB Ram
Today the Oculus Rift DK2 wouldn't work in my main OS (with the red letters "No HMD detected, Tracker connected"). So I uninstalled - reinstalled, unplugged-replugged HDMI (HMDI I always have to un/plug anyway because I also got another issue, but so far it has always worked) and swapped a USB port to no avail.
I've made no changes to the setup since yesterday, when it worked. And yes the display is detected in nVidia control panel and Windows "screen resolution" dialogue, and it's enabled as extended displays. It also "works" in that the extended displays does show up in the Rift, yet it's still not detected by the Oculus Configuration Utility.
The DK2 don't work in "Direct to HMD" mode either btw.
Rebooting to my backup OS just now and there was no error in Configuration Utility, both HMD and tracker was detected. Well so far at least.
I compared the diagnostic logs from both OS'es, and I can't really see any important differences, except ofc the Rift is not listed in the main OS. Also I haven't installed the drivers for my TrackIR 5 in the backup OS, and that's basically the only difference afaik.
I guess I'll try to downgrade the Oculus runtime on my main OS next, to see if that helps. I just wanted to post this first atm.
EDIT: Downgrading to 0.4.4 worked btw.
EDIT #2: Upgrading to 0.5.0.1 again didn't work..
EDIT #3: Redownloading 0.5.0.1 results in the same md5 sum, so they're identical (I didn't reinstall this). Downgrading to 0.4.4 worked again.
EDIT #4: Minor clarification
I have been facing the same issue lately and have found a temporary fix. Though I want to mention that I am using a DK 1 on:
Windows 8.1
16 GB RAM
Nvidia 850M 4 GB
i7 4710 2.5 GHz - 3.4 GHz
Oculus Runtime 0.5.0.1
Display mode is on "Extend" and NOT "Direct"
The fix: Right-click on the desktop and choose "Screen Resolution". In Multiple Display select the "Extend these displays" instead of "Duplicate" (Now when you go to the Config Utility you will notice that the Oculus has been detected). Now is the tricky part, to display games on the Oculus screen you will need to start a game using its DirectToRift.exe (While still in EXTEND mode. Also, If you don't have one then download one, plenty of games out there), this will force the game to appear on the Oculus's Screen. It's not a perfect fix but it does the job for now until a proper fix comes out.
Note: For some reason, the Oculus extend mode works perfectly on my Mac but not on the Windows machine. Very odd.
Cyber ive been doing some testing on this and i think it may have something to do with the way windows projects to other monitors on some cards? For example when you hit WIN+P what screen does it switch to? if it doesnt switch to your rift its detecting the screen incorrectly, i can get mine to detect but not display on the correct screen.
if you wish when you respond i can post pictures and a log sheet for you.
Happy to help guys lets get this fixed.
Edit ( it will only detect in extended if i have only the main screen and the rift attached OR if i have my third monitor extended as well, i know this runtime works with some people as i have seen DK1 GTAV Vorpx videos floating around and that requires 5.0.1 so im at a loss as to why it wont work for some of us DK1 or DK2)
When you install the 0.5.0.1 Drivers and turn on the Rift it becomes the Primary display and the Oculus software cannot detect the Rift.
Simply change the primary display to another device other than the rift and all of a sudden the Oculus software detects that you have a Rift DK2 HMD.
After doing this I can now turn the Rift on and off with out problems it was just the 1st run after installing the Oculus 0.5.0.1 run time.
At least thats the way its worked for me
Win7 x64 / i7 4790K / 2 GTX970 in SLi / 32GB DDR3 / Asus z97 Deluxe
i7 4790K @ 4.4Ghz with delid and Liquid metal ultra +Corsair H110i / MSI GTX1080Ti Sea Hawk / 32GB DDR3 @2400Mhz
(All rads running EK Furious Vardar F4 / F5 fans)
Sandisk Extreme for OS and Kingston SSD Now for games
Steam = http://steamcommunity.com/id/xgsdonkyboy
TS3 server = xgs.ts3.nz
My rift has never been the Primary Display it has always been secondary or tertiary. I attempted to make the rift Primary just to change it back and was still a no go.
I tweeked what DonkyBoY did. It's primarily me going back and forth with the extended screen settings and the Oculus Utility.
Here are my specs:
Lenovo X1 Carbon
Intel Core i7 – 3667U CPU 2.0ghz
8gb ram
Windows 8.1
64-bit
Intel HD Graphics 4000
Oculus DK2
SDK 5.0.1
And here are the steps I take to get it working: http://bit.ly/HMDerror