New to the forums? Click here to read the "How To" Guide.

Developer? Click here to go to the Developer Forums.

Height glitching up and down

12357

Comments

  • tellmiketellmike Posts: 30
    Brain Burst
    Ok, I played around with my sensor setup a bit this evening and have got rid of the height glitches (for now!). I changed the angle of the rear sensor (3rd sensor) so it was tilted higher - now it's roughly targeting my belt/hips. So it was actually pretty low before. I also turned the camera more towards the center of my play area, rather than having it angled towards the edge (I wanted to cover a bigger area, but that might have been bad). 

    I played some Arizona Sunshine (Horde mode - 360 degree action) and didn't experience any hight glitches at all during the 40 min of gameplay. Nor did I experience any severe tracking glitches on my touch controllers either.

    I will try to reorient the sensors a bit more to see if I can get better tracking of the touch controllers when facing backwards - towards the rear sensor - since the controllers can still drift slightly/loose tracking when only the rear camera can see them.

    So right now it actually works pretty ok. Also, I moved the headset slightly higher so that my eyes are in perfect center of the lenses, and that reduces the small shift in perspective while fully turning around - so now it's almost not noticable! Massive improvment never the less.

    So thanks for the tip @Phil007!
  • will84will84 Posts: 76
    Hiro Protagonist
    edited January 2017
    @tellmike

    just out of interest mate did you do a reboot or turn off your system then test to see if the glitch came back?

    I ask because I have been lucky on a few occasions and had no glitching, very few I will add like 1 in a 100 lol.

    A reboot or complete power down and the bug or whatever it is, returns.
  • tellmiketellmike Posts: 30
    Brain Burst
    @will84

    I didn't reboot to see if the problem would return. Will probably notice it tomorrow or friday when I'll be using it again. Will report back of how it went.

    Cheers
  • JesseDeyaJesseDeya Posts: 91
    Hiro Protagonist
    Zandil said:
    It will be fixed, it's just a matter of them getting to the bottom of it.  I have had Touch and 2 sensors since they were released and this issue has only started since Xmas update went live to Home for me, so I'd make a guess that it's a software issue.

    If in the extremely unlikely event they can't fix it, I'm sure there will be refund available.  
    I sure hope you're right. I got my Touch before Christmas but didn't have a chance to use until January - I've spent a lot of time trying to rule out my setup but I'm confident now that it's a software thing.

    Come on Oculus, this should be your absolute priority right now, your latest hardware is basically broken due to a software fault.
    kzintzi said:
    similar for me - I've put a cloth over the second sensor and I just play Elite ATM - trying to play anything in touch just doesn't work.. waiting patiently since it's January and all, but I really want to be able to use Touch again.
    Yup, back to Elite. Suck too because I was really enjoying the Touch, especially Arizona Sunshine - between glitches.
  • Iceburn26Iceburn26 Posts: 8
    NerveGear

    Support have contacted me last night to say they are working on a software solution to the height glitching issue. 

    I'm hoping a patch will roll out by the end of the month.

    So it's just wait patiently / play without touch for another week or two until this is sorted.

  • JesseDeyaJesseDeya Posts: 91
    Hiro Protagonist
    Iceburn26 said:

    Support have contacted me last night to say they are working on a software solution to the height glitching issue. 

    I'm hoping a patch will roll out by the end of the month.

    So it's just wait patiently / play without touch for another week or two until this is sorted.

    @Iceburn26 Thanks for letting us know, I feel a bit better now know a fix is on the way. Any chance you could share the details of the support message specifically?
  • Iceburn26Iceburn26 Posts: 8
    NerveGear

    @JesseDeya I've been trouble shooting this issue since 30th December, I'd just put a new graphics card in my rig, so thought it was that at first. To cut a VERY long story short, I've done everything from test my setup on 3 different computers, change all the camera configurations, windows re-install, etc...

    The only thing that worked was to go to a one sensor setup (didn't matter which one of my 3 sensors either), and not use my touch.

    I've been detailing everything I've done with oculus support, in the hope that they would be able to advise me on something I hadn't tried, or I'd sort the issue out and the data I'd collected might have some help for other oculus users having the same problems.

    A friend of mine has an almost identical setup in terms of PC and sensors, and he's had no problems at all, so I was starting to think it could be a issue with the hardware, except my problem started almost the exact same time as other people have reported, and my sensor and HMD work in non-touch setup.

    Oculus support have been in regular contact since my first message on 30/12/2016 too, and I've been speaking to them nearly everyday as I've been quite willing to do some trouble shooting to get my rift touch back in action.

    Oculus contacted me yesterday, and said thanks for all the info and sorry I'd been having this problem. They have said:

    "The behaviour you've reported appears to be an issue we are currently tracking. Our engineers are aware of this, and we're working hard to release a software enhancement which should help to address this behaviour. We aim for this release some time near the end of this month".

    So they are aware of the issue, could be they are having trouble replicating this at their end but not sure. I'm just waiting now and hopefully i'll see you all in the rift again next week or the week after :)

  • JesseDeyaJesseDeya Posts: 91
    Hiro Protagonist
    @Iceburn26 Awesome, thanks for sharing. Our of curiosity, what are your hardware specs? (CPU, Motherboard, GFX card etc).
  • MradrMradr Posts: 3,535 Valuable Player
    edited January 2017
    Just chiming in - I am also having this issue.

    - I think it has to do with the way it maps the location base off the cameras. 1-2 even 3 didn't seem to have as much trouble as lets say 4. More or less I think the system might need some counter weight to know or trust a senor more than another for tracking. One thing - if the tracking says, "hey, they moved enough we have to move the current camera" - then have it recheck again to make sure.
  • YoLolo69YoLolo69 Posts: 1,113
    Wintermute
    IMHO they should stop to check for sensors moving in realtime, and do that only once when Oculus Home is started.

    “Dreams feel real while we are in them, it's only when we wake up that we realize something was strange.” - Dom Cobb

    "Be careful, if you are killed in real life you die in VR too." - TD_4242

    I7 3770K OC 4.6GHz, GTX1080 OC 10%, 16GB DDR3 2448  OC, Oculus Rift CV1

  • Iceburn26Iceburn26 Posts: 8
    NerveGear

    @jesseDeya Intel i5 6600k (OC to 4.5ghz), on an MSI Tomahawk board, with an EVGA 1080 FTW.

    Also tried it with an i7 6700k (OC to 4.6ghz), on ASUS Maximus hero VIII and ASUS 1080 STRIX.

    And the girlfriend has a 4670k with a Maximus hero VI, I put my 1080 in her machine. Same results on all of them.

  • Iceburn26Iceburn26 Posts: 8
    NerveGear

    I feel it's definitely something to do with the way the sensors hand over to each other, but since it's happening in my machine and not my friends (who has a 6700k on a Maximus board and GTX1080), I thought it was something to do with the firmware in the headset / cameras and not the software.

    Can't be sure though, as I haven't checked his firmware and software versions against mine. 

  • cyberealitycybereality Posts: 26,156 Oculus Staff
    Sorry about that. This is definitely a priority and we are taking all these reports seriously. In fact, we have a software patch releasing soon (probably later this month) that may resolve some of the issues. I'd recommend waiting a bit longer to see if the update helps with your case. Thanks.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i
    Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
  • YoLolo69YoLolo69 Posts: 1,113
    Wintermute
    As already suggested by some persons around here devs can contact some users having different problems related to sensors positioning, Touch tracking, etc. to be beta testers several days/weeks before release. I guess it's easy for them to only dispatch update to specific headset looking at serial number, and people will be happy to report back (as PM, nothing public). Instead of been frustrated, they could feel participating in resolution and really help devs to tests on the vast diversity of configuration we have around. I know this is not that easy to initiate as process as it can create extra works sorting all reports but Oculus may think about it for the future.

    “Dreams feel real while we are in them, it's only when we wake up that we realize something was strange.” - Dom Cobb

    "Be careful, if you are killed in real life you die in VR too." - TD_4242

    I7 3770K OC 4.6GHz, GTX1080 OC 10%, 16GB DDR3 2448  OC, Oculus Rift CV1

  • Callidus80Callidus80 Posts: 24
    Brain Burst
    edited January 2017
    YoLolo69 said:
    As already suggested by some persons around here devs can contact some users having different problems related to sensors positioning, Touch tracking, etc. to be beta testers several days/weeks before release. I guess it's easy for them to only dispatch update to specific headset looking at serial number, and people will be happy to report back (as PM, nothing public). Instead of been frustrated, they could feel participating in resolution and really help devs to tests on the vast diversity of configuration we have around. I know this is not that easy to initiate as process as it can create extra works sorting all reports but Oculus may think about it for the future.
    What a great idea @YoLolo69 ; It would have saved my HMD, Controller and three sensors from being packed away, useless in the bottom of a drawer for the last 20 days. I received Touch on December 5th and went through 4 weeks of trouble shooting. Tried everything similar to @Iceburn26, even rebuilt my PC with different hardware, re-installs, Numerous BIOS configs and driver combinations, got pissed off and dumped it all in a drawer, utterly disappointed. Obviously a software issue and the fix just took to long, Suggesting its more likely the way the Oculus Runtime interfaces with some third party such as Unity.


  • metadanemetadane Posts: 23
    Brain Burst
    Zandil said:
    metadane said:
    Epxzz said:
    The problem lies within the headset itself. I just tried the headset of a friend with the exact same setup/computer/USB ports and it worked flawlessly! LED brightness is exact same for both headset (I did not check the frequencies).

    This is a big problem: I spent hours and days trying to fix this stupid glitch. I was about to wipe my complete system making backups and reinstall windows. Then maybe buying extra hardware for other USB Ports.

    Please give us an update on what will happen next.
    I heard there will be an update at the end of the month... but I really feel fooled again, two month without a fix?
    Can I just run this: https://forums.oculus.com/community/discussion/44368/is-your-rifts-view-tilted-slanted-heres-how-you-fix-it
    Will it the issue shown in this thread? Will it void warranty?

    Sorry for sounding a bit impatient, but I bought the controllers, more than a month ago and every time I use them buggy like they are now I loose faith/trust in the Rift. I won't leave Steam for a while if things keep going like this.

    A bit odd if this was the headset itself, as most of our error logs are showing sensor timeouts and "sensor moved" errors.

    I thought so to, until this morning.  I have been working with Oculus support regarding this issue for a couple of weeks, this morning I got a email from support asking these points

    A short video demonstrating the issue, if possible.Your Rift serial number from the box (starts with 'WMVR' or 'WMPV').Your Rift headset serial number (starts with 'WMHD')Your full name.Your shipping address.
    They would appear to be getting ready to possibly ship out another Rift to me ?
    If they do this will be me third CV1.




    I also got asked for the headset information this week!
  • SahusaSahusa Posts: 5
    NerveGear
    Same or shame probleme since 8 december...PFFFFFF! It's very very very longgggggggggggggggggg... I hope an up date quickly !!!
  • Arock387Arock387 Posts: 729
    Trinity
    Came to join in on the fray!.

    Here to report that I received and set up my third sensor yesterday.  And the height jumping issues became quite a bit more frequent than with the rare 2 sensor setup.  Its playable but is annoying.  Hope they sort it out soon. 
  • KevinLongtimeKevinLongtime Posts: 283
    Nexus 6
    Sorry about that. This is definitely a priority and we are taking all these reports seriously. In fact, we have a software patch releasing soon (probably later this month) that may resolve some of the issues. I'd recommend waiting a bit longer to see if the update helps with your case. Thanks.
    Soo glad to hear at-least some sort of hope for a near future fix. I've been holding off everything VR for weeks.
  • Callidus80Callidus80 Posts: 24
    Brain Burst
    metadane said:
    Zandil said:
    metadane said:
    Epxzz said:
    The problem lies within the headset itself. I just tried the headset of a friend with the exact same setup/computer/USB ports and it worked flawlessly! LED brightness is exact same for both headset (I did not check the frequencies).

    This is a big problem: I spent hours and days trying to fix this stupid glitch. I was about to wipe my complete system making backups and reinstall windows. Then maybe buying extra hardware for other USB Ports.

    Please give us an update on what will happen next.
    I heard there will be an update at the end of the month... but I really feel fooled again, two month without a fix?
    Can I just run this: https://forums.oculus.com/community/discussion/44368/is-your-rifts-view-tilted-slanted-heres-how-you-fix-it
    Will it the issue shown in this thread? Will it void warranty?

    Sorry for sounding a bit impatient, but I bought the controllers, more than a month ago and every time I use them buggy like they are now I loose faith/trust in the Rift. I won't leave Steam for a while if things keep going like this.

    A bit odd if this was the headset itself, as most of our error logs are showing sensor timeouts and "sensor moved" errors.

    I thought so to, until this morning.  I have been working with Oculus support regarding this issue for a couple of weeks, this morning I got a email from support asking these points

    A short video demonstrating the issue, if possible.Your Rift serial number from the box (starts with 'WMVR' or 'WMPV').Your Rift headset serial number (starts with 'WMHD')Your full name.Your shipping address.
    They would appear to be getting ready to possibly ship out another Rift to me ?
    If they do this will be me third CV1.




    I also got asked for the headset information this week!
    This information was requested from me December 14th.
  • FlausnFlausn Posts: 187
    Art3mis
    how long does this take unplayable with 3 cams !!!
  • DuffvaderDuffvader Posts: 38
    Brain Burst
    Having the same issue. I'm kinda regretting more and more for buying the Oculus Rift and not HTC Vive :expressionless:
  • tellmiketellmike Posts: 30
    Brain Burst
    @will84
    I didn't experience the height glitch when using the Rift/Touch today. Was enjoying "Dear Angelica", The Lab, Google Earth VR, and some testing around in Oculus Home to try to provoke some height glitches. So far so good 

    I only have some minor Touch gliches when turning completely around, but other than that it's pretty solid. Waiting for a HDMI repeater to arrive from China to extend my room scale experience with 10ft, so will see how robust the tracking will be then.
  • tellmiketellmike Posts: 30
    Brain Burst
    @Duffvader
    I had the same though the other day when I had severe height glitches, and floating Touch controllers when I added a 3rd camera. Now when things are working then I'm glad that I went with Rift. The HMD/screen/lenses/Touch are so good when they work.

    In order to fix my height glitch issue I raised the angle on the 3rd camera slightly and re-calibrated the sensors.
  • BushchookBushchook Posts: 3
    NerveGear
    My rift and touch setup had been working flawlessly until I added a third camera yesterday and the height glitches started. The two original front cameras are at exactly the same height with the third camera being about 400mm lower than them. I am going to try them with all at the same height to see if that is the problem. Perhaps using different USB ports might be worth a try too. 
  • SolslandSolsland Posts: 278
    Nexus 6
    Unfortunately having the same issues here.  In most games I am jumping up and down and in 'Onward' it is unplayable as my avatar sticks in crouch position limiting movement and seriously hindering speed.  

    Have spent a bit of time resetting sensors etc with no success.  Here's hoping the patch later this month works.
  • CanenCanen Posts: 1
    NerveGear
    I am also having the floor height glitch issue. I have been silent so far in hopes that one of the multiple answers may fix the issue. I am working with 4 sensors but have tried 3 sensors as well. It is quite annoying when you go to reach for a gun and it is under your real floor.

    I have lost count of what I have tried. I have moved the sensors multiple times and aimed them up and down. I have them 6' up and on the floor. I have aimed them down and up in both areas. I have made sure that they are perfectly aimed in deskscene. I tried multiple versions of the usb drivers for the fresco board as well as for the mother board drivers. I even tried another usb card that some people were having luck with the orico usb 3.1 2 port. I have tried multiple usb extension cables. I have a pile of them over on the floor.  I have taken anything even remotely shiny out of my play area. I updated to the newest beta software from windows to see if that would help.

    This software update is my only hope that I know of!

    My computer:
    MSI Z170A Gaming M7 LGA
    MSI GTX 980TI LIGHTNING
    Intel Core i5-6600K


  • FlausnFlausn Posts: 187
    Art3mis
    fix it !!!!!!!!! why is this like it is ???? and no update for a month now !!!!
  • gamefan101gamefan101 Posts: 194
    Art3mis
    Flausn said:
    fix it !!!!!!!!! why is this like it is ???? and no update for a month now !!!!
    +1
Sign In or Register to comment.