Jump to content

Beta_Tester

Verified Members
  • Posts

    170
  • Joined

  • Last visited

Everything posted by Beta_Tester

  1. Hi @C.T. - just noticed that the controller battery status has vanished when using motion controllers & faceplate (see attached). Not sure which version it vanished on? I used to be able to check the status when bringing up the Lens.
  2. Vive Wireless is heavily dependant on CPU resource. The compression process is performed entirely using the ViveVRCompositor.exe process. If your CPU isn't up to the task, then you will start to loose frames and eventually (if it is really bad) you will start to see really noticeable compression artefacts. Check your CPU usage when using Vive Wireless. Is it getting towards 100%? You can also try increasing the priority of the ViveVRCompositor.exe process to AboveNormal or High.
  3. @C.T.Getting a weird display issue with Vive Lens and the Cosmos-style loading screen. I am getting a white box. I'll IM you some screenshots and I've create an Issue Report for this.
  4. Is the headset tracking properly? Normally the controller tracking should pick up once the headset is working. One thing to try is to make sure there isn't any cool white lighting in the play area. This can cause tracking issues.
  5. Are you saying you haven't got any basestations? The Cosmos Elite uses Valve external tracking, and won't work without the basestations & the original or gen2 Vive controllers. Can you please confirm?
  6. @C.T.Selecting that option makes no difference. SteamVR still doesn't launch automatically and if left alone, eventually the compositor crashes out (see screenshot).
  7. Same here. ViveVRCompositor.exe hangs on launch and shows a green screen on the HMD. Once SteamVR is manually started, I'm getting strange display issues in VIVE Lens (like the menu options in the Library & the LH controller - see attached screenshots) and Origins. @C.T. submitted an issue report for you - no 20210515221414
  8. This has been fixed in the latest Viveport update. Unfortunately I've now lost sound ☹️
  9. Hi. Your specs are pretty low for the Cosmos Elite headset. It's probably worth leaving Task Manager running to see if the CPU or GPU are maxing out just before the issue starts. The fact that the ViveVRcompositor.exe thread remains running suggests it is getting into some sort of state - possibly as a result of CPU availability. If this doesn't seem to be an issue, you could try disabling hyperthreading (some have reported improvements by doing this). Finally I'd try generating an issue report from the VIVE Console when the issue occurs, as this will probably enable Vive support to pinpoint the issue.
  10. This is really interesting. I've got a similar setup to yours, but I have absolutely no issues with Vive wireless at all (literally zero)!!! I've had this running on Cosmos Elite and std. AMD Ryzen 7 5800X ASRock X570M Pro4 Sapphire Radeon RX 6800XT 16GB Corsair Vengence RGB Pro @ 3200 MHz I don't even see any issues with the fact that the WiGig card is plugged into a PCI slot connected to the chipset (rather than a CPU bus-connected one) - which I know others have reported issues with. Try dropping the overclock on your RAM - I know that others have reported grey screens when running at the maximum speeds.
  11. Looks like a fix is incoming in the next Viveport Streaming update for this issue. Hopefully not too long now!
  12. Yes I am having exactly the same issue with the pass-through camera option. I keep on accidentally launching something from the Steam VR dashboard.
  13. @Tony PH Lin - does anyone have any update on this? I've been waiting for 4 months for a fix. I currently have an Focus Plus headset that is pretty much useless at the moment.
  14. @C.T. @VibrantNebula Any idea when AMD cards will get motion compensation for the Cosmos headsets? It's been on the cards for over a year now. https://www.vive.com/us/support/cosmos-elite/category_howto/what-is-motion-compensation.html
  15. Hi - I assume you have an AMD graphics card? I reported this issue in September last year. It appears that the issue is driver-related. If you can downgrade your Radeon drivers to 20.5.1 you will find the issue is resolved. However if you have a 600p series card, you don't have this option. Given up on HTC fixing this issue. Bear in mind this is "enterprise support". As if! @VibrantNebula can you shed any light on this issue?
  16. Not sure this is the correct forum as you've posted in the Vive Focus forum. What did you download and what headset have you got?
  17. Also noticed that I am getting grey screens again fairly regularly - including some extended ones where the headset appears to restart. I've downgraded back to the public release and I don't appear to be getting any grey screens. I'll upgrade back to the beta and put in an Issue report.
  18. I'm assuming that you are on the latest GeForce drivers? HL Alyx is pretty intensive graphically even on the lowest settings - it might be that your 1080Ti is not up to the job.
  19. Hi @C.T. - just been testing this release and I've noticed that the controllers stay on even when the HMD goes into standby. I've ended up with some flat batteries as I hadn't noticed. This is with the std Cosmos and Wireless.
  20. Have you tried reseating all the cables - especially between the wireless adapter and the HMD (that one gets put under a lot of strain)? Is the Vive Console reporting that all is OK? Also it's probably worth testing a different battery pack if you have one.
  21. Sounds like a network problem. Ideally the PC needs to be connected to the router via a wired connection. The HMD connection should be on 5GHz WiFi. What is the spec of your PC? Not sure if you can connect via USB. @VibrantNebula will be able to advise. There is no way to connect via a private network unfortunately.
  22. Skipping the headset setup is correct, but then you need to launch the apps or games from the ViveportM launcher in the Focus Plus headset itself. Before that go to the Viveport settings on your PC and click the "Check PC" button. This will test your PC hardware and start the streaming service. If you are prompted by the windows firewall to allow rrServer.exe to listen to incoming traffic then confirm this. Once you have done this, then go to the headset itself. There is a section under library called "On my PC (Beta)". If the headset is not connected then it will walk you through connecting, and then you can launch any SteamVR or Viveport PC titles directly. It will automatically start StreamVR when required. It's a pretty neat implementation.
  23. Working fine here! What's the issue you are seeing?
  24. @JustinVive Currently on one of the internal builds - 4.13.623.1
×
×
  • Create New...