I knew the dreaded day would come. It had to be today tho...

blastard

blastard
Hi commanders,

Booted up the pc earlier for a bit of gamaplay and my rift has thrown a major wobbler. Was perfect up to now and I've changed nothing since playing last night. CV1 wouldn't center when in the oculus home view. Image kept drifting around as though wasn't talking to tracking camera.
Its had been faultless since i originally set it up. Everything has always been up to date. Now if I look directly at the sensor the rift view is looking backwards. I have to turn away from the sensor to even catch site of the oculus menu (which should be straight ahead) before the view starts moving about by itself.
Tried everything from swapping usb's around, checking usb connections and cables for damage etc but cant get the rift view looking forwards and stable. Just keeps flitting about. Its always starts up looking rearwards and off to the side before doing its own thing. Ive tried using oculus settings to try and reset the view but even that is so off center and constantly on the move. It made no difference.
Oculus home says my rift and sensor are connected and the white led's are lit on both devices. even uninstalled oculus and reinstalled+setup. Same problem was there from the moment the rift came to life. Both devices connected ok but still no stable view and tracking.

I suspect my sensor may be kaput but its £100 for another so a fair amount to gamble if it turns out to be lead or rift. Another lead is nearly £50 - although mine looks undamaged.
Has anyone else experienced this kind of ' no proper tracking and failure to focus on the sensor' problem?

I'm grounded without it (and its my birthday today). I may end up spending all my money on another rift as i won't wait weeks if I have to send it back etc.

the upset CMDR Blastard
 
Last edited:

blastard

blastard
Verlaine said:
Have you tried re-doing the sensor setup through the Oculus app?
Click to expand...

Tried to but you have to complete that while in the rift, and I cant get a stable fixed view in rift to complete the setup. Its as though the rift doesn't really know where the sensor is.
 

Blian

Blian
Check the connection in the headset itself. Take off the foamy frame, and underneath there is a hdmi connector where the cable goes. Pull it out and plug in again, maybe it came loose. It is a long shot, but what do you know.
 
Last edited:

Hell Razor5543

H
Although it make take a couple of weeks to get a replacement unit I would DEFINITELY contact Oculus. My first CV1 started playing up (lost the sound from the right speaker), and after a few checks I sent it back (they sent me a pre-paid label via e-mail), and the replacement (which was new) came back within a fortnight. Back in April the replacement had the same fault develop, and they replaced that within a fortnight or so.

Prior to asking me to send it back they did clearly explain how to run some tests on the Rift CV1. That could help.
 

Kaltern

Kaltern
(This post is just to try and help, and is in no way assuming you've not done anything I am about to mention - unfortunately I don't know exactly what you've done, so it's easier to just go through steps :) I hate Tech Support asking if it's plugged in, even though I have first hand experience of that being the exact reason someone's printer wasn't working once....)

* What happens when you try to recalibrate the sensor - what do you see in the Rift?
* Is the position of the sensor the same in virtual space as it is in real space? Does the 'scanning beam' look correct or is that also 'wrong'?
* Have you cleaned the sensor?
* Unplug the sensor. Turn your PC off completely. Disconnect from the power cable. (trust me, this is NOT a waste of time.). Hold the power button down for 30 seconds (I promise, I'm not winding you up.). Release, plug back in and power up. Wait until Windows is all loaded, and HDD is more or less idle. Open Oculus Home, go to Devices, and confirm the sensor is not found. Plug the sensor in, and see what it reports as - USB2, USB3 or nothing. If nothing, is there a USB malfunction message from Windows?

If there is, Go to Device Manager, uninstall the sensor from the USB device list (I don't remember it's exact name). Once done, uninstall Oculus software, reboot, reinstall without the sensor plugged in, then see if it works.

* If the sensor showed as USB2, try using a different USB3 port. If this STILL makes no difference, try a USB 2 port. Some motherboards are especially finicky with USB ports and the sensor, even if you use a USB extender.

If all the above fails, I would RMA the entire Rift package. Unless you have access to another sensor, and the sensor you have isn't showing any obvious signs of fault, then it;s entierly possibly the Rift is the faulty component, as you have correctly deduced. Oculus are usually pretty good, but they DO seem to take some time unfortunately.

I hope this helps. Let me know if there;s any good or bad news :)
 

Orvidius

Orvidius
When I was forced to rebuild my computer (motherboard died), and set up the Rift on the new hardware, at first I had all sorts of tracking problems. Everything was fine on my older, slower computer, but wasn't performing well on the newer hardware.

I always had a sensor that reported "poor tracking performance", but it never seemed to impact anything until the rebuild. Tech support kept suggesting that I replace the extension cables, or take everything to a friend's place and try the sensors and/or headset with his gear, etc.

The thing that they should have suggested, and would have saved everyone's time, is to just point out USB saturation. Most of the time, you have 4 USB ports to a controller. The sensors are very high bandwidth, and putting two or more of the Rift's components on the same controller can cause tracking problems. As soon as I spread the connectors out, instead of plugging them in next to one another, everything started working again. Now I use a multi-controller USB card (4x PCIe, about $80), that gives each port its own controller, so that they don't interfere with one another. Works great.

EDIT: This is the card I was mentioning: StarTech.com SuperSpeed USB 3.0 PCI Express Card with SATA Power. The caveat is mine came with one bad port, but I didn't care, since I could plug in all three of my sensors on it, and plug the headset into the motherboard's backplane, and everything runs smoothly.
 
Last edited:

kiario

kiario
Try in another pc perhaps to rule out yours?
No dirt on any of the sensors in the hmd or sensor?
 
Last edited:

blastard

blastard
Blian said:
Check the connection in the headset itself. Take off the foamy frame, and underneath there is a hdmi connector where the cable goes. Pull it out and plug in again, maybe it came loose. It is a long shot, but what do you know.
Click to expand...

Hi Blian, yes I tried that. Checking all the connections was one of the first things I did. All secure.
 

blastard

blastard
Kaltern said:
(This post is just to try and help, and is in no way assuming you've not done anything I am about to mention - unfortunately I don't know exactly what you've done, so it's easier to just go through steps :) I hate Tech Support asking if it's plugged in, even though I have first hand experience of that being the exact reason someone's printer wasn't working once....)

* What happens when you try to recalibrate the sensor - what do you see in the Rift?
* Is the position of the sensor the same in virtual space as it is in real space? Does the 'scanning beam' look correct or is that also 'wrong'?
* Have you cleaned the sensor?
* Unplug the sensor. Turn your PC off completely. Disconnect from the power cable. (trust me, this is NOT a waste of time.). Hold the power button down for 30 seconds (I promise, I'm not winding you up.). Release, plug back in and power up. Wait until Windows is all loaded, and HDD is more or less idle. Open Oculus Home, go to Devices, and confirm the sensor is not found. Plug the sensor in, and see what it reports as - USB2, USB3 or nothing. If nothing, is there a USB malfunction message from Windows?

If there is, Go to Device Manager, uninstall the sensor from the USB device list (I don't remember it's exact name). Once done, uninstall Oculus software, reboot, reinstall without the sensor plugged in, then see if it works.

* If the sensor showed as USB2, try using a different USB3 port. If this STILL makes no difference, try a USB 2 port. Some motherboards are especially finicky with USB ports and the sensor, even if you use a USB extender.

If all the above fails, I would RMA the entire Rift package. Unless you have access to another sensor, and the sensor you have isn't showing any obvious signs of fault, then it;s entierly possibly the Rift is the faulty component, as you have correctly deduced. Oculus are usually pretty good, but they DO seem to take some time unfortunately.

I hope this helps. Let me know if there;s any good or bad news :)
Click to expand...

Hi Kaltern.
I did a full reset like you suggested. Lead out, etc. It rebooted and I opened oculus home and devices reported no sensor, as expected. While the sensor was unplugged I popped the headset on anyway and noted the following;
I was in the euclidean plane about mid-way between the grid-boundaries. the 'no sensor' message was behind my left shoulder and upside down. I was able to look around in any direction and it was largely stable when looking around. However, if I focus on the 'ok' button (over my left shoulder) the whole view moves in an arc briefly. As the sensor is not plugged in at this point I assume the position sensors in the headset are working ok as I can look about. The rift image quality is unaffected.

I then plugged the sensor in. Oculus home reports its connected and working. I pop the headset on and noted the following;
I'm in the euclidean plans but its not stable I'm closer to one boundary grid than the other. The menu is now by my right shoulder and upside down. The whole image jumps about by a few degrees every half second. Its almost impossible to focus on any menu buttons. I can look around so there is some tracking going on but I suspect this is the inbuilt headset sensors rather than the camera sensor. The image also changes position periodically.

I tried to recalibrate the the camera sensor. I noted the following when wearing the headset and looking towards the camera sensor;
The sensor image appears in front of me but I'm seeing what looks like the cable/arm image from it facing towards me. Its as though the sensor is facing the wrong way i.e. looking away from my headset. If I reach out and reorientate the sensor its position moves in the hmd but in different rotation. The two don't match. There is no orientation I can move the sensor in to make it appear to face me as the view jumps about. There is some tracking going on but its hit and miss, with some jumps.

I tried the scanning beam next by clicking my remote. I had hmd on and was looking straight at camera sensor. The image of the sensor is where it should be but is facing away still. I see the cable/arm image facing me. The actual scan in blue waves happen correctly and squarely across my field of view. Once I acknowledge this by clicking my remote I'm in the oculus home page - off the ground, at an angle of 30 odd degrees with the menu behind me. Some tracking but stuttery with the odd bigger jump.

I'm suspecting its the camera sensor. The hmd shows it has good image quality and its own internal sensors work as it can orientate without the camera sensor. When camera sensor is plugged in it all goes to pot!
I'll hopefully have a resolution on Tuesday. I'll have another cv1 arriving so will be able to swap out and see what is at fault and go from there.
 
Last edited:

Kaltern

Kaltern
The headset uses it's inbuilt sensors to compensate for when the sensors are not getting a good enough reading (due to some headset LED's not working or being obscured), and normally is quite seamless. No sensor at all of course means it has no way of compensating for positional errors, and therefore will act in the way you mention.

I am wondering if there is indeed a problem with the headset LED's. Try getting a camera, smartphones work fine, and put it into video mode, and 'scan' the headset with the camera - you should see the faint LED's in regular distances on the front side and back of the unit. It's possible some are not working, which might explain the sensor's odd behaviour.

Anyway, as you said you're getting a replacement, assuming that is working fine, do try the old sensor with the new headset - I'd be very interested to know if it really was the sensor at fault :)
 

blastard

blastard
Kaltern said:
The headset uses it's inbuilt sensors to compensate for when the sensors are not getting a good enough reading (due to some headset LED's not working or being obscured), and normally is quite seamless. No sensor at all of course means it has no way of compensating for positional errors, and therefore will act in the way you mention.

I am wondering if there is indeed a problem with the headset LED's. Try getting a camera, smartphones work fine, and put it into video mode, and 'scan' the headset with the camera - you should see the faint LED's in regular distances on the front side and back of the unit. It's possible some are not working, which might explain the sensor's odd behaviour.

Anyway, as you said you're getting a replacement, assuming that is working fine, do try the old sensor with the new headset - I'd be very interested to know if it really was the sensor at fault :)
Click to expand...

Hi Kaltern.
All the IR led's on the headset are working. Checked all around it. None missing.
I'll report back my findings on Tuesday. I bet its the sensor.
 

CptXabaras

CptXabaras
blastard said:
Hi commanders,

Booted up the pc earlier for a bit of gamaplay and my rift has thrown a major wobbler. Was perfect up to now and I've changed nothing since playing last night. CV1 wouldn't center when in the oculus home view. Image kept drifting around as though wasn't talking to tracking camera.
Its had been faultless since i originally set it up. Everything has always been up to date. Now if I look directly at the sensor the rift view is looking backwards. I have to turn away from the sensor to even catch site of the oculus menu (which should be straight ahead) before the view starts moving about by itself.
Tried everything from swapping usb's around, checking usb connections and cables for damage etc but cant get the rift view looking forwards and stable. Just keeps flitting about. Its always starts up looking rearwards and off to the side before doing its own thing. Ive tried using oculus settings to try and reset the view but even that is so off center and constantly on the move. It made no difference.
Oculus home says my rift and sensor are connected and the white led's are lit on both devices. even uninstalled oculus and reinstalled+setup. Same problem was there from the moment the rift came to life. Both devices connected ok but still no stable view and tracking.

I suspect my sensor may be kaput but its £100 for another so a fair amount to gamble if it turns out to be lead or rift. Another lead is nearly £50 - although mine looks undamaged.
Has anyone else experienced this kind of ' no proper tracking and failure to focus on the sensor' problem?

I'm grounded without it (and its my birthday today). I may end up spending all my money on another rift as i won't wait weeks if I have to send it back etc.

the upset CMDR Blastard
Click to expand...

to be sure that all your IR led are functioning, look at the HMD with the camera of your mobile phone, on the screen the led will be visible.

Edit: never mind ninja'd
 
Last edited:

Kaltern

Kaltern
UniMag said:
Haha

And imagine my nerves when I tried again on my other one yesterday. My stomach was churning when I booted up and voila it worked!!

Sorry to hijack the thread BTW
Click to expand...

Dear god, you were brave enough to try AGAIN? You must have nerves of steel. Or too much money. :D
 

blastard

blastard
Ok folks, my 'spare' cv1 arrived today (a day later than expected), so I've just finished trying to suss whats up with my 'original' cv1.

The 'spare' oculus headset works fine, as does its sensor and lead - I checked the correct operation of this cv1 package first. I then quickly swapped sensors over from 'spare' to 'original' and looked through 'spare' cv1 again. All working perfectly so it looks like my original sensor IS working ok.
I then tried my original headset with the 'spare' sensor and 'spare' lead and looked through cv1 again - I get the same problems as before with tracking, orientation etc. This means its my original headset or lead at fault so I rebooted the 'spare' cv1 with my 'original' lead and everything works perfectly. This eliminates my original lead from being faulty.

I've concluded that it's my headset that's at fault. This is despite oculus settings saying everything is connected and all headset led's working (as viewed through my camera phone) so its something that cannot easily be detected in software via setup and device settings.

I'll get in touch with oculus to see if they'll entertain replacing the headset for me (tho I've had it since Jan 2016). If not - I'll pay for repair if its not too pricey or look at fixing it myself. Still, at least I'm now 'back in the rift'. That was a long 4-days without - lol. My newly built motion simulation chair is just not the same in 2D (and neither is ED). As an added bonus - I also now have two sensors to use - should tighten up the tracking a little.
I'll also have to decide whether to sell one of the cv1's on (when its fixed/replaced) or keep both and put together the 2nd pc and buy a 2nd ED commander so my mates/kids can multicrew/wing with me in 3D when they pop 'round.
I've clearly too much spare time on my hands!

take care out there!
CMDR Blastard
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom