Forum Replies Created
-
Posts
-
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”
There should be a process named vorpControl64.dat in your task manager which starts automatically when you run vorpX. If that process is running, vorpX normally also hooks 64bit programs.
Thanks for the setup tips. Will add them to the Game Optimizer to automate this.
Driving FOV: I only played the first driving sequence so far,and was under the impression the FOV changes depending on speed. Odd effect. Will try to find an ini setting to turn that off.
@ OculusRiftRocks : Their FOV calculation is a bit strange. The 120 you can dial in in the options don’t look like 120 at all. Hence the 150 ini tweak recommendation.
@ baggyg : No problems here. Hooks just fine in 5/5 tries when started from Steam without any special tricks using the last release version of vorpX to make sure it still works with what everybody uses.
Hello,
I checked the e-mail address you used for registering to the forum against the purchase database. There is an entry with this e-mail address, but the purchase did not succeed.
I can’t tell why it failed unfortunately, but I’m almost certain that you were not charged for the failed attempt. You can verify that by checking your Paypal account.
You can either try again using the normal method or contact support |at| vorpx com for an alternative purchase method, which might work better for you.