Forum Replies Created
-
Posts
-
Your problem will be gone in a few days. The next version will have a smaller and darker logo without any bright colors.
vorpX had 64bit support since day one. With the current version you have to uncheck the “Run as administrator” checkbox in the config app for 64bit to work.
BTW: “Run as administrator” is usually not needed with vorpX except for games that also need admin rights. Might do more harm than good in other cases.
Only a few more days. Things get tested, bugs are found, bugs are fixed, things get delayed. The very nature of software development.
As always, thanks for your amazing patience.
If vorpX does not hook with multiple games in a similar fashion, the most likely cause is another program on your PC interfering with vorpX. Some possible candidates are: graphics driver add-ons, video streaming and recording software, chat programs, and in general everything that can show content over games or does also “hook” into the graphics pipeline. Also anti virus programs may cause issues.
If you didn’t do that already, please restart your PC and check the trouble shooting guide in the vorpX help. It lists some (but not all) examples of programs which might cause issues when running together with vorpX.
Skyrim (maybe Outlast too): If you have a gamepad attached to your PC, please make sure to disable it in the game options. Skyrim disables the mouse when a gamepad is enabled, which also disables vorpX’s head tracking.
You will still be able to use your gamepad through the built in gamepad emulation in vorpX.
If that doesn’t work, please make sure that no other program is accessing your Rift at the same time. This might even be a crashed one. if in doubt, reboot your PC.
For games without a mouselook function (like many racing games) things are a bit more complicated:
One option is OpenTrack, the other option to emulate a gamepad axis with the vorpX head tracking. The first option is the better one, simulating a gamepad has a few drawbacks.
A. OpenTrack compatible with DK2:
https://www.dropbox.com/sh/544fbhsokdpy3n7/AAAKwl6BluqwT9Xn2slyp0dCa
B. Head tracking as gamepad
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.
5. Map the emulated ‘gamepad’ to the look around functions in the game you want to play. Do not leave this step out, it’s vital!The options below this should be more or less self explanatory except maybe Deadzone Correction, which efectively eliminates analog stick deadzones set by the game.
Now you are able to look around in your cockpit. The view has to be centered from time to time because of possible yaw drift (should be greatly reduced with an calibrated magnetometer). There is a shortcut for centering.
Issues with converging images usually are releated to either the IPD (interpupillary distance) setting in vorpX or a wrong resolution setting. You should check the things below:
1. Set all games to 1920×1080 fullscreen for the DK2
2. Do not use an Oculus profile in the config app.
3. Dial in the IPD manually. You might have to set it slightly lower than your real IPD due to a calculation glitch.Step 3 can be done with direct feedback ingame on the display page of the vorpX config app. Lower (or raise) the IPD value until you can converge without any eye strain.
There is no 3D in unsupported games like the specific Stalker game you mention. Supported games have Stereo 3D, in regard the Stalker series currently this applies to Call of Pripyat (an possibly others when using the DX9 renderer).
BTW: immersion in VR is a result of many factors, and S3D isn’t even the most important of them. The most important factor for VR immersion is the ability to walk and look around in the game. You can test that yourself with a simple real world experiment right now: close one eye and check whether you are still immersed in your surrounding.
You can run them in DX11, and they probably will hook just fine, there might just not be any Stereo 3D. All VR related functions like head tracking and most additional vorpX functionality will be intact though. So they will still be fully playable.
The problem with the Stalker games is that they all use the same .exe name for the actual program, which confuses vorpX’s game identification. You might get lucky with DX9/Z-Buffer 3D for all Stalker games, but there is no guarantee unfortunately. Many things in regard to 3D-creation, be it Z-Buffer or Geometry 3D, depend on game specific heuristics. A (slightly) smarter game identification, which can account for Stalker-like cases, is on the long-term todo-list.
Hi, normally the steps in the second post above should suffice. Going offline in Uplay is highly important.
This issue is almost certainly related to your virus scanner. Please try to deactivate or uninstall your virus scanner and temporarily and see whether the problem persists.
Quite a few games will allow you to give a custom depth value to HUD elements (incl. the crosshair) in Geometry 3D mode shortly, which mitigates the issue for the most part. Won’t apply to everything, but at least to all games that allow to somehow separate the HUD programatically inside vorpX, for which there are several methods now. Not sure ATM whether Black Mesa is among them though.
The other way to achieve something like laser sight is using one of the Z-Buffer 3D modes. In these modes the crosshair is always drawn at the depth of the scene elements it is overlaying.
Please make sure that you paste in both the name and the key exactly as shown in the mail you got, Name INCLUDING THE E-MAIL ADDRESS. It’s best to copy and paste the whole line. There is an example image attached to the key e-mail that shows how the dialog is supposed to look like after pasting in the data.
Also please check for leading or trailing whitespaces after pasting in the data. Those might cause problems.
If that does not solve your issue (it almost certainly will), please send a mail to support |at| vorpx com.