Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
2) WMR has decided that the headset can't start at 90hz. HP themselves don't understand why, have issued me with a new headset, and that one only runs at 60hz too. Suggests WMR software problem - nobody knows what it is.
3) WMR keeps messing up the tracking.
4) WMR keeps not being able to find my boundaries.
5) WMR keeps telling me it can't connect because of a cable problem. Meaning computer restart.
6) WMR keeps randomly going into "slug mode" where the FPS on all software drops to about 5 - 10 fps. Restart computer is the only fix.
7) WMR has no shortcut to starting SteamVR and the controllers are useless at doing it through a virtual desktop.
None of these problems ever happened with my ageing Vive Pro.
Otherwise, everything works fine!!
I tell you, if HTC or Valve released a high res headset, I'd bin my G2 in a heartbeat!
My system: 3090 10900k 64 gb RAM HP reverb G2.
I don't believe you. I know that point 2) is unique to me (and even the finest technical minds at HP can't understand why I'm experiencing the problem). Everything else I have found echoed in reviews and forums all over the web - along with a problem where the lenses turn off when the volume is set too high!
It seems to me (from my research and experience) like the G2 headset is a fantastic piece of hardware, but the software & controllers are absolute ♥♥♥♥.
4) Why do you have boundaries when you are in a treadmill? Turn off the boundaries. Mine are off all the time.
You have a pretty rare setup. Does the treadmill have conflicting drivers perhaps. This multitude of issues seems likely to originate from all the different hardware. Treadmill, Knuckles. Remove items from the setup and build it back up again until it fails again. Troubleshoot it. Remove other unrelated USB hardware as well.
What issues persist when using just the G2 and G2 controllers on their own?
Seems unlikely you can disable WMR as it runs the headset.
Looking at your other 90hz thread - get the rid of any overclocks. Just because it doesn't bluescreen - doesn't mean the system is stable. You have to create a baseline where you know the hardware is stable and methodically work back up adding hardware and overclocking.
My visual boundaries are off, but WMR insists on finding boundaries for the inside out tracking, and it can never find them correctly.
I've tried it all with nothing plugged in except headset, mouse and keyboard. All these problems are still there.
I rarely use WMR controllers. I connect index knuckles with trackers. The problems persist with / without controllers trackers or treadmill.
My system has been overclocked by the builder. It has been running at higher clockspeeds throughout the length of my having it. It never causes any problem whatsoever. I get no instability either. I ran my Vive pro for about 4 months before getting the G2 and had no problems.
The problems began as soon as I installed WMR, and only occur when I am running WMR. I have gone back to running my Vive pro for segments of time and had no problem whatsoever.
It wouldn't seem logical to conclude that the problem is overclocking since the problem exists only with WMR. I wouldn't know how to underclock, and wouldn't trust myself to mess with clock speeds anyway, because I don't know what I'm doing (and my system is frigging expensive).
Ought to mention: I ran my G2 at 90hz for about a month. Then it stopped working at 90hz gradually over a 24 hour period (black screen flickers, black screen periods, and then wouldn't start unless dropped down to 60hz) around mid January. System was overclocked as usual throughout that time.
It isn't a hardware fault, I've replaced it all with HP and still have the problem. HP tech team can't explain it. Microsoft completely ignore all contact from me.
https://www.reddit.com/r/HPReverb/comments/khm4a8/hp_reverb_g2_running_insanenly_bad/
Apart from that:
Did you checked the NVIDIA driver? Not sure if they fixed it, but there were reports that newer drivers did not work with WMR and even Nvidia suggested to install an older version.
Also an interesting read:
https://www.reddit.com/r/HPReverb/comments/lo2s11/wmr_devs_identify_performance_bottleneck_between/
Best tip for high performance graphic cards is to set render resolution to 100% and NOT to Automatic.
I found something odd this morning. When I start WMR it automatically changes my monitor refresh rate to 50hz. No idea why (it should be 60hz). I change it manually, and stil it seems to default my screen to 50 when I close it and start again.
Really odd.
Maybe you try a clean driver refresh using DDU (DisplayDriverUninstall). But first search which driver version is recommended with WMR (not sure if they fixed that RTX 3x00 issue, maybe just start with an approved older version)
Did you download the OpenXR developer tools for windows mixed reality?
Under developer settings inside the app there is a checkbox to use the latest openXR preview. That is what i am using, maybe it will help.
Also about your 60hz issue. Did you mess with the quality in the mixed reality settings for windows 10? It has options for 60, 90, or let windows decide.
Sounds like you have already done and know about the things i mention but just in case i thought i would mention them to be safe
It is on the microsoft store.
It comes with a couple of useful functions for MSFS 2020 and allows you to set the resolution of your headset and turn on and off reprojection and also has a check box that gives you access to the preview build of OpenXR witch is the VR plug in that game uses to run WMR headsets. Not sure if it would help you with other specific issues tho.
Has there been firmware updates released from HP since you got your headset? always a good thing to keep that up to date
(Thanks by the way - I'll check that out)