Forum Replies Created
-
Posts
-
@ rusty:
Try to reset the profile to default in the config app. If you played the game before with vorpX, the settings might not have been fully updated with everything the weapon hide feature needs. Also please don’t change any settings that affect the game FOV (e.g. the ImageZoom value). The default is right anyway.
On a sidenote: odd that you have to run the scanner at all. For Portal 2 the scan results are fully cacheable, and the profile comes with an updated cache for the latest game version (until the next game update makes a re-scan nevessary). Try to delete the ‘C:\ProgramData\Animation Labs\vorpX\Cache\dvr’ folder, maybe vorpX couldn’t replace an older cache file or something.
@ dborosoev: Can’t really say anything else right now. I’m currently reinstalling the Steam version to check that one too for you, just to be sure it’s not some issue that only occurs with the Steam version. Other than that: apart from apparently noone else having this problem so far I have no clue in general how the game’s keyboard input should have been broken by vorpX. Nothing is impossible, of course.
I’ll keep an eye on any potentially incoming report that sounds somehow similar.
What you could try on your end is checking whether the issue also occurs when you use your VR controllers in keyboard/mouse mode. That might also be a viable workaround for your problem BTW, VR controllers can be used either as gamepad or keyboard/mouse. Even if they fail in kb/m mode, maybe you can use them as gamepad.
Edit: Steam version also working fine here.
First please make sure that both your Windows 10 and the WMR software are fully up-to-date. OpenXR is still very much a moving target, everything has to be up-to-date. The Windows 10 version should be the current feature release dubbed 20H2. You can check that by clicking on the start button and typing ‘winver’ + Enter.
If you are sure, everything is up-to-date, please create a trouble shoot data archive in the config app after launching a few games and send that to support at vorpx com.
@ dborosev : Checked with a gamepad earlier and after reading your post I checked again with mouse and keyboard. The radial menu works perfectly fine here, I pretty much did nothing but selecting objects with the mouse wheel for a few minutes.
Not sure what to recommend other than generic stuff like resetting game settings and the vorpX profile to default or checking your GPU drivers are up-to-date. Might sound super-silly, but if your mouse is wireless, maybe try fresh batteries.
Since there have been no other reports like yours so far, currently I’m leaning towards thinking that this is likely some mysterious issue with your setup. If it’s a an actual, more widespread vorpX issue, there should be more reports like yours coming in shortly. I’ll keep an eye on that.
Glad that you find it useful. And BTW sorry that this hasn’t been done way earlier. Was sitting on the I-should-do-this-sometime list literally for years. Works not only with WoW, but with every game that uses the standard Windows ‘hardware’ cursor.
@ ShibbyPanda72: Untick the “Use built-in audio device” checkbox in the config app. vorpX now switches to the Quest audio device automatically, which didn’t work before.
@ dborosev: I’m not really sure if I understand the issue, but I’ll check the game later. The game’s first ingame menu screen that pops up after pressing ESC is fairly sluggish even without vorpX if that’s what you mean.
Probably just the screen getting scared of you.
Seriously: Indeed a bug, actually a hot candidate for the yearly most-stupid-bug-award. Not directly related to the new scale/distance calculation, but while I was at that I cleaned up some nearby code… The issue is that essentially forward/backward movement gets applied in the opposite direction. Funny that I never noticed that, I should move back and forth more while EdgePeeking, I suppose…
I’ll upload a hotfix addressing this within the next hour. Thanks for the heads-up.
That sounds odd for sure. I’m EdgePeeking here all day long pretty much every day.
Please try a full factory reset in the vorpX config app (‘Trouble Shooting’ page), just in case today’s update messed up some settings. In case you have any additional input devices (e.g. a racing wheel or flight stick) connected to the PC, also try to remove them for testing.
If it’s the latter that causes the issue, it would be great if you could let me know.
Can’t replicate any of that for the life of me. 2019 crashes on my main dev box on start currently (with or without vorpX), but I just checked 2020 and it runs as great as always. My usual test is starting a race event with full grid. Except for the start with everyone in front of me I pretty much get stable 90fps with G3D at 1440p and with roughly medium graphics details. Looks great, feels great as well.
That’s with a 3080 though, so obviously a fast machine. But on my 1080 test box the F1 games run also fairly well. Should be absolutely no problem to run these games at least with stable 45fps on a decent PC.
The only thing I can really recommend is resetting the vorpX profile to default and using either the low or medium detail presets provided by the game without adjusting anything manually. Also make sure to let vorpX audjust the game’s settings in case you disabled that.
Hooking issues almost always are caused by some conflict with another program that also hooks into games.
The most likely candidate would be some invasive third party antivirus program. If you happen to use anything else than Windows Defender, try to remove it. There is no risk involved, Windows Defender will kick in instead. There is no real need for third party AV on Windows 10 anymore, Windows Defender is an excellent AV solution for years.
If that does not solve your issue, please check for other potential conflicts. The trouble shooting guide on top of this sub-forum has more details on the matter.
Indeed, the ‘Use built in audio device’ function doesn’t work as intended for the G2. It’s not really necessary anymore anyway since all vendor runtimes have options to define how audio is supposed to be handled. Pretty much a relic of the past.
I’ll upload a quick fix later that disables the function for OpenXR. Thanks for the heads-up.
For Windows Mixed Reality headsets this update is really quite something. WMR was always extremely clunky with SteamVR compared to other headsets. I’m really happy to have that out of the way. With OpenXR WMR headsets finally are on par with how native SteamVR headsets like Index or Vive work with SteamVR.
The weapon should appear when you press one of the related gamepad buttons or keys normally. Did you maybe raise the camera height before to lower the weapon on the screen? That’s pretty much the only thing I can imagine to be the issue here.
Might make sense to link the weapon y-position to the camera height modifier now that the camera height doesn’t have to be changed anymore to change the weapon position, didn’t think of that.
Your key should still be valid. I fixed a small bug in the check routine, shouldn’t really affect its outcome though (and doesn’t here in a brief test). Probably some weird coincidence. If you need a new one, just shoot me a mail.
Just checked this for you. Working fine here with the “Elder Scrolls Online [vorpX]” cloud profile. Please double check whether you imported this one, not maybe some of the user settings that might also be on the cloud. That’s necessary currently since a recent game update broke the profile that came with your vorpX version.
If that does not help (it should), please check again later today with the next vorpX version.
Try to run the game windowed. There currently is an issue that leads to vorpX losing the connection to the headset under some circumstances in some games. Will be fixed in the next vorpX (incidentally later today).
Provided that’s what causing your problem until then switching to windowed instead of fullscreen should do the trick.