Jump to content

groslala

Verified Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

6 Neutral

About groslala

  • Rank
    Explorer

Recent Profile Visitors

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

  1. Thank you CMDRZOD ! Seems to work for me as well. So random disconnects could just be a conflict between the PCI-E card and Windows power management after all...
  2. So, no answer to my question about the difference between my 1440 x 1700 pixels per eye wireless Cosmos Elite and the 1632 x 1632 pixel per eye (upgraded to 2448 x 2448) Vive Pro 2. I guess I have to wait for independant comparative tests... maxstep: HackPerception already answered your question. HTC use almost no compression, contrary to Oculus, that's why the image is much better and there is no latency, but it's much heavier. With the resolution of the VP2, it reaches the limits of the existing wireless technology bandwidth, even at 90 Hz. Concerning the price, Oculus have a very diffe
  3. Thank you for your detailed answer. From a practical point of view, will there be a big difference between the wireless Vive Pro 2 and my wireless Cosmos Elite, concerning resolution, not FOV of course?
  4. Do you confirm the HTC wireless won't support the full resolution of the Vive Pro 2? https://uploadvr.com/vive-pro-2-wireless-limitations/ 1632 x 1632 won't make a big change compared to my wireless Cosmos...
  5. Will the Vive Pro 2 be compatible with the HTC wireless? I guess the resolution and maybe the power requirement could be a problem, but that would be great. HTC still has the best VR wireless system, and considering the bandwidth of the 60 Ghz wifi, it should be possible, when we see what Oculus does with a simple wifi 5 connexion (but great compression algorithms).
  6. OK, solved. Restarted everything, and, I don't know how, but it works! 😋
  7. I changed from AMD to Intel to improve my performance in wireless VR but for the moment it's a disaster (everything worked fine with my previous AMD config).☚ī¸
  8. OK, did the clean install and just reinstalled everything... But nothing's changed: "Impossible to find any headset". Wired VR is OK. Green flashing light on my wireless module. Blue light on the PCI-e card.
  9. OK, found the solution: I deleted the Vive Wireless folders in C/Programs and C/ProgramData. But I still can't play wireless: "headset not detected". I checked all the connections. My wireless module has a green flashing light Rebooting doesn't help
  10. Hello, I just changed my hardware from AMD to Intel (CPU + motherboard), updated all my drivers and my Windows edition, and I can't play wireless anymore. First my wireless Vive could'nt be detected, so I decided to test it wired, everything is OK. Then I decided to uninstall/reinstall everything: Vive drivers, Viveport, Vive wireless app, SteamVR. The problem is I can't install the Vive Wireless app anymore: I get an error message: "Fail to shut down SteamVR. Please shutdown SteamVR and try again.". But Steam VR isn't running and rebooting doesn't help. Any idea?
  11. Just found that: https://casques-vr.com/vive-cosmos-elite-le-casque-seul-et-la-faceplate-bientot-disponibles-16564/amp/ Yay, nice move HTC, I'll soon be able to upgrade my Vive, at last!
  12. Thank you for the answer! I am just realizing that the Vive Pro is still one of the best HMD on the market and that no other device relased after it brought any significant improvements. Critics mainly focused on its price and that's the reason why I never considered buying it till now. But its price drop to 600 $ (cheaper than a Cosmos + external tracking faceplate that finally might not be better) could make it the best option for wireless PC VR in the end (I'm trying to build the best wireless VR combo).
×
×
  • Create New...