Forum Replies Created
-
Posts
-
Skyrim and Bioshock are supposed to have a DirectVR scan option. If you don’t see it in these games, something is wrong. Might be worth to check whether you maybe have renamed the .exe files for some reason which would prevent the profile from loading correctly.
Caveat: for Bioshock please use original DX9 version of the game, the remastered version (Bioshock HD) currently is not supported.
Just a little heads-up that the FOV mod should not be required normally since the game is supposed to have DirectVR FOV.
Unfortunately that doesn’t work anymore since two or three vorpX versions due to a pretty stupid bug. Will be fixed for the next update.
Did you check the support FAQ?
I purchased vorpX before and need another download link.
Please request a new download link here.
Might be an issue with the DotNet version. The installer is supposed to check that, but maybe that failed for some reason. It has to be 4.6.2, installer is available here.
BTW: On Windows 10 the correct DotNet version is available per default.
If you use any other AV programs than Windows Defender, try to uninstall them. Some more invasive AV programs make it very hard to fully disable them unless they are uninstalled.
Windows Defender provides decent AV protection these days, using three AV programs at the same time sounds a bit like overkill anyway.
There is no official RAGE profile. If there is a custom profile created by a user in the cloud, it’s probably 2D. vorpX cannot provide stereo 3D for newer, shader based OpenGL games like RAGE. I don’t know what Supermodel is, sorry.
For Quake 3 please make sure to run the DirectVR scan after entering a level like indicated when you start the game. After a successful DirectVR scan the game automatically has perfect 1:1 head tracking without you having to adjust it in the vorpX ingame menu.
That should not happen anymore. Please try to reinstall the update manually, then do a full factory reset (config app/trouble shooting) and afterwards make sure to leave all gamepad related settings for GTA5 at their default values.
Please check whether you are running the installer (or vorpX) in some compatibility mode. If so, please disable that. The installer was created with the exact same settings as always, so I’m 99.99% sure that this is an issue caused by your system.
If the above is the case: please never ever run vorpX in any compatibilty mode. Doing so will cause vital internal functions to fail, which can and will result in severe and unpredictable problems.
vorpX 18.2.4 has been released. This is a maintenance release that addresses the issues below.
- Opening the vorpX ingame menu with a gamepad can no longer cause games to hang.
- Vive/Touch controller gamepad stick emulation no longer feels jumpy under some circumstances.
- Vive controller trackpad rotation sensitivity is not framerate dependent anymore.
- VR controllers cannot be considered in use anymore although they were never used.
- Deus Ex: Mankind Divided: fixed issue with occasionally losing depth when exiting menu screens.
- Left 4 Dead 2: DirectVR resolution and tweaks added.
Without Touch controllers the above does not apply to your setup and disabling the override should always work as expected. I’ll look into this again, but for now I’m out of ideas.
For the time being you can either change the vorpX gamepad mapping to your liking in the ingame menu or play with mouse and keyboard.
BitDefender is one of the most problematic AV programs in regard to vorpX. It almost certainly causes problems and on top of that makes it very hard for its users to disable it fully. You will have to disable multiple components, including the so called “advanced threat protection”.
I would highly suggest to uninstall BitDefender instead of trying to disable it. Since Windows 10 has decent AV protection built in (Windows Defender), additional AV software usually is not required anymore these days.
Checked this today.
What you see is the intended behaviour. When VR controllers are reported as active and set to keyboard/mouse emulation (which is the default), they override the gamepad setting in the vorpX menu.
If possible without unwanted side effects, I’ll change the way this is handled, otherwise I’ll add an according hint to the vorpX menu that will be shown whenever the above is the case to avoid future confusion.
Try to turn off VR-controllers in the vorpX menu or simply switch them off hardware wise in case you use Vive wands. That should help.
What you see is the intended behaviour. When VR controllers are reported as active and set to keyboard/mouse emulation (which is the default), they override the gamepad setting in the vorpX menu.
If possible without unwanted side effects, I’ll change the way this is handled, otherwise I’ll add an according hint to the vorpX menu that will be shown whenever the above is the case to avoid future confusion.