Forum Replies Created
-
Posts
-
If you have Geometry 3D enabled and get the positional tracking calibration window on startup, it almost certainly is active. Try to walk up to something close to check it. Not sure what else to recommend. Apologies.
Since I can’t know whether you have done that: please check the setup guide in the documentation and try the most compatible option (Rift as primary display). Make sure to follow the guide completely, every step is important.
If you are sure everything is correct in this regard, please check the trouble shooting guide. You might have something installed that blocks vorpX.
Interesting info. Thanks for letting me know. So far that case, odd.
Head tracking: sounds like you are playing with inverse mouse. You can invert the vorpX head tracking accordingly on the input page of the vorpX ingame menu. You can also adjust the headtracking sensitivity there.
Portrait is not correct in Windows 8. Set the Rift to Landscape flipped, otherwise the image will be displayed too small and/or offset. That is an error in the vorpX documentation. Sorry for the confusion.
Also please make sure to follow the advice about setting the FOV to 120. This extremely important to get a natural looking image. What exactly you have to is described in the first vorpX window that opens when you start Skyrim.
These are not the settings that are mentioned in the documentaion. Please follow the guide exactly. Cloning will not work with the DK2.
I could write everything here again, but it’s really easier if you follow the guide in the vorpX documentation.
OK, if I understand correctly you are running the DK2 in clone mode, right?
This will not work. The vorpX documentation has a step-by-step setup guide with pictures. It’s probably easier to check that, before I explain it here again without the images. It’s important to set the display options in vorpX correctly, depending on whether you use the Rift as primary display or not. But that’s all explained in the documentation.
Running games windowed should not be necessary, might even do more harm than good.
I will look into a way to intercept the mouse input for a future release, which would allow to disable vertical mouse movement. Can’t promise anything though, since it’s not clear whether that will work out.
Something around 130 as FOV is also fine, the perfect value varies a bit based on your personal eyesight.
This screenshot is not from vorpX. You probably have a d3d9.dll in your Skyrim folder. Please remove it, it doesn’t belong there per default.
There should never be a d3d9.dll in any game directory since this causes a conflict with vorpX.
Plese send a mail to support |at| vorpx com. I can you provide you with a rollback option to the last version if you can’t solve the issue.
Do you use Windows 8? There is in error in the vorpX documentation about the display orientation. In Win8 it has to be set to set “Landscape flipped” instead of “Portrait”.
Your description sounds like the issue that is caused by using “Portrait” in Win8.
You could try to switch from the games from DX9 to DX11 or vice versa. DX9 is the preferred mode, since it has Geometry 3D, but if one of them does not work, the other may be worth a try.
This has to done with an .ini tweak unfortunately. Here you find a short tutorial for Dirt 3: http://forums.steampowered.com/forums/showthread.php?t=1907032
dirt2.exe and dirt3.exe should remain on the exclude list. These are the launcher programs, not the actual games. vorpX should not hook them.
You can do a full factory reset in the config app (trouble shooting page) to bring them back if you can’t add them back manually.
@ qasim: I can’t open the images. Could you please resend them as e-mail attachment to support |at| vorpx com. Thanks.
Still no button, since the auto detection was improved. Apparently it still doesn’t catch everything.
I will implement an “emergency cursor hotkey” with the next release. Easy to do, but I didn’t think it was necessary anymore. Sorry.
Just it checked it here, using the exclusive fullscreen mode. Both 64bit and and 32bit worked simply by starting from Steam, no shortcut, not even Rift as primary display was necessary. Forcing to the Rift through the vorpX config app worked just fine. So I fear, I’m out of ideas in regard to your issue.
Little tip in case you can make into the game: The 64bit version doesn’t seem to show the vorpX cursor in the main menu, so 32bit will be easier to use.