08-16-2017 12:54 PM
First, let me thank John and other HTC employees in the background for your support - even if this is a painful road to go. But it feels good to go it together.
Yesterday I had time to test the exchanged HMD again for 2h with the old firmware and then around 2-3h with the new firmware.
environment & other variables:
- the same than last time - no changes
- tested EVE: Valkyrie and some games in seating position with and without Vive controller
- room temp was around 26.9°C - so again warmer than last time
- no issues during the whole playing time
- no issues also in the steamVR overlay (no greyouts of the lighthouse symbols)
- new Vive is also getting hot (measured by touch on front) - I assume even a bit hotter than the old one, but I didn't test the old one such a long time - but still no issue.
- I seems, that heat alone is not responsible for the issue to happen. It needs also a factor more - maybe one ore more faulty sensor(s) - to make the issue happen in combination with heat.
- I was never able to play that long time with my old HMD during the last months - so I assume, that the exchanged HMD is OK (it still needs to prove over time). I now have a better feeling.
-> so, this seems to be good news for the moment - I keep my fingers crossed!
I still expect answers to what's going on in the lab at HTC now
08-17-2017 08:06 PM
Yeah but mine worked for several months before it started malfunctioning, so unless a hardware change has been made I would not be surprised if the new one started having problems in a few months.
08-18-2017 12:43 AM
I also have the flashing gray screen problem. I usually play room-scale and I played several months (from November 2016 to about June 2017) without the issue.
Here are the infos that @jagibson require:
HMD Serial and date of purchase: FA6B4JJ00301 - 11/2016
Grey Screen: does it flicker or stay solid grey? Starts flickering after 10-15 minutes, then the problem increases until the screen becomes competently gray.
When problem began (more or less): June 2017
Your location: Italy
OS Version: Windows 10 version 1703 Build 15063.540
Computer Make/Model or Motherboard if homebuilt: Asus Z170 Pro Gaming - i7 6700k 4GHz
RAM: 32GB ddr4
Networking or other cards plugged in to motherboard: Sound Blaster Zx
Graphics Card: ASUS GeForce STRIX-GTX1080-A8G
General Computing Environment and Set up: 1 Monitor Full HD - DVI
Steam Version: beta and public - The problem occurs with both versions
VR Home Beta enabled/disabled: enabled
Viveport installed/not installed: I tried with and without - same behavior
Oculus or revive or other VR environment installed: oculus and revive installed, but I also tried without, with the same result
08-22-2017 12:05 PM
I am sorry that I still can't find the time to post here , but I've been busy a lot lately so ... I will try to find time these days to post my statements and info that we were all asked to give. After I bought and set an AC in my room and keep the temperature at 23 C , I haven't got any issues, but I've only had the time to play twice and longest was not more than 3 hours. Anyway, so far I guess it's obvious that the reason causing this problem is hardware issue, and therefore the only reasonable solution I see is that we all get an exchange with new HMD's .
08-22-2017 02:03 PM
I added a post last night with all my details, but after editing it a few times, it seems it is still waiting to be approved by the list Admin. Hoping it shows up soon, because I didn't keep a copy
08-22-2017 07:24 PM
Ok, I'm going to try this one more time since my post from last night seems to have been lost in the ether, and I too, have been having this same issue for about 2 weeks now.
My Vive worked beautifully for the first few weeks without any issues. I played several hours at a time my first few days, but for the time, only played around with demo's and the free game I received with purchase. My main reason for setting up VR is because I wanted to do a space combat simulator in VR. I spent a few weeks choosing my game (Elite: Dangerous), and another few days getting my controller (Thrustmaster HOTAS 4) to work. So it was not until I got everything installed and configured before I started noticing the issue. Unfortunately, I am not sure if I ran into this issue my first night playing, but honestly, after getting everything working, I just tried a training mission or two before passing out. So it may have been there from the very beginning.
As others have noted, it works fine for maybe 20-40 minutes, maybe slightly longer. Since I can spend a lot of time in E: D in the station menu's, I may not even move my head for a while... so the issue either happens when I'm in the middle of a dogfight, or when I first move my head after being in station menu's for too long.
At that point, it usually is only a momentary flash of solid gray, but the duration and frequency both increase over the next few minutes until the Vive screens stay gray. As it begins to fail, I can still perform actions in my game, and HEAR that I am doing something, but when the screen stays solid gray, no other actions seem to occur, and the screen mirror has frozen (though it continues to work as the gray flashes increase).
After reviewing other threads, and this one, I tried updating the BIOS of my motherboard, updating the USB drivers direct from the MoBo manfacturer, re-aligning my base stations, moving my Vive USB connection from a shared 3.0 hub to a dedicated 2.0 MoBo port, and reduced the frame rate of the camera in the Vive settings. None of these actions seems to have had any effect.
So, having this for only 6 weeks, I am VERY discouraged to have found this thread only yesterday, and see that people have been having this issue since at least June, maybe even March, with NO resolution yet from HTC.
I'm beginning to wonder if I should pressure Amazon to accept a return, since it took this long to find out it can't do what I bought it for
08-22-2017 07:47 PM
So here's a thought:
My issue only started occuring about the time I installed and started using my Thrustmaster HOTAS 4 controller for Elite: Dangerous.
But this got me thinking... though I don't believe it's related to the controller, perhaps it does have something to do with what I have NOT been using when this issue appears: The Vive Controllers themselves.
It would seem to me, that the controllers might be powering down, or going into some other 'hibernation' and perhaps it's not until the base stations and/or HMD can't talk to them, that this issue starts to appear? I could see this kind of behavior overlapping quite well with the percentage of people who are having this issue.
So, users with this issue.... do any of you run into this problem only when doing activities where the Vive controllers are sitting idle?
08-22-2017 09:03 PM
I have a similar issue where my Vive controllers act really strange when I have my racing wheel / pedals turned on. The controllers with flake out, get gittery and will often not click when pressing the trigger in SteamVR dashboard. The problem is well known and it seems the culprit is any controller with a throttle, racing wheels with a gas pedal and flight sticks with throttles can affect the behaviour of the Vive controllers. I just leave the Vive controllers off and fire up the game I want to use with the mouse in Steam. There are some utilities out there that can fix this problem one of them being called "DashFix".... check this out...... https://github.com/simonowen/dashfix
08-24-2017 09:21 AM
08-24-2017 09:28 AM - edited 08-24-2017 09:41 AM