Forum Replies Created
-
Posts
-
Theoretically that could be used for decoupled look in some games, but it would cause too severe artifacts, missing geometry depending on view direction etc, so unfortunately that’s unfeasible.
You should be able to use 0.4.3 with the current vorpX version, I’m not aware of any ill side effects. If you want to stay on the safe side and don’t absolutely need 0.4.3 for something else, I would recommend to stick with the version vorpX installs though.
The vorpX installer does a version check to avoid installing an older runtime, but unfortunately Oculus changed the registry key they store the version number in with 0.4.3. So this check fails in some cases (like yours). Will be fixed with the next update.
Please set everything up as shown below. Do not leave out anything. When you follow all five steps, every game will open on the DK2 automatically, even without the config app.
1. Reinstall vorpX to reset everything to default
2. Set the Rift to Extend Desktop mode with the Oculus Config Tool
3. Make the the DK2 the PRIMARY display in Windows
4. Set the orientation of the DK2 to “Portrait” or in Win8 possibly “Landscape flipped”
5. Run all games at 1920×1080 in fullscreen mode, not windowed.Yoy should also make sure to set the FOV to 120. Depending on the game from best to worst here is what you can do in this regard:
1. Set the game FOV directly in the game if it provides to dial in an FOV of 120°,
2. Set the game FOV directly with the vorpX Game Optimizer (vorpX config app) for games that support it.
3. Set the game FOV to 120 manually through an ini tweak or external tool (avaliable for many games, google FOV + game name).
4. Use the 3D FOV Enhancement in the vorpX ingame menu (availabe in Geometry 3D games).
5. Use one of the letterbox aspect ratio modes in the vorpX ingame menu and/or ImageZoom
6. Use the 2D FOV-Enhancement in the vopX ingame menu (be aware that this distorts the image)There seems to be an issue when using Z-Buffer 3D (although it doesn’t look like your description), but the game runs fine in Geometry 3D here using the Steam version of the game.
We also didn’t receive any other reports about something like this as far as I’m aware of. At this point I can only assume that this is specific to your system or setup, so all I can give you are a few general hints unfortunately:
1. Check whether the game runs in 1920×1080, other resolutions might not work correctly
2. Reset the game profile in the vorpX config app
3. Do a factory reset or reinstall vorpX (this resets everything)There already is an option called “G3D Latency Enhancement” on the input page of the vorpX ingame menu which eliminates input lag almost entirely. It applies head rotation directly in vorpX, completely circumventing the games input pipeline.
You can experiment with that in every Geometry 3D game. Setting it to something around 0.3 should usually suffice, above 0.7 lag is even gone in games that run below 60/75fps (read Skyrim).
One small caveat: enabling this in Skyrim creates a slight rendering artifact with far clouds/fog when turning your head. But that’s not really bad.
In case you haven’t done that already the other thing you can/should do is adjusting the head tracking sensitivity in vorpX until turning your head feels fully natural.
Can’t say anything in regard to the mod unfortunately.
The only correct resolution for using vorpX with the DK2 is 1920×1080. Other resolutions probably lead to games being displayed wrong one way or the other,
Please also make sure to set the Rift to “Portrait” mode in the Windows display config (Win7), or maybe “Landscape flipped” (Win8).
With this setup vorpX will work just fine whwn using the DK2 as primary display. This is actually the most compatible option.
In regard to the config app crash temporarily disabling or uninstalling your virus scanner may be worth a try.
If that doesn’t help, you can use vorpX with the above setup. Most things that can be done in the config app can also be adjusted ingame after pressing [DEL].
Currently not, but you won’t have to wait long for that anymore. The next update which will include this option will definitely happen this month.
Won’t work for all games in regard to playing with the mouse, but Skyrim (and probably all other Bethesda RPGs) is among them.
When using a gamepad with vorpX’s internal gamepad handling it will work with everything (including games that normally don’t work with a gamepad).
Thanks for letting us know. They probably whitelisted the current vorpX version know. If it breaks again after a future vorpX update, you may have to disable Kaspersky again temporarily (or add an exception).
This is not a vorpX problem, it’s a Kaspersky problem. vorpX does memory patching to hook games, which some overzeleous antivirus programs wrongfully may detect as malicious behaviour. They are just guessing, and their guess is wrong in this case.
Personally I would recommend to use Microsoft Security Essentials, which usually doesn’t scare users with wrong detections.
If you want to stick to Kasperky, you should add exceptions for vorpControl.exe and vorpConfig.exe. All AV programs allow to add exceptions manually.
Already implemented for the next version. Someone else requested that a few weeks ago for another reason. The way it’s done the hotkey doesn’t change performance, but UI issues etc. can be resolved this way temporarily.
Not 100% sure yet whether customizable hotkeys will make it into the next release, but that’s definitely on the list too.
This clearly sounds like an input (gamepad) issue of some kind. Please disable the gamepad in the Skyrim options. Also reset the Skyrim profile in the vorpX config app, or reinstall vorpX.
If that does not help, please also try a fresh Skyrim install without any mods. Maybe there is an issue with a mod you might have active.
After installing vorpX the license dialog automatically appears when you double click the “Start vorpX” icon on your desktop or start vorpX from the start menu.
If I understand you correctly, that is already possible. You can emulate a gamepad axis with vorpX by following the steps below.
Just be aware that this does not work as good as mouse emulation. Gamepad input is filtered quite heavily by most games, so you usually end up with pretty high latency and other issues. I would recommend to do this only if necessary, for example in racing games that do not have mouselook.
1. Press [DEL] to open the in-game menu
2. Go to Input page
3. Set ‘Handle Gamepads Internally’ to Off
4. Set ‘Headtracking as Gamepad’ to Relative or Absolute depending on the game. You should get a grasp of what is better quickly.If this is done, the head tracker is now a gamepad axis. The final step is to go to the game’s input options and map look left/right/up/down to the ‘Rift-Gamepad-Axis’, exactly as you would do with a real gamepad.
Hi Seelenmord,
Thanks for the comprehensive guide! Much appreciated. One addition: You can make your life a little bit easier by using the DK2 as secondary display in Windows. This involves two steps:
1. Set the DK2 as secondary display in the Windows monitor configuration.
2. Set vorpX to “Show only on Rift DK2” instead of “Use system settings” in the vorpX config app.You should also set Skyrim to 1920×1080. Not sure whether you did that, didn’t see it in your post.