Forum Replies Created
-
Posts
-
Try to re-center head tracking (ALT+SPACE). After re-centering your current real world position is the actual game position.
Not in all games the FOV can be adjusted by vorpX, that is exactly like before where the config app optimizer also did not cover every game. Some games just don’t allow to adjust the FOV via tweaking an ini file.
Every game that previously was handled by the config app optimizer is now handled by the new Direct VR optimizer though.
Nothing has been taken away, on the contrary.
Exchanged for “Head Tracking Multiplier” in the cinema mode UI. Instead of just on/off you now have more fine grained control. Setting the multiplier to 0.0 does what locking did before.
There is nothing to bring back since you can still do that. You can manually apply a +/- 20° offset to the computed value on the DirectVR page of the ingame menu. For games where the FOV is set via an ini tweak make sure to click “OK & Save” afterwards and restart the game if you are prompted to do so.
Rebooting your PC may be worth a shot. In Unreal Engine games the memory regions that have to be scanned are best described as moving targets in layman’s terms. Uncluttered memory after a reboot can help. Also disable real time scanning in your AV scanner if it’s not Windows Defender. Some more aggressive AV scanners can cause issues with vorpX’s Direct VR scanner.
Apropos clutter: posts like this one are best posted in the “Technical Support” sub-forum to avoid unnecessary forum clutter.
I’m not sure whether I approve making your dad shit his pants, but you can activate a license on two PCs. The caveat is that normally both have to be yours since this is not meant for sharing a license. Your dad’s PC is OK though.
Just send the request code shown on the second PC to the register mail address and you get a second key.
I know that you like to tweak, and I know that it’s tempting to ‘optimize’ for your own needs, but all I can say, especially after the latest update, is: don’t disable the settings optimization.
What you learned the hard way in regard to Witcher 3 is true for many, many more games: vorpX tweaks settings the way that are best for it. Disabling this feature will cause you more problems like this one that simply aren’t there if you just let vorpX do its job.
In theory it should just work. Nothing is impossible, but I would be highly surprised if it wouldn’t.
Personal note: if you can easily spend the money, upgrading from the regular Vive is probably worth it. But if for example you are a student with a more limited budget, I would recommend to think twice (or thrice) about it. Roughly calculated the pixel density of the Pro will be slightly better than Oculus Rift, which currently has the advantage in this regard due to its lower FOV. While that certainly is a noticable improvement, I wouldn’t consider it enough of an upgrade if one can’t easily afford the Pro.
That could be resolved by adding Direct VR head tracking, which would be possible for the game. Will probably happen sooner or later, but since there is a VR version of the game it’s not super high priority.
The actual render camera location that vorpX has access to is not necessarily the same as the one a game uses for collision detection etc. In some games that might be the case, in others it will not. Positional tracking in vorpX works great for peeking around corners, dodging, moving a step forward/backward and similar things, but not necessarily for freely roaming an entire 3x3m playspace. Hence the recommendation to stay more or less in place that you see when a game starts.
The obvious thing first: please double check whether “Steam VR” is selected as your headset type in the vorpX config app.
If you use multiple GPUs (or a laptop): please make sure that the internal Intel GPU is disabled and both your monitor and the headset are connected to the nVidia/AMD GPU.
Apart from that:
There might be an injection conflict with some other program on your PC. Many programs also hook into games and can cause such an issue. Not all of them are obvious.
Hottest candidates are: virus scanners, any sort of CPU/GPU utilities, game video recording/streaming software, chat programs and generally everything that can show notifictations in games.
Best way to trouble shoot this is to disable/uninstall programs running in the background.
If you can’t solve the issue this way, please try to start a few games, then create a trouble shoot data archive in the vorpX config app and send that to support |at| vorpx com. I will then check whether I can find something that you may have overlooked.
I have no experience with that mod, but please check whether you maybe accidentally enabled vorpX’s gamepad override (“Mouse and Gamepad Settings” page of the ingame menu). It is disabled per default in WoW, but in case you enabled it, any other gamepad input would be blocked, so that might potentially be the issue. That’s really just a guess though.
If you can’t make the mod work, you can use the internal vorpX gamepad override, which maps a gamepad to mouse+keyboard and is freely configurable in the vorpX menu. Probably not as good as a dedicated mod, of course.
If you made any changes in the vorpX settings, please reset the profile to its default values in the config app (trouble shooting page).
Also please make sure that the game is updated to the latest version, just in case it’s an issue related to changes in the game’s rendering pipeline.
Please disable nVidia hairworks, that will probably solve this.
Just in case: vorpX should do that automatically normally. So if you disabled the automatic settings optimization, please re-enable it.
Just in case 2: please never report something as an issue that does not happen with profile settings at default values. Thanks.