Forum Replies Created
-
Posts
-
The game is not supported yet, it’s out for merely 12hrs.
However, it should work in 2D simply by starting it from Steam. Rift as secondary, “Show only on Rift DK2” in the vorpX config app works just fine here. As always setting the game to 1920×1080 beforehand is important.
Someone on Reddit mentioned he had to start the game windowed and then move the game window to the Rift and switch to fullscreen afterwards. None of that is necessary here though, but maybe that helps in your case.
Irrespective of possible starting issues I would strongly suggest to be a lttle bit patient. You probably won’t regret it, a profile is being worked on right now.
Never heard of that issue before, and you surely aren’t the first customer from Spain. Does this happen in all games?
The key code for the DEL key should be universal. Which DEL key did you try? Normally the one above the cursor keys is the right one (probably named “Supr”), not the one on the numpad.
You should also the see the game already in Rift view (warped split screen). Otherwise vorpX probably didn’t hook at all and the menu can’t be opened because of that.
You have to adjust the head tracking sensitivity once for every game in the vorpX ingame menu (input page). Unfortunately it’s not possible to have a default value that fits everyone, since this depends on your individual mouse sensitivity.
No idea TBH. If you haven’t done that already, you could try to just exit/restart vorpX Control and see whether that also helps. Doing this resets some internal book keeping vorpX does while running and should have the same effect.
Star Citizen was never tested here BTW., so it might be a game specific problem. Although that sounds unlikely.
If you use your DK2 as the secondary screen, you have to set vorpX to “Show only on Rift DK2” display wise in the config app.
If that doesn’t solve the issue and you use mods, please try a fresh Skyrim install without any mods.
If that still doesn’t solve the issue, there might be something on your system interfering with vorpX. Generally everything that can interact with or show content over DirectX games can cause issues. Also temporarily disabling your antivirus program is worth a try.
Hot candidates are: graphics drver add-ons like Geforce Experience, or MSI Afterburner etc., desktop streaming apps like Splashtop, video recording software (FRAPS, OBS etc.) and many chat programs like (X-Fire, Skype etc.).
FSX does not hook currently when a DK2 is used. This will be fixed with the next update.
Doom 3 does not work with vorpX unfortunately since it uses OpenGL for rendering. vorpX currently is DirectX 9-11 only.
No problem, just send us the new request code that is displayed in the license dialog like you did when you first regeistered vorpX.
Head tracking works out of the box for almost any game that has mouse look, regardless whether it is on the supported games list or not.
For some other games (like many racing titles) you either have to configure the vorpX head tracking as gamepad axis (see below) or use an external solution like OpenTrack which can emulate TrackIR input. The game needs to support TrackIR for that of course. OpenTrack usually is the better alternative, although a bit complicated to use. Gamepad emulation has a few inherent problems like high latency, but is still better than nothing.
OpenTrack for DK2: https://www.dropbox.com/sh/544fbhsokdpy3n7/AAAKwl6BluqwT9Xn2slyp0dCa
vorpX 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.
@ artura: 1. + 3. sound like a good idea and easy to implement, will be done with the next update. 2. isn’t as easy, but will probably be available for DirectInput games in the next version. Not sure yet how many that are, but a few important ones (Bethesda RPGs for example) are covered.
@ Trancer: The image scale for EdgePeek has been reduced by 10%, maybe that’s enough. Making this user configurable would be easy, but I’m a bit hesitant to add a setting for this, the menu is already pretty overcrowded. Will think about it, but no promises. Key mappings will definitely be configurable in the future, not sure if that will make into the next version. For now I changed [SHIFT][SPACE] to [ALT][SPACE], since I recently experienced exactly your issue myself.
Hi stereoviewer,
Unfortunately all three games you mention do not have a profile yet. PS2 and Hawken are running in ‘unsupported’ mode, which usually means they have image doubling, head tracking and most other VR related vorpX functions enabled, but no 3D. So what you describe sounds normal.
A list with games that have Stereo 3D with vorpX can be found here: https://www.vorpx.com/supported-games/
Hawken uses the Unreal Engine IIRC, so you might get it working with full 3D by making a copy of the main game .exe and renaming it to UDK.exe. This *may* work, but probably with more graphical glitches than usual due to missing game specific optimizations.
ESO supposedly works (in unsupported mode) when you force it to use the DX9 renderer which can be achieved by editing an .ini, wasn’t tested here though.
1. Open C:Users[Your Name]DocumentsElder Scrolls OnlineliveeuUserSettings.txt with a text editor
2. change the graphics driver line to: SET GraphicsDriver.7 “D3D9″
The most important thing to get you “into the game” is to get the FOV (field of view) right. Ideally you should have a FOV of ~120° in vorpX. This is highly important, in many ways even more important than Stereo 3D.
Games that allow you to do this and have Geometry 3D in vorpX are indistinguishable from native Rift apps in terms of the visual experience.
You have various options to do that depending on the game. From best to worst:
1. Ideally a game allows you to set the FOV to 120° in its options menu, which is true for a few games, but not that many
2. For various other games you can use the Game Optimizer in the vorpX config app, which can add the necessary tweaks automatically. More will be added here soon.
3. For many other games you can manually edit an .ini file or use a console command. Googling for “FOV + gamename” brings up tutorials for many (maybe even most) games.
4. If a game has no option to set the FOV in the engine itself, but has Geometry 3D support in vorpX, you can use the “3D FOV Enhancement” in the vorpX menu.For games that don’t allow any of the above options, you can compensate for the lack of FOV with some post process helper functions vorpX has to offer, but these come at a price (for example black bars)
5. If absolutely no option is available to really increase the FOV in a game you can use one of the letterbox aspect ratio modes or the ImageZoom function.
6. Alternatively there is a post process 2D FOV Enhancement in the vorpX menu that works on everything. This causes image distortion though, so this should be the last resort.With all these options available, almost any game can be made reasonably well playable. With the first four options you can usually get a perfect result in regard to the FOV.
I will look into it. Seems to be a good fit for VR as far as I can tell from the first few minutes. Mostly exploration and a slow pace.
If you got this problem with multiple games in a similar fashion, it’s quite likely that something on your PC is blocking vorpX. There are various kinds of programs that also hook into games, not all them are obvious cases. Try to disable/uninstall all such software. A few examples are:
– Additional graphics driver software that you might have installed. For example: MSI Afterburner, GeForce Experience, Lucidlogix Virtu
– Video recording/streaming software you might have installed. For example: Fraps, Dxtory, Open Broadcaster, Splashtop
– Chat programs that can show content over DirectX, like Skype, Mumble, Evolve, X-Fire
– The Steam/Uplay/Origin ingame overlays
For WOW please also check whether switching from 64bit to 32bit or vice versa makes a difference. Normally both should work, but in some cases one might work better than the other. It’s also best to use DirectX 9 instead of DirectX. You can change these settings in the WOW launcher.