Forum Replies Created
-
Posts
-
@ 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)Something like that *may* happen if the DK2 is used as primary display. When you follow the steps with the DK2 as secondary display, this does not happen.
Changing the display orientation of the DK2 is a basic technique in regard to using the DK2, which is also mentioned in Oculus own user guide, it’s not specific to vorpX. You will also need to do this for many native demos.
To reiterate the two possible vorpX setups:
A. The convenient one (does not work with everything)
1. Set the Rift DK2 to “Extend Desktop to HMD”
2. Use the Rift DK2 as SECONDARY monitor in Windows
3. Set vorpX to “Show only on DK2? display wise in the vorpX config appB. The compatible one
1. Set the Rift DK2 to “Extend Desktop to HMD”
2. Use the Rift DK2 as PRIMARY monitor in Windows
3. Set vorpX to “Use system settings” display wise in the vorpX config appIt is important to choose the right setting in the vorpX config app according to your display settings in Windows. It is important to choose the right setting in the vorpX config app according to your display settings in Windows. For a more detailed guide including screenshots please check the DK2 setup guide that comes with vorpX.
Can’t promise anything yet, but the game is high on the list. Will be looked into in the next few days.
IPD calculation is indeed not quite correct currently. 60.9 sounds a bit too low in your case though. Please check whether the game runs in 1920×1080. Other resolutions can cause issues similar to what you describe.
For head tracking in Dirt 2 (and other games without mouse look) you have two options:
You can either use OpenTrack to simulate TrackIR input or configure vorpX to simulate a gamepad axis. The first option is the better one, simulating a gamepad has a few drawbacks.
A. OpenTrack for 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.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.
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.
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.
You have to change the orientation of the DK2 in Windows. For Windows 7 the orientation has to be set to “Portrait”, for Windows 8 the right value sometimes is “Landscape flipped”.
You do not do this within vorpX. It is done in the Windows monitor configuration.
You can access a step-by-step DK2 setup guide with some images, which explains all necessary steps in detail, in the vorpX help.
Thank you for giving me reason to investigate this. Strange that it got unnoticed so long, probably caused some grey hairs for quite a few others too.
Issue is fixed, next version will also have proper 64bit support when run as admin.
Found it: You probably started vorpX with the “Run as administrator” checkbox checked, right? This disables the 64bit process for yet unknown reasons (probably a path issue when starting the process).
Running vorpX as administrator is hardly ever necessary. The only situation where this makes sense normally is playing (very) old games that require admin rights themselves. Might actually do more harm than good in most other situations.
One more thing: If you finally get it working, please be aware that there is no profile for the game yet. You can use the UDK.exe renaming workaround, but it will of course not be ideal.
Currently not. This *may* be an option for the future, but I can’t tell anything specific at this point.
The 64bit process is definitely missing, why that may be the case I can’t tell unfortunately. Just checked it on two Win 8.1 machines to make sure there is no general Win 8 issue in this regard with the last release version.
If you use something else than MS own antivirus solution, disabling/uninstalling your AV program might be worth a try. Maybe also reinstalling vorpX, just to make sure the issue isn’t caused by a corrupt file. Not much else I can imagine apart from that.
You can try to change the extension to .exe and start it manually. It’s very possible though that strange things happen when doing this, so I do not officially recommend it! I wouldn’t even be surprised if it refuses to start this way. Can’t remember currently.
Are you sure it’s not running already? May be only visible on the details tab of the task manager in Windows 8.
Never heard of anything like this before, so it might just have been a coincidence. You should run every game at 1920×1080 with vorpX.
Please also check the DK2 setup guide in the vorpX documentation in case you haven’t done so already. It explains the two possible display configurations that you can use vorpX with. In short:
A. The convenient one (does not work with everything)
1. Set the Rift DK2 to “Extend Desktop to HMD”
2. Use the Rift DK2 as SECONDARY monitor in Windows
3. Set vorpX to “Show only on DK2? display wise in the vorpX config appB. The compatible one
1. Set the Rift DK2 to “Extend Desktop to HMD”
2. Use the Rift DK2 as PRIMARY monitor in Windows
3. Set vorpX to “Use system settings” display wise in the vorpX config appIn both cases you have to change the orientation of the DK2. Usually to “Portait”, in Windows 8 in some cases to “Landscape flipped”