Forum Replies Created
-
Posts
-
Like said earlier I get back to you via mail if I find something unusual in the logs. On first sight there wasn’t anything unfortunately, no obvious error message.
I don’t have a Vive Pro 2 unfortunately, and so far you are the only one reporting an issue with it. Whether that is because the headset is uncommon or whether it’s an individual issue related to your setup is impossible to tell at this point. I’ll keep an eye on the matter. If more reports like yours come in, I’ll get a Vive Pro 2 to check it myself directly.
For the time being all I can really recommend is sticking to your WMR headset if that works fine.
No double posts, please. I have removed your other post regarding the same issue. Thanks for your understanding.
Can’t replicate this here, but I’ll take a closer look. please use a gamepad instead for the time being. Be aware that gamepad movement works a bit differently compared to playing the game on a monitor to allow movement with just the left stick. Instead of strafing you can turn with the left stick.
You have to make sure that WMR is set as your OpenXR runtime. The WMR portal should display a warning message on launch if that isn’t the case.
If you are sure WMR is your OpenXR runtime and it still doesn’t work for some reason, there isn’t really much else to recommend than using SteamVR instead.
Because the second logfile you sent still was a log file with Afterburner and all your other background tasks running. Your log files are of no use for me in regard to checking for other issues while there are potentially interfering programs running unfortunately.
Doesn’t matter whether the Lenovo headset works with the other apps running.
As suggested above please disable everything that doesn’t belong to Windows. If the issue still occurs afterwards, please resend a trouble shoot data archive without the other apps running. Your log files are of no use for me in regard to checking for other issues while there are potentially interfering programs running unfortunately.
If you want to play laying down, stick to mouse emulation based head tracking.
DirectVR head tracking is not suited for playing laying down, it presumes that the game’s horizon is where the actual horizon is (just like head tracking in probably 99.99% of native VR games).
Just briefly checked the log. There is a bunch of stuff running that obviously falls in the categories mentioned in the touble shooting guide as potentially interfering (e.g. MSI Afterburner, Skype, Slack). The logfiles are of no use in regard to checking for other issues as long as obvious trouble maker tools like Afterburner are running.
Please check the trouble shooting guide again in that respect. If the issue still occurs afterwards, please resend logfiles without potentially interfering backgrounds tasks running. Rule of thumb: disable everything you have running in the background that doesn’t actually belong to Windows.
Please also check whether your Lenovo headset works with SteamVR instead of OpenXR, that’s a good way to check whether the issue is really headset related.
Last but not least please check whether all SteamVR settings are at their default values. Judging from the log files there is some SteamVR supersampling active, which looks kind of odd considering the headset’s already high native resolution.
The archive has to be created after the issue occurred. Sending one for each headset would be great. While I can see what headset is active in the logs, two distinct archives for your Lenovo and your Vive headset make things easier.
to create two distinct archives simply restart vorpX when you switch headsets, that will clear the log files.
Please create a trouble shoot data archive in the vorpX config app and send that to support at vorpX com. I’ll take a look at it next week and let you know if the log files show anything unusual that might help with your problem.
That’s the most common issue with interfering progams, but with G3D more/other functions are hooked, so there are more things that can go wrong when another program is also hooked into a game. Just disable/uninstall everything running in the background that might potentially interfere.
Since it works in Z3D mode it’s highly unlikely that your issue is a headset specific issue. There is no difference at all regarding how vorpX sends images to the headset in G3D mode compared how it does that in Z3D mode.
1. If it works in Z-Buffer mode, it can’t really be a headset specific issue. How vorpX interacts with the headset is unrelated to the 3D method. More likely that some program on your PC interferes by also hooking into games. The trouble shooting guide on top of this sub forum has more details on the matter.
2. You have to run games at higher resolutions for better image clarity. Games run at the resolution set in their graphics/video options, not at your headset’s display resolution. If you don’t have a 4K monitor that allows you to set high resolutions, check the ‘Custom Resolutions’ section in the vorpX help for a step-by-step guide regarding adding higher resolutions than your monitor allows. Caveat: key here is finding the right balance between performance and image clarity, G3D + super high resolutions can be extremely demanding performance wise.
No promises, but I’ll take a look at it. Bought it early on but never checked it until now because of the existing mod.
Can’t really say anything overly useful in that respect except that so far I’m not aware of any issues. That doesn’t really mean anything though, of course…
In general I’d be as sceptical as you are though. In a certain way there always is some additional software between SteamVR and the headset since headset vendors have to provide drivers/runtimes for SteamVR, so maybe HTC just lets users configure their driver. If on the other hands like Pimax their software adds another frame interpolation layer that wouldn’t really be ideal. I have no clue though what’s the case here.
I’d check whether the headset supports OpenXR natively (i.e. not via SteamVR). If that’s the case, you could use it entirely without SteamVR.