crwdns2933423:0crwdne2933423:0

Released March 2016, the Rift CV1 is the first consumer-targeted virtual reality headset by Oculus.

crwdns2934591:033crwdne2934591:0 crwdns2934593:0crwdne2934593:0

Request timeout on sensor setup

This drives me crazy. cant find anything on the internet answering this, but tons of users with the same problem who also dont have answers. basically, I get to the part where I have to put the controller at eye height push the trigger and get request timeout. any help? thanks!

I have a 2 sensor setup.

@oldturkey03 @avanteguarde @paperboypaddy @pccheese @mayer

crwdns2934089:0crwdne2934089:0 crwdns2934093:0crwdne2934093:0

crwdns2934109:0crwdne2934109:0

crwdns2889612:0crwdne2889612:0 2
crwdns2934285:0crwdne2934285:0

crwdns2933315:010crwdne2933315:0

crwdns2934057:0crwdne2934057:0

After fruitless search on the internet and many attempts, I finally got it working.

SOLUTION:

75% luck

25% arrangement

make sure the sensor are pointing towards the play area at an angle slightly looking over your head. keep re-arranging until the sensor detects the controller and does not keep losing connection. then, press and hold the trigger. success!

also, keep trying different USB port combinations.

UPDATE 3/26/18 (one day later)

or not. had to setup again and now having the same problem. this does not work 100%

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 4

crwdns2944067:02crwdne2944067:0:

You would think for a $200-$600 device this would not be such a hassle to setup.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

I have an HTC vive and it was a breeze to setup. Cost me $1,000 though..

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

I got past this problem by moving closer to the sensors, and if the detect them just skip that part. It’s usually just the room you are in. Also if that doesn’t work try lining up the controllers were the sensors can’t miss them, even if it’s not at eye level. That’s what I used to get past this annoying glitch. I think that something is Interfering with the sensors when the controllers are at recommended distance, moving rooms may help to. Hope it works for you.

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 1

crwdns2944067:02crwdne2944067:0:

This works too I also had a lot of lights around my setup and the tv was right next to it and also there was Christmas lights and when I turned them off it started working so maybe it was too much ir interference.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

It's mostly Christmas tree lights. They will mess up tracking.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

My subjective experience is that the timeouts are related to setup pegging my CPU at 100%. I seem to have better luck if I run nothing else but Task Manager, watching for any dip in CPU use below 95% before holding the trigger. (It still takes me about a dozen attempts. WTF Oculus?)

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 1

crwdns2944067:02crwdne2944067:0:

3 weeks of frustrations !! And I finally got it to work. this may help some people.

**I am using windows 10

With your sensor calibration open... You know the one that keeps saying request timed out.

Press CTRl AlT DEL and run task manager.

If your CPU is pegged at 100%ish

Scroll down on task manager and end task on "windows explorer".

This will make everything go black except your oculus setup. If your computer is like mine the cpu will drop to 60% and your sensor setup will work!

Honestly I haven't tried it twice, but it's been 3 weeks of insane frustrations after moving my setup. Hope this helps someone else!

Thank you to rrusson for the point in the right direction!

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

Chadh your advice was a godsend, thank you.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

There is no way to fix this as it is an issue with the oculus I recommend returning it and buying an htc vive I have the same problem with my oculus I bought today.

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 0
crwdns2934285:0crwdne2934285:0

Blew the dust off my Oculus. Everything has been up to date. One eye shows a white background and the other shows a black background. I’ve got two navigation menus going. Tracking is all janky. I go to set up my sensors, all green check marks, I put the touch at eye height, pull the trigger, completes, Request Timed Out. Some times it can’t see the touch sensors, I replaced the batteries and try again. I hit skip, nothing happens. I kill the program, go to guardian settings, sensors are way off! Can’t do anything!

I’ve had issues in the past with Oculus. They fall behind NVIDIA driver updates so sometimes my Oculus screens will never come on unless I downgrade. Wish I could just get all my money back and wait for the Quest.

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 0
crwdns2934285:0crwdne2934285:0

What I did was connect only two sensor at time. Testing it and then arranging it with different usb ports and then testing it again. Test usb 3.0 and 2.0 ports. After I find a combination that works. I then bring the 3rd sensor back. Then it doesn’t work again. Then I move around the 3 sensor to different usbs and then it worked. I am using the recommended usb 3.0 Inateck  card. I ended up plugging all into the inateck card except one sensor to usb 2.0 and then it worked. I think the problem has to do with the fact that not all usb ports are controlled with a separate controller so when you plug it into the wrong usb the sensors are unable to sync and time out when you try to complete the test. Though my theory has holes in it, it’s the only reason I can come up with. Also when you change the usb ports I close the Oculus each time before unplugging anything.

————-

Update it doesn’t work. Another work around is to plug in 2 sensors get it really close where it can still see the controller . Once you get past the sensor setup and pick the direction of the computer finish out the whole setup. Then move the sensors to where you actually want it and add the 3rd sensor back. Turn off the guardian system. Use a small rug as your guardian system. When you are in VR you can open the Oculus menu to reset game position.

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 0
crwdns2934285:0crwdne2934285:0

After buying over 24 Oculus headsets, all having different problems….I finally bought a Samsung Odyssey Plus. All I want to do is fly my X Plane 11 aircraft in Virtual Reality. Plug and play setup. Configuring software for games is where it gets interesting. But hardware setup is easy. Doesn't have the power but Resolution is same as HTC Vive Pro. Has OLED displays instead of LCD displays and you can pick up a good used System for around $200. I love Oculus but it doesn't love me. Why does Oculus/Facebook Technologies,LLC have such poor customer service? Why doesn't Oculus care about their customers?

Block Image

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 0
crwdns2934285:0crwdne2934285:0

I may have found the solution. It seems to be a power issue. Make sure your computer is plugged into an outlet and have oculus tray tool set to high performance power and usb selective suspend is enabled. Those last two things may not even be necessary, but it is exactly what I had set up and it worked once I plugged into a power outlet.

I was trying and trying to set up my sensors today with no luck(I’m on a laptop). As soon as I plugged in, the sensor setup video was running smooth in the bottom corner. It was a breeze after that; first try it worked. I didn’t realize how laggy and jittery it was when I was trying before without direct power. It should be looking smooth on your computer, including the “squeeze the trigger” circle meter. If it’s not you’re going to have troubles.

I’d double check all the usual stuff too: sensor placement, controller batteries, and weird lighting/reflectors, usb configuration/drivers. But, I’m betting it’s your power. It must be keeping the sensors active during the process. Hope that helps fix this annoying problem for everyone.

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 0
crwdns2934285:0crwdne2934285:0

duders make sure you point your control at your screen during this step worked for me every time. Eye Level and at the screen.

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 0
crwdns2934285:0crwdne2934285:0

Changing the USB ports helped me. I have a 3 sensor setup. After hundreds of fails, I finally changed the USB ports. It finally started trying to work every 10 tries or so; however, it would want me to turn the sensor and start over. Finally I moved my hand rather than the sensor. This worked well - finally.

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 0
crwdns2934285:0crwdne2934285:0

crwdns2934229:0crwdne2934229:0

Aiden crwdns2934231:0crwdne2934231:0
crwdns2936625:0crwdne2936625:0:

crwdns2936751:024crwdne2936751:0 0

crwdns2936753:07crwdne2936753:0 1

crwdns2936753:030crwdne2936753:0 19

crwdns2942667:0crwdne2942667:0 16,080