Forum Replies Created
-
Posts
-
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.
To get your key, simply follow the short instructions in the license dialog and send us your request code. We need this code to create your key. You will receive your key shortly afterwards.
@ Rambo : If you already sent us your request code, but did not receive your activation key yet, please contact support |at| vorpx com. In that case something did go wrong. In most cases this takes only minutes, it sure doesn’t take a day.
Plesse also check your spam folder.
TrackIR: I’d love to integrate TrackIR emulation, and technically that would certainly be possible. Unfortunately legal reasons prevent me from being able to do so. The company behind TrackIR does not allow the usage of their API with anything else than their hardware. Unfortunate, but they are of course entitled to handle it this way.
Oculus runtime: The vorpX installer normally does a version check to prevent installing an older version of the runtime. Unfortunately Oculus changed the place where the version info is stored in 0.4.3, so currently this check fails in some cases. This glitch will be gone again soon.
Hi rufus, As in most cases your key was sent a few minutes after we received your request code. If it didn’t reach you, please contact support |at| vorpx com.
The vorpX ingame menu should work in every game that vorpX is able to hook into. If it doesn’t, there is something fundamentally wrong with your setup.
Please try to press the DEL key relatively shortly, otherwise the key press might not get registered correctly.
Did you read the various guides in the help? Below you find what you can do about a “zoomed in” image.
You should also check the quick reference that explains a lot of useful vorpX functions which allow you to use invisible menu parts (EdgePeek) in corners etc. Do yourself a favour and really read these things. Saves a lot of head scratching. :)
You can get most games look almost perfect in regard to the FOV. And even for those that do not offer FOV control, neither directly, nor through vorpX, there are functions in vorpX to make them playable, although not in a perfect way. From best to worst here is what you can do, depending on the game.
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)