Jump to content

stikaz

Verified Members
  • Posts

    14
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. i did the test asked me to do. I switched back to the power bar i was using previously and the problem appeared after around one hour. Then i switched again to the power plug without surge protection and played for a few hours. Normal gameplay went smooth, but i was able to willingly reproduce the issue if i kept staring for a few minutes at the virtual ceiling. Keeping my head in that position, even in clear view of both base stations, caused the screen to go grey after a while. So, in the end, now that temperatures are lower, the issue is much less prominent. Everything is pointing in the direction of this being primarily an issue about overheating. I find it very strange that HTC Staff didn't manage to give us a serious answer in all these months. I am guessing they know the problem is heat related, they have no fix, and they are just hoping that with the end of the summer the problem will be less apparent and people will shut up and will not be too vocal about it.
  2. hi, i was thinking of doing this test too, trying again with the power bar. I am quite busy at the moment but i will try to do it in the next few days and will post here the results.
  3. to answer your questions: with the power bar, the problem usually appeared after at least 30 mins. I was convinced it had something to do with overheating, and i still do, anyway, since i'm not using the power bar, everything run perfectly. Not only i do not see any grey screen but the tracking seems improved too. Before finding this, i had tried the sensor covering trick. It helped for a time but at last the problem appeared again.
  4. hi everyone, i have potentially promising news. I was discussing the issue on reddit and someone suggested to try to not use a power bar with a surge protector to power the base stations. As i was using one, i tried what he wrote. I connected the base stations directly to the power socket without using the surge protector. I have been playing for the last few days, several hours a day, without the slightest problem. Not a single gray screen up to now. Temperature was also cooler last days, but i have a feeling that the surge protector was what causing the problem in my case. It maybe also be that the issue is caused by different factor for different people, but if someone experiencing the problem is using a surge protector to power the base stations, it's worthwhile to try without it and post here the results. On my part, i will post again if i will experience the problem again. Good luck everyone!
  5. I want to add that the sensor-covering workaround is not 100% reliable. It's up to how many sensors start malfunctioning in the headset. If it is more than one sensor failing (as in many cases), the problem will happen even with one or two sensors covered, it will just take more time to appear.
  6. I don't think controllers are directly related to the issue but, as is a tracking problem, using the controllers helps the system to keep good tracking. With no tracking controllers, when sensors fail, the tracking go nuts more quickly. That's why the issue is more prevalent when playing sitting. At least that's my impression I also had the problem you're talking about, and your link is the best way to solve it, but it's totally unrelated to the issue in this thread.
  7. As others are asking, is there any news? Have the engineers analyzed 's HMD? Did they find anything unusual in its sensors? Did they manage to find the root cause of the issue? Has HTC thought about what to do with users experiencing the problem? What about Vives bought more than a year ago (as in mine and other's cases) that started experiencing the issue around the same time as everyone else (few months ago, starting since March or earlier)? I recall the Rift had tracking problems when touch went out, and people found a workaround covering selected sensors in the HMD, until Oculus put out an update that solved the issue (took them a few months). As this is similar to our situation in this regard, could something similar happen with our issue? Or do we need to change the HMD entirely? Thanks and good work!
  8. I'll check it again. It could be that I confused between the mirror screen and the game screen on the monitor. Aidarpro description makes more logical sense. Unfortunately I am not home for about one week.
  9. I can confirm what wrote. When the grey flickers start appearing, the mirror screen on the desktop still behave as normal and the HMD position keeps being tracked in the mirror display on the monitor with no flickers. Only inside the HMD there is flickers. Maybe this information can lead engineers in the right direction to find the cause of the issue.
  10. I have read the whole thread, as was implied in my post. "a few months ago" spans until March. Actually as I wrote in my previous comment, I changed video card in April and the problem was already there, so probably I experienced the problem in March too. It could be that the problem started in March (or even earlier) but people playing mostly room scale games (where the problem is less apparent) didn't notice until later. Or maybe not. Obviously mine were just suggestions, I am not even an expert. But given that support still seemed to have no clue and were looking at faulty cables, and given that I recently changed my cable and the issue persisted, I commented about my experience and what I thought would be worthwhile to check. That's all. Obviously there can be different and totally unrelated causes of the issue. It could be about deteriorating components, but then why the problem appears after several months of use for someone like us (around one year in my case), and after a few weeks for others, as I wondered in my previous comment? I wrote that maybe the fact the the problem seemed to appear for everyone around the same time-window can point to a faulty update in the software. But maybe this is explained simply by the fact that from March temperatures started rising, so it could have nothing to do with software updates but only with overheating. Then again, someone wrote the problem is there even with air-conditioned rooms; besides, in March temperatures weren't so high (while June has been exceptionally hot this year in my country). So the point is, unfortunately finding the the cause of the problem is still far, and my post was only to suggest to try other solutions, and especially involved the valve team. EDITED for additional details.
  11. I have read the whole thread, as was implied in my post. "a few months ago" spans until March. Actually as I wrote in my previous comment, I changed video card in April and the problem was already there, so probably I experienced the problem in March too. The post in the steam forums someone linked also mentioned March. It could be that the problem started in March (or even earlier) but people playing mostly room scale games (where the problem is less apparent) didn't notice until later. Or maybe not. Obviously mine were just suggestions, I am not even an expert. But given that support still seemed to have no clue and were looking at faulty cables, and given that I recently changed my cable and the issue persisted, I commented about my experience and what I thought would be worthwhile to check. That's all. Obviously there can be different and totally unrelated causes of the issue. It could be about deteriorating components, but then why the problem appears after several months of use for someone like us (around one year in my case), and after a few weeks for others, as I wondered in my previous comment? I wrote that maybe the fact the the problem seemed to appear for everyone around the same time-window can point to a faulty update in the software. But maybe this is explained simply by the fact that from March temperatures started rising, so it could have nothing to do with software updates but only with overheating. Then again, someone wrote the problem is there even with air-conditioned rooms; besides, in March temperatures weren't so high (while June has been exceptionally hot this year in my country). So the point is, unfortunately finding the the cause of the problem is still far, and my post was only to suggest to try other solutions, and especially to involve the valve team. EDITED for additional details.
  12. I have read the whole thread, as was implied in my post. "a few months ago" spans until March. Actually as I wrote in my previous comment, I changed video card in April and the problem was already there, so probably I experienced the problem in March too. It could be that the problem started in March (or even earlier) but people playing mostly room scale games (where the problem is less apparent) didn't notice until later. Or maybe not. Obviously mine were just suggestions, I am not even an expert. But given that support still seemed to have no clue and were looking at faulty cables, and given that I recently changed my cable and the issue persisted, I commented about my experience and what I thought would be worthwhile to check. That's all. Obviously there can be different and totally unrelated causes of the issue. It could be about deteriorating components, but then why the problem appears after several months of use for someone like us (around one year in my case), and after a few weeks for others, as I wondered in my previous comment? I wrote that maybe the fact the the problem seemed to appear for everyone around the same time-window can point to a faulty update in the software. But maybe this is explained simply by the fact that from March temperatures started rising, so it could have nothing to do with software updates but only with overheating. Then again, someone wrote the problem is there even with air-conditioned rooms; besides, in March temperatures weren't so high (while June has been exceptionally hot this year in my country). So the point is, unfortunately finding the the cause of the problem is still far, and my post was only to suggest to try other solutions, and especially involved the valve team. EDITED for additional details.
  13. i have the O11G since about two weeks. Before i had an Aorus 1080ti but it overheated so i returned it. The problem was there even with that card. If i'm not wrong, i had the problem even with the old strix 970 (that i changed in April). EDIT: psu is RM750i if that's of any relevance
  14. hi everyone, i have the same problem everybody described in the comments. My experience is exactly as AGR-13 described above. I recently changed cable from the old to the new 3-in-1 but the problem persists. I usually play seated with controllers turned off, but it can also happen when playing room-scale with controllers. I use the sync cable. I am worried because from staff's response they don't seem to have a clue and several months have passed already (no disrespect meant, i know it's like finding the proverbial needle in a haystack but this is a severe issue that needed to be solved already). From everyone experience, it seems clear that the problem is HMD sensors overheating and giving false information to the software. Then again, if that's the case, why the problem was not present from the beginning? i played several months without the issue, while others are affected after a few weeks. It happens with several different iterations of the HMD, from the oldest to the newest. It seems to have started for everyone around the same time, a few months ago. This is good because it points to a problem in software. Maybe the made an update to improve the software tracking precision, and then the overheating problems became apparent. In any case, i think it's a problem that the Vive team have to solve with the steamVR devs, maybe finding a way to check the reliability of the sensors and ignore information from sensors that don't pass the check. here are my infos: HMD Serial and date of purchase: FA63PJJ00304 - launch day Grey Screen: does it flicker or stay solid grey? starts flickering after 30-60 minutes, than flickers more and more, one of the basestations keeps greying out. Basically what everyone said. When problem began (more or less): few months ago Your location:italy OS Version: Windows 10 version 1703 OS Build 15063.483 Computer Make/Model or Motherboard if homebuilt: asus z170 pro gaming - i5 6600k@4200Ghz RAM: 16gb ddr4 Networking or other cards plugged in to motherboard: Intel® Ethernet Connection (2) I219-V Graphics Card: asus strix 1080ti O11G 382.33 General Computing Environment and Set up: 1 monitor via displayport Steam Version: tried with both VR Home Beta enabled/disabled:tried with both Viveport installed/not installed: installed Oculus or revive or other VR environment installed: oculus and revive Looking forward to hear any news, thanks staff for your work
×
×
  • Create New...