12-12-2016 12:30 PM
01-18-2017 01:13 PM
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.
01-18-2017 01:17 PM
01-18-2017 01:29 PM
01-18-2017 03:39 PM
01-18-2017 06:23 PM
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.
Yup, back to Elite. Suck too because I was really enjoying the Touch, especially Arizona Sunshine - between glitches.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.
01-18-2017 10:18 PM
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.
01-18-2017 10:23 PM
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.
01-19-2017 03:07 AM
@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 🙂
01-19-2017 04:50 AM
01-19-2017 06:13 AM