Firmware

Hi new user here. Running win 7 at the moment with 0.5 driver installed until there is proper win 10 support. Do I also need to update to the latest firmware or will this not support the 0.5 driver?
Thanks
 
thanks, my problem is though that this is second hand so not sure what its been flashed with, and i cant get the pc to detect the HMD 'no HMD detected' message. I dont know whether i need to update it or not as it isnt working at the momet.
 
Thanks for replying, having a bit of a nightmare with it really and can't post for support on the oculus forum until i've made 3 posts and wait for someone to upgrade my forum membership.

Specs are as follows (new build)
Windows 7 Pro
8gb RAM
I5 - 4690k CPU
MSI Gaming 5 Mobo
MSI Geforce GTX970 twin frozr

I have established no issue with the firmware its running 2.12
Havent tried with the power source as i thought that was just for an optional USB but will give it a go.

The problem is getting the pc to recognise the rift an d install a driver. The tracking camera installs fine.

On boot up i get 'service disconnected' message in the task bar and the config utility displays 'No HMD Detected, Tracker Connected'. The blue light on the headset is ON, and I can see my desk top through it on extended mode.

If i right click on desktop and go to screen resolution it displays both the generic monitor and identifies the Rift DK2. I can alter the settings and switch to extend, rotate view etc.

In device manager sometime it identifies 'Rift Dk2' under Other Devices, and sometime as 'Unknown Device'. Clicking on it tells me that there are no drivers installed. When i click on update driver it will not find it on my pc even if i direct it to the folders.

What i have tried:
Plugging HDMI cable into DVI connector - no issues, power and signal getting to rift
Plugging HDMI cable into GPU HDMI port - no issues power and signal getting to rift
Ensuring cables are all plugged in correctly
Installed drivers 0.4, 0.5 and 0.6 separately to see if I could get it working - HMD not detected
Installing older Nvidia drivers that are known to be compatible with the above - did not solve
Uninstalling and re-installing the drivers with both Oculus off, and on - did not solve
Tried all USB ports which I know are working with other devices - did not solve


So i'm at a bit of a loss for ideas really, I'm no tech expert but not completely clueless. I'm thinking it is something to do with the USB connection but its not something you can replace with another to check as it is all cased in.

Took days holiday yesterday to set it up and spent 7 hours messing with it!!

I will try with the adaptor, but if anyone else has any other suggestions i will be more than grateful!

cheers
 
the demo in config? no its greyed out as are all the tweaks to the tracker. have not tried 0.7 runtime. Can the 0.7 runtime be rolled back to 0.5 easily? was a bit nervous of trying 0.7 at the moment

Also plugging the adapter in has not solved the issue.
 
Last edited:
I would uninstall everything and have a go at 0.7. Its not ED compatible but atleast you can check if the headset is working with the latest driver.
Just uninstall everything oculus related->install 0.7 runtime->reboot->and run the config

- - - Updated - - -

Also what nvidia driver are you using? 355.98?
 
Last edited:
at the moment i have Nvidia 350.12 but have tried 355.6, 355.98, 350.12, 353.3

i take it i can uninstall and reinstall 0.5 or 0.6 once i have finished with 0.7?

update
strangely when the pc is booting up the blue light is on the headset and i can see desk top. The config utility then displays 'Service Disconnected' error and the screens in the rift turn off, although the blue light is still on. If i then click 'stop runtime' in the config the headset screens come back on. Restarting runtime turns them off again. The HMD is never detected though still
 
Last edited:
yes you can install/uninstall any sdk any time you want. Just try the full uninstall and then a clean 0.7 runtime install+reboot, just too see if config room works as it should
 
Last edited:
yes you can install/uninstall any sdk any time you want. Just try the full uninstall and then a clean 0.7 runtime install+reboot, just too see if config room works as it should

Hi
Did as you said with 0.7 and still the same problem, HMD not detected, Tracker Connected with latest Nvidia drivers.
Since then i have spoken to the person i bought it from and he had it working perfectly so unlikely a problem with the hardware.
In device manager it does show as Rift DK2 but with no driver under Other Devices. There is another entry under Oculus Vr Devices which is the tracker. Should there be one for the camera?
Also in 0.7, the light is orange not green and i cant see the desktop through it.
 
Hi
Did as you said with 0.7 and still the same problem, HMD not detected, Tracker Connected with latest Nvidia drivers.
Since then i have spoken to the person i bought it from and he had it working perfectly so unlikely a problem with the hardware.
In device manager it does show as Rift DK2 but with no driver under Other Devices. There is another entry under Oculus Vr Devices which is the tracker. Should there be one for the camera?
Also in 0.7, the light is orange not green and i cant see the desktop through it.

Yeah with 0.7 the light is orange intil you start a VR experience, then the light turns blue and the camera swicth on with a blue light too. And in 0.7 there is no desktop to watch as its not seens as a monitor anymore by windows. Thats why the 0.7 runtime
config tool and demo way is the easiest to test the pc for errors.

But that the config tool shows "no hmd detected" is really weird. I just checked my Dk2 and if i remove either the HDMI cable or the usb cable from the computer, i get the same message. But as soon as i have both in, config find the HMD instantly.

And you tested with 355.98 driver too right? I know that driver is working well. Are you admin on the pc?

On you 970 you have both HDMI and DVI right? have you tested both ports with the DK2?
 
Last edited:
didnt think elite supported above version 6, I would reinstall runtime 6 and then update firmware thats comes with runtime 6. and run the dk2 in extended mode only.
 
Yeah with 0.7 the light is orange intil you start a VR experience, then the light turns blue and the camera swicth on with a blue light too. And in 0.7 there is no desktop to watch as its not seens as a monitor anymore by windows. Thats why the 0.7 runtime
config tool and demo way is the easiest to test the pc for errors.

But that the config tool shows "no hmd detected" is really weird. I just checked my Dk2 and if i remove either the HDMI cable or the usb cable from the computer, i get the same message. But as soon as i have both in, config find the HMD instantly.

And you tested with 355.98 driver too right? I know that driver is working well. Are you admin on the pc?

On you 970 you have both HDMI and DVI right? have you tested both ports with the DK2?

yes the hdmi seems to work as on extended on the older drivers i can see the desktop to the rift so the signal gets through. i think something to do with the usb and the driver not installing. Like i say, the previous owner had no issues so it must be a software issue/conflict somewhere. Yes i am running as admin
 
Last edited:
- - - Updated - - -

didnt think elite supported above version 6, I would reinstall runtime 6 and then update firmware thats comes with runtime 6. and run the dk2 in extended mode only.

He doesnt get the DK2 to work with anything atm, thats why we are trying to rule out errors. Not ED play testing.

- - - Updated - - -

yes the hdmi seems to work as on extended on the older drivers i can see the desktop to the rift so the signal gets through. i think something to do with the usb and the driver not installing. Like i say, the previous owner had no issues so it must be a software issue/conflict somewhere. Yes i am running as admin

DK2 can be extremely sensitive to what hdmi, DVI and USB port you are using. And ofcourse what GPU driver.
But it really sounds like something is off with the USB

But it very much can be a firmware mismatch too, as suggested.
 
Last edited:
But it very much can be a firmware mismatch too, as suggested.

the firmware is 2.12 which i can obtain from the oculus folder. Trouble is, with the config utility greyed out i cant do anything with the firmware. Having said that, the latest is 2.12 which is what everybody is using as there was no update to this with 0.7.

Had enough for today, but in the morning will try unintstalling my Avira anti virus.

Thanks so much for taking the time to help me by the way - very much appreciated, i switched from xbox and built this pc purely for ED which i love, after meeting the dev team in our office (meeting again before xmas hopefully). This is a bit disappointing but not giving up!!
Goodnight all
 
Last edited:
wow this is frustrating!

uninstalled anti virus
made sure windows update is on
still wont detect hmd. It *tries* to install driver but is unsuccessful therefore it must be detecting that the USB is plugging in so dont think its a problem with the cable. Not sure why it won't install the driver. The PT and camera install fine.

Update:tried new USB cable with same results, so dk2 USB cable seems fine and ruled out.

Windows event viewer gives the following error which is something to do with the hdmi, giving me something to go on
Error: [Win32Display] WARNING: The driver was not able to return EDID for a display


 
Last edited:

mxcross2002

M
try swapping the HDMI cable for a different one , that's sorted out a lot of similar issues
 
I tried using the dvi -d port (my monitor has to go in the dvi-I port as I only have a vga/dvi -i adapter for the monitor) using the adapter that comes with the dk2 but still same issue.

Haven't tried new hdmi cable yet as don't have a spare.

Def something along these lines as that what the windows event message is trying to tell me, that something isn't right re the hdmi.

Read that some people have got it to work by taking main monitor out and using rift as primary, but that is a huge lot of faffage because it's hard navigating the desk top through the rift.

Must.....crack...on..... Sigh
 
Back
Top Bottom