Jump to content


Verified Members
  • Posts

  • Joined

  • Last visited

Everything posted by joellipenta

  1. Still getting random grey and black screens. Last night, it happened not even two minutes after booting the headset. This is on the latest Nvidia drivers and the beta. I am going to uninstall the GPU drivers using DDU but I suspect this will still continue to occur. Here's the wireless log from last night if that helps. HtcCU_20210831_204315_20220.txt
  2. Same issue for me here as well. I played for about two hours last night and had two blackouts (it came back by itself in about 30 seconds) and one grey screen that required me to disconnect my battery pack and reboot the headset (this was all during a game of Population One and couldn't have come at a worse time). Prior to this update, I may only get one blackout every several hours of playtime (still frustrating, but not to this level). I will try to create a ticket and send logs next time it happens.
  3. Hmmm thanks for the info! That's certainly encouraging. Like I mentioned in my OP, it did work flawlessly at first, then the performance degraded to where I couldn't play for 4-5 minutes without gray and black screens. I'm using the XMP profile for the board and didn't change anything, but I could always try lowering to 3200MHz and see if that helps. I still have hope for increased compatibility from HTC and the MOBO manufacturers, so here's hoping!
  4. Thanks, @HackPerception. That's pretty unfortunate to hear. I will continue to hope that things get better because the difference between wired and wireless is night and day and I have invested quite a bit of money into this and cannot even use it.
  5. Over the last few months, I fought and scrapped and found myself in possession of the parts I wanted to build a new PC. The specs are: AMD Ryzen 9 5900X AORUS X570 Master EVGA RTX 3080 XC Ultra 32GB G. Skill Trident Z Neo DDR4 at 3600MHz 850W EVGA PSU When I first setup the Vive Cosmos Elite and wireless adapter, I was floored. Coming from an i7-8700K, the wireless was buttery smooth. Everything worked great...until it didn't. I started getting the gray screens and then the black screens and then sometimes, it wouldn't come back at all until a reboot. I have a fan mounted on the wireless adapter so the temps on the adapter max out at around 51C, so it's not that. So, I opened a support ticket (20210404023734) and was basically told it's not compatible. That stinks mainly because I built this PC because I wanted to really enjoy the wireless VR experience with the Cosmos Elite. So, back to wired for now. I have accepted that. However, I am hoping to have this thread here so others are aware and to use it as a placeholder for updates. I asked support if I could be notified of this being resolved but that wasn't really an option. So, is there any ETA anyone from HTC can provide? Thanks!
  6. @MercilessComa39 I posted this on another thread where I was having the issue. The replacement cable appears to have resolved my issue: "I received the replacement cable from Vive's support. Took 6+ weeks but I played tonight for about 2 1/2 hours and got zero blue, gray, or black screens. Everything seemed to be working really well! Fingers crossed that my issue was due to a bad cable. Not sure how much they cost out of warranty, but may be a good idea to offer those for sale to people should they have this isssue."
  7. *Update* I received the replacement cable from Vive's support. Took 6+ weeks but I played tonight for about 2 1/2 hours and got zero blue, gray, or black screens. Everything seemed to be working really well! Fingers crossed that my issue was due to a bad cable. Not sure how much they cost out of warranty, but may be a good idea to offer those for sale to people should they have this issue. I'll continue to test while I patient await the availability of the 5900x. Can't wait to see how this thing works with that CPU. Thanks, everyone!
  8. I just received the replacement cable from the HMD to the wireless adapter. My adapter was still under warranty so support shipped one (took more than 6 weeks to arrive). I am going to test it out later today to see if that helped resolve the issue.
  9. I purchased this cable per that post and it did not help. Still get the overheating.
  10. Just a quick update: After chatting with support and ordering the replacement cable on October 27th, it's still not here. They said it could take up to three weeks. It has been over a month. Hopefully it'll arrive before the end of 2020 so I can test wireless again.
  11. @Gyroquake No, not yet. They said it can take three weeks. I may try the wireless tonight while I wait now that I moved the WiGig card to the top PCI slot. If I have a chance to try it, I'll report back.
  12. Thanks for the suggestion but I always have the power plan set to High Performance. Hasn't helped me.
  13. Thanks for the info! I was able to put it in the PCIEX1_1 slot right above the GPU so it's now closest to the CPU. Fit like a glove. Once I get the new cables, I'll test and report back here. Appreciate it!
  14. Support is sending a cable so I'll test and report back, @C.T.. Thanks!
  15. The 3-in-1 cable from the headset to the wireless adapter? If so, no, I don't have an extra, just the short one that came with the wireless kit.
  16. Hi @C.T.! 1) The LED light was still green. I could still hear the game running in the background (I was playing Angry Birds VR which isn't graphically intensive). 2) The battery was fully charged prior to playing. I am using an Anker 20000mAh QC 3.0 battery that I had used previously with no issues. Not sure how to check its health though. 3) I am not using the stock USB cable. I purchased this cable per another user's recommendation several months ago and had no issues prior to the motherboard swap. Any other logs I could provide or other things to check? I'd really like to be wireless again. I miss the freedom so much when playing combat-intensive games like GORN and Blade & Sorcery.
  17. I recently swapped motherboards from an MSI Z370m Gaming Pro AC to an ASUS Strix Z390-F Gaming and am having an issue with the wireless adapter. I have the Cosmos Elite and previously, I could play for a while without getting the blue/grey screen or the picture cutting out. On the new motherboard, I couldn't even play for an hour before the picture went completely black and would not turn back on. Less than an hour of playing is pretty bad. I had to switch back to wired just to enjoy my headset again. My PC's specs are: i7-8700K @ 4.9GHz ASUS Strix Z390-F Gaming Motherboard EVGA RTX 2080 XC Ultra 32GB Corsair Vengeance Pro RGB DDR4 RAM @ 3200MHz Games are on one of two M.2 SSD drives The line of sight is perfectly clear as it was previously. I have the WiGig card in the bottom PCIEX16 slot if that makes a difference. I know the 8700K only has 6 cores but I have seen plenty of other users have great success with the wireless kit and I'd like to be a part of that club. Thanks! HtcCU_20201024_194519_13212.txt
  18. I'm glad this worked for you but it did not for me. I just reinstalled W10 and even added a faster M.2 drive as my main drive. My CPU and GPU combo should be more than enough for wireless, and it did work well in the past, but now it doesn't. I've resorted to going back to wired for the time being so at least I can play again. Not sure what the cause is, but hopefully someone can/will review this thread to help shine a light on this.
  19. So as a test, I hooked the headset back up as wired and played Star Wars: Squadrons again. No issues, no pixelation, no screen cuts. Definitely something is up with the wireless. Not sure if it's the beta firmware I'm running or not, but I essentially have $300+ of useless tech right now. And it seems I'm not alone. Is there anything we can do/check to get this resolved? While being wireless doesn't matter as much for seated games like SW:Squadrons, it's not the only game I play. I'd like the freedom back, please!
  20. I'm having the same issues. Cosmos Elite, i7-8700K @ 4.9GHz, and an EVGA RTX 2080 (non-super). I tried playing Star Wars: Squadrons last night and not even 5 minutes into my first match, my FPS TANKED and everything got pixelated. 15 seconds later, no screen whatsoever. Luckily you can toggle VR on and off in the game so I was able to continue the match. However, this is the first time this has happened and now I'm hesitant to even use the wireless which costs a pretty penny. Any suggestions from support would be great because I have invested a LOT of money in this product and not being able to use wireless out of nowhere is a lousy feeling.
  21. I have experienced minimal light leakage but I suggest taking the time to ensure you're putting it on properly. I wasn't at first and that made a difference. Fit the headset plush against your face first and then pull the strap down over your head and tighten. Once I started doing that, I found much less light getting in.
  22. @Michal I have a similar system and have 32GB 3666MHz RAM. I recently upgraded from 16GB 2666MHz and haven't noticed a significant difference in VR.
  23. I was able to resolve this! I had cleaned out the PC not long ago and when I plugged everything back in, I plugged the USB for the link box into a 3.1 Gen2 port. Apparently it doesn't play nice. I moved it to a USB 3.1 Gen1 port and it immediately reinstalled the driver for the mic so I'm back in business. Thanks for your help, @C.T.!
  24. Thanks for the suggestion! Just tried but could not get the Cosmos mic to appear. I also tried resetting the headset via the Vive Console and still, nothing. I am on the beta branch if that makes a difference and it did previously work. Out of curiosity, the mic isn't embedded in the original Vive's faceplate, is it? Just wondering where its physical placement is. Thanks!
  25. I was able to remove the Bigscreen Audio driver (never going to use that anyway). USB drivers are all up to date. Only thing that has changed was the swapping of the stock Cosmos faceplate with the External Tracking Faceplate. Attached the DxDiag report. Thanks! DxDiag.txt
  • Create New...