Forum Replies Created
-
Posts
-
The behaviour with the menu open is the normal one, so tracker seems to be functioning.
Haven’t come around to test this yet, but one thing I forgot yesterday: in case you have a gamepad connected to your PC, you could try whether disonnecting it helps. Some games disable the mouse input when a gamepad is active, which also disables vorpX’s head tracking. Not sure ATM whether this is true for Risen 2.
Never tried an external gamepad tool tbh, you should be able to use xpadder if you change the “Handle gamepads internally” option in the vorpX menu ([DEL]). You can also change key bindings for the internal gamepad emulation there, that will most likely be enough, except for complex multi-key macros.
Skyrim runs below 60fps on most machines outside, hence the judder. Reducing graphics settings will help, also vorpX’s “G3D Latency Enhancement” (input page of the ingame menu). If you can live without Geometry 3D, Z-Buffer 3D doubles your framerate, but has a less convincing 3D-effect and no positional tracking.
Glad you found a way to make it work. I will check whether there is a bug in screen metrics related calculations somewhere.
Make sure all games are set to 1920×1080 if you use a DK2, also please make sure that you don’t have any unusual GPU scaling settings in your displays drivers control panel. I’m not sure anymore whether you use Win8. In that case, please check the Win8 sticky above.
Unfortunately I do not know currently what might cause a general convergence issue besides using an Oculus Profiles, which is a confirmed bug, and cannot replicate it at this point in time. Sorry for not being able to help you better in this regard.
Unsupported games do not have Stereo 3D. VR related functionality like headtracking etc. is intact in unsupported games, given that a game has mouselook, but there is no S3D.
The latest runtime (0.41) is indeed required, regardless of DK1 or DK2. Normally the vorpX setup should install it, but maybe that fails in some cases. The runtime can be downloaded from oculusvr.com .
Your convergence issue sounds extremely odd. Especially that you seem to have this across everything you try. This is not normal at all.
Just checked ME2. Geometry 3D seems indeed broken, will check that. But there was zero issue in regard to double images or anything similar.
You should check out the various aspect ratio modes BTW. In games that don’t allow to set the FOV, using one of the letterbox modes will greatly help (at the expense of black bars at the top/bottom). You can also change the image zoom in the ingame menu if the mouse wheel fails.
Check the ‘Basic Facts’ menu above.
One caveat: not everything has been tested with DK2 yet to get the update out as fast as possible.
Many more games will also work BTW, only thing missing in these cases is Stereo 3D.
There may be an IPD issue, please try to lower it. I got one similar report recently, and apperently lowering the IPD solved it. Will be investigated. You definitly shouldn’t use an Oculus Profile, that’s buggy in the current release for sure.
Probably not your issue, but just in case: Make sure games run at 1920×1080 for DK2 and 3D-Strength isn’t set too high.
I have no idea what might cause this. All that vorpX does when checking the device is initializing the HMD and checking its name.
If the problem persists, and you can’t find a solution, please send a mail to support |at| vorpx com. Sorry for not being able to be of more help.
Sounds like neither the control app nor the injected DLL can initialize the Rift. One other thing I can think of is that you might not have the latest Oculus runtime (0.41) installed. It can be downloaded from oculusvr.com . The vorpX setup should install it automatically, but maybe that failed for some reason.
If that doesn’t help, please send your vorpx.log to support |at| vorpx com. The log can be found in your temp folder (Usually C:\Users\[User]\AppData\local\temp).
@ iloctus: The black smear is an issue with the DK2 OLED display. There is an option to fix this software wise on the display page of the vorpX ingame menu. Also please make sure to set the game to 1920×1080 for DK2, this may be the cause of your display issue.
@ david: besides what moarveer says, you may have to set the DK2 as primary display and the vorpX config app to “use system settings” display wise. That’s the most compatible option.
The DK2 has to be turned on when you start vorpX otherwise it won’t be found, maybe that’s the issue.
Also please try to use the Rift as primary display and set the vorpX config app to “Use system settings”. That’s the most compatible option. The documentation has a step-by-by guide with pictures. Direct to Rift will only work with very few games currently.
And just in case: Did you try the usual things like rebooting and changing the USB port?