Jump to content
 

AGR-13

Verified Members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About AGR-13

  • Rank
    Settler

Recent Profile Visitors

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

  1. Hello HTC I still have the same problem of poor audio quality - still having the workaround active using +12db bass on 80Hz in Windows audio devices. Could you please provide some news on this issue and the progress of solving it? Thanks for a swift answer
  2. https://community.viveport.com/t5/Technical-Support/flashing-grey-screen/td-p/8607/page/26
  3. Hi everybody 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 results: - 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. conclusion: - 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! :manvery-happy: I still expect answers to what's going on in the lab at HTC now best, AGR-13
  4. Hi everybody Like others here I'm in contact with John and today I received an HMD from HTC Regenersis (Repair station Romania) after sending mine in for testing in the Lab in Taiwan - the exchanged unit has the same serial number like my old one, but it seems to be an exchanged HMD unit (serial No. sticker is not in the same position). The cable seems to be the same (3in1 with my marker). There is a firmware upgrade recommended, but I didn't do the upgrade until now. I tested 30min and also 60min (didn't have the time for 2h+, had to watch my kids today ;) ) environment: - room temp is around 23.7°C (around 3°C lower than my last tests with my original unit) - I tested with the "old" firmware, that came with the exchanged headset - I tested one session 30min with the old cable and 60min with the new cable I received from HTC - no changes made in software, except a windows update yesterday (should have no effect) - no HW changes - no covering of reflective surfaces - same chair, monitor and furniture as ever (same environment) - no changes in position of the lighthouses - tested with all HOTAS controllers like last time Here is the result: - no issues detected during both tests (30min and 60min Eve: Valkyrie) - I couldn't reproduce the error, but I have to test it again for 2h+ --> no issues in tracking --> lighthouses were never grey in SteamVR overlay - HMD is still getting hot during the test, but still no issues detected Here some detail info regarding the HMD firmware versions: NEW report of the EXCHANGED HMD device from today (2017-08-11): -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- <Devices> Device 1 - LHR-901853DF Headset Vive MV HTC Firmware: 1462663157 steamservices@firmware-win32 2016-05-08 FPGA 1.6/0/0 Hardware Revision: product 128 rev 2.1.0 lot 2000/0/0 0 Hardware Id: 0x80020100 Firmware Update: Update necessary Watchman Firmware: 1462663157 / 1462663157 (2016-05-08) Watchman FPGA: 262 / 262 (1.6) Camera Firmware: 8590262285 / 8590262295 (Version: 02.05.0D Date: 2016.Feb.26) (Update necessary) Display Firmware: 2097432 / 2097504 (Update necessary) Display FPGA: 57 / 57 Display Bootloader: 1048584 "0x0000000000100008" Display HW Revision: 19 "0x13" Audio Firmware: 3 / 3 VSync to Photons: 0.0111111 Display Frequency: 90 User IPD (m): 0.0609 Current Universe ID: 1499985803 Previous Universe ID: 0 Dongle Version: 02BF2D3EDC Version: 1461100729 / 1461100729 (2016-04-19) Dongle Version: 81AE76616C Version: 1461100729 / 1461100729 (2016-04-19) OLD report of the OLD HMD device from 2017-07-17: -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- <Devices> Device 1 - LHR-88365322 Headset Vive MV. HTC Firmware: 1462663157 steamservices@firmware-win32 2016-05-08 FPGA 1.6/0/0 Hardware Revision: product 128 rev 2.1.0 lot 2000/0/0 0 Hardware Id: 0x80020100 Watchman Firmware: 1462663157 / 1462663157 (2016-05-08) Watchman FPGA: 262 / 262 (1.6) Camera Firmware: 8590262295 / 8590262295 (Version: 02.05.017 Date: 2016.Jul.19) Display Firmware: 2097504 / 2097504 Display FPGA: 57 / 57 Display Bootloader: 1048592 "0x0000000000100010" Display HW Revision: 51 "0x33" Audio Firmware: 3 / 3 VSync to Photons: 0.0111111 Display Frequency: 90 User IPD (m): 0.0602 Current Universe ID: 1499985803 Previous Universe ID: 0 Dongle Version: 862C94A052 Version: 1461100729 / 1461100729 (2016-04-19) Dongle Version: B0DBD37E6C Version: 1461100729 / 1461100729 (2016-04-19) At the moment I'm waiting for information about what the exchanged HMD exactly is and if there is news about the root cause and if they where able to reproduce the issue with my HMD, that I sent in. I will do some stress tests over a longer time when I have a time slot. Could take some days until I can do a real 2-3h test. all best AGR-13 Just for information to all users, that are affected: I also informed the HTC CEO and the Head of HTC Creative Labs about this thread - just to be sure, that there is enough attention to a possible design mistake.
  5. Hey stikaz thx for sharing your detailed info with us. May I ask since when you are using the 1080 Ti Strix O11G? I have the same card.
  6. Hi everybody The last days I tested several times: - my room temp is between 26 and 29° C these days - the issue can be reproduced reliably after around 20-30min - if you don't connect your controllers (just let them "off") then you can see the following: -> the headset might still be tracking well - but the lighthouses start greying out in the SteamVR application. -> sometimes you are able to continue playing whithout grey flashes for some time, even the lighthouses show grey in SteamVR overlay -> regarding your headset position, the grey flashes start to appear -> if you cover your headset from the sides with your hands like you want to take it off the head, sometimes, the grey sreen stays for a long time. -> and it starts to be unplayable after a while - in my case it happens a lot, when I'm facing my monitor directly and turn my head a bit downwards.
  7. I expected news yesterday. Why there is no communication? What can we do?
  8. Thanks to Dave for taking the time to do an test for elimination. So it actually means: there are just a few headsets affected and the issue goes with to a different location with a whole different environment. So it stays with the headset. So that rules out the rest of the equipment as a root cause. Additional test: Today I played also around 30min only in the environment of Oculus - since I wanted to test how it reacts to revive. -> same issue occured, also in the Preview of another app in Vive, again in Elite Dangerous Two things: - 1. - I could stop the issue for 15min when I cooled down the Vive - and I put the Icepack not over a sensor. So it took about 10sec to cool it down enough, so that the issue didn't return for around 15min - 2. - When I put a finger on the sensor (red circle in pic below) then I also could stop the issue immediately. But when I lifted the finger, the issue returned immediately. It disappeared only during the finger was on the sensor (similar to the test of ) And it is worse when putting the head in a down direction. So this my additional information to the case. Question to everybody: Does anybody have a Deluxe Audio Strap? (I use one) Question to HTC: Could you maybe send out some brandnew units built in 2017 to the people who have the issue. I think we could make some comparison tests for you if we can reproduce the issue also with another headset?
  9. Thanks to Dave for taking the time to do an test for elimination. So it actually means: there are just a few headsets affected and the issue goes with to a different location with a whole different environment. So it stays with the headset. So that rules out the rest of the equipment as a root cause. Additional test: Today I played also around 30min only in the environment of Oculus - since I wanted to test how it reacts to revive. -> same issue occured Two things: - 1. - I could stop the issue for 15min when I cooled down the Vive - and I put the Icepack not over a sensor. So it took about 10sec to cool it down enough, so that the issue didn't return for around 15min - 2. - When I put a finger on the sensor (red circle in pic below) then I also could stop the issue immediately. But when I lifted the finger, the issue returned immediately. It disappeared only during the finger was on the sensor (similar to the test of ) And it is worse when putting the head in a down direction. So this my additional information to the case. Question to everybody: Does anybody have a Deluxe Audio Strap? (I use one) Question to HTC: Could you maybe send out some brandnew units built in 2017 to the people who have the issue. I think we could make some comparison tests for you if we can reproduce the issue also with another headset?
  10. Thanks to Dave for taking the time to do an test for elimination. So it actually means: there are just a few headsets affected and the issue goes with to a different location with a whole different environment. So it stays with the headset. So that rules out the rest of the equipment as a root cause. Additional test: Today I played also around 30min only in the environment of Oculus - since I wanted to test how it reacts to revive. -> same issue occured. Two things: - 1. - I could stop the issue for 15min when I cooled down the Vive - and I put the Icepack not over a sensor. So it took about 10sec to cool it down enough, so that the issue didn't return for around 15min - 2. - When I put a finger on the sensor (see pic below) then I also could stop the issue immediately. But when I lifted the finger, the issue returned immediately. It disappeared only during the finger was on the sensor (similar to the test of ) And it is worse when putting the head in a down direction. So this my additional information to the case. Question to everybody: Does anybody have a Deluxe Audio Strap? (I use one) Question to HTC: Could you maybe send out some brandnew units built in 2017 to the people who have the issue. I think we could make some comparison tests for you if we can reproduce the issue also with another headset?
  11. With all due respect - it's not a cheap 5$ mouse from around the corner - this is a 1000$ device! And I expect it to work flawlessly. Or exchange to a new one (not refurbished) without issues. And I'm also getting to start beeing disappointed since we don't receive any information what exactly is going on. At least I'm not sure how I feel, having a obviously overheating, malfunctioning electronic device directly on my face - with or without overtaped a sensor. But of course, this is only my view and my opinion.
  12. Hey MartinMarty That's what I call a workaround. Do you think it is a acceptable one for future? Regarding the cooldown. It would have been really interesting if this is also working the same like on my side. Not for having a solution, but for helping HTC to figure out the problem. By the way: Were your engineers able to reproduce the issue?
  13. Please give us daily reports in this thread (situation, news, next steps, possible workarounds, root cause analysis information). I would really appreciate this very much. Thank you. To everybody who is interested in how the Vive looks inside - with very hi res pictures!: https://ifixit-pwa.appspot.com/guide/62213 best, AGR-13
  14. wrote: ... Could you guys do me a favor and test it, too? I reported a similar discovery recently. Thanks MartinMarty - Just wanted to know if the issue also immediately disappears if you put cold on the Vive.
  15. Option HMD Serial and date of purchase: HMD S/N: FA6BXJJ00060 - purchased on 2017-01-11 Grey Screen: does it flicker or stay solid grey? - after 15-30min it first starts flickering more and more and sometimes it stays grey for 5 to 10 seconds. - in the SteamVR it shows that the basestations are grey - sometimes one, then the other, sometimes both. Even when both are grey it sometimes keep on tracking (witch is impossible). this happens only without controllers are online. - If the controllers are online, everything keep green in the SteamVR, even the tracking problem starts the same time after 15-30min When problem began (more or less): - around start of July 2017 when I finished my new PC build the issue started. Could have happened also before, but I'm not sure, because I didn't play a lot of Elite. What I know is, that in the beginning after the purchase on the older computer (ASUS Maximus VI Extreme / GTX 980 Ti) I was able to play EVE: Valkyrie for hours without any issues. But then it was January and room temp was around 22-25 degrees. Not sure if this had an effect. actual PC: Your location: - Bern, Switzerland OS Version: please provide actual version (build etc) by typing "winver" in the run command - Win 10 Pro Version 1703 (Build 15063, 483) Computer Make/Model or Motherboard if homebuilt: - ASUS Maximus IX APEX RAM: - G.SKILL Trident Z RGB, 32GB (F4-3600C17D-32GTZR) 2x 16GB, DDR4-DIMM, PC4-28800 (3600MHz), CL17-19-19-39-2N, Kühlkörper • Low Voltage (1.35V)/Intel XMP 2.0/LED Networking or other cards plugged in to motherboard: - Bluetooth ASUS BT400 Adapter Graphics Card: make/model any addtional built in graphics as well. Current driver version. - ROG-STRIX-GTX1080TI-O11G-GAMING - Driver Version 382.53 - Monitor lg 34um95 3440x1440 General Computing Environment and Set up: - Exsys 7x USB 3.0 Hub (USB ext.) - 2x Farbwerk LED Control (USB int) - 1x USB 2.0 x7 Aquacomputer Hubby7 internal USB Hub - 1x Aquacomputer Aquaero 6 PRO Steam Version: beta or public release - beta (also tested with public - same result) VR Home Beta enabled/disabled: - enabled (also tested with disabled - same result) Viveport installed/not installed: state which version if installed by going to - installed, Ver. 1.0.8889 (r1076) Oculus or revive or other VR environment installed: - Oculus revive was installed on the old computer, but not on this one Photo of the room your vive is in: If you can it would be good for us to see how the physical layout of the room your vive is in is set up. You can post publicly if you wish or send via PM to myself or @Synthesis or @VibrantNebula. (Foto will send directly) -> this is a screenshot taken when the issue is not happening. When it happens, then there is one or both base stations not visible. General: - connected by HDMI - room temp is around 28-30 degrees Celcius - I tested with different USB ports - same issue - Disabled every software and service, that could affect the system - same issue - tested a lot of options in the SteamVR - same issue Workaround: - the ONLY workaround I found - and it is 100% reliable is put a cold ice pack directly on the Vive. (a not-cold thing with the same size didn't change the issue - tested this to be sure it's not the covering of the sensors) Reproducing the error: - see the following thread on reddit: https://www.reddit.com/r/Vive/comments/6e5jne/base_stations_losing_connection_while_playing/ -> it describes it very well and suits also my experience. Vive in seated position, playing Elite Dangerous, beeing always on the border of the chaperone. But repositioning of the lighthouses didn't help. Last thing: it IS a overheating problem. no matter how it's happening. It's obvious.
×
×
  • Create New...