06-27-2016 07:53 AM
03-20-2017 09:23 PM
03-21-2017 01:08 PM
Vaeyn said:
I had this problem of random HDMI disconnects and I realized it happened most when I was in the middle of a very intense bit of combat in games like Robo Recall. I played with the headset a bit and found out that the cable connecting into the Rift headset was kind of lose and if I touched or messed with it even lightly it would disconnect.
I decided to try something really simple to see it would fix the problem. What I did was get some cellophane tape and I wrapped it around the rubber part of the plug just above the metal connector that goes into the Rift headset to make it thicker and give it less room to wiggle during intense play. I then plugged it back in and gave it a go with Robo Recall and Raw Data, the two main games I got the most disconnects.
So far it seems to have fixed the problem pretty well. If you notice your disconnects come from intense play and touching the headset then you may want to give this a try.
03-24-2017 10:15 PM
03-26-2017 07:31 AM
04-26-2017 07:32 AM
02-06-2018 01:59 PM
02-19-2018 09:19 PM
KERISS said:
Seems, a problem is finally solved for me. The mainboard bends together with the whole rift when it's being moved or touched. In the middle of the board there is a STM32F chip located (iFixit teardown, step 9, yellow square) which has almost no space between textolite and chip's body. But since it is located in the middle, all bends come thru this point and bga connection gets broken. I've heated this chip with soldering heat gun (together with small amount of flux) and glued another piece of textolite to the backside of motherboard to reduce flexibility in this point. Since that I'm not afraid to make head movement or adjust the rift on the head. Disconnection problem has gone. Hope this information helps.
P.S. English isn't my first language, so please excuse any mistakes.
04-25-2018 09:10 PM
Javbomb said:
Javbomb said:
PIXELATED said:
@javbomb.. did you get your rift made happy again or are you still waiting?
Not just yet...
https://forums.oculus.com/community/discussion/comment/417773/#Comment_417773
Got my replacement Rift Finally... After four hours of the amber light and not being able to get it working I found a really odd quirk where I had a rogue file called 'Program' in the root directory of C Drive which was stopping the Oculus services from correctly executing the library and switching on the HMD... I was almost ready to give up when I finally looked really hard at the Oculus logs and found some references to not being a valid Win32 application, googled it, and saw a tip saying that's usually because of a space in the file path... Ha.
Anyway, deleted that file, and holy hell it all seems to work. Didn't play for too long, but I kind of squeezed the HMD and twisted it a bit to the point where the other would cut out and this one is good... played a couple games for about 30 mins and not one drop out despite taking on and off the HMD a few times. I think this nightmare may be over 'touch wood'
Time to try and forget this whole ordeal and just enjoy VR.
Over and out.