Forum Replies Created
-
Posts
-
Using the left stick with the controller emulation works like hitting the “W” key (walk), rspectively “SHIFT+W” (run) when you press the stick further. So, pressing it only gently will make you go slowly, pushing it completely forward will make you run. This is how all programs with similar functionality (XPadder for example) work.
Sometimes this is inverted, in this case you can change the “Invert Walk/Run” option on the gamepad page of the ingame menu.
Binding the thumbstick buttons seems indeed wrong, apparently the back/start buttons and the thumbstick buttons are swapped in the binding menu. You can change the thumbstick button binding by assigning to back/start and vice versa. Funny that noone noticed this so far.
Probably an issue with wireless vs. wired x-box controller. I will look into it. Normally ESC should be bound to back and start per default, not the thumbsticks.
Hi dredmama,
vorpX cannot make Rift Coaster, or in general DK1 programs, usable on the DK2. It only works with ‘normal’ games that were not made for the Rift.
You can disable head tracking in the vorpX config app. This should allow you to use OpenTrack without geting a warning message.
Planetside 2 was never tested here, but reportedly works fine with a gamepad.
For Arma 3 please check the thread below. It’s currently buggy but there seems to be a temporary workaround:
Please check the supported games list in the “Basic Facts” menu above. Not much of what you list has been tested with vorpX.
vorpX generally tries too hook into every DX9-DX11 game, so many games that are not on the list will also work (usually without Stereo 3D), but there are no guarantees in these cases.
BTW: To get good head tracking in racing sims which do not have mouse look you should take a look at OpenTrack, which can emulate TrackIR input using the Rift (might not be DK2 ready yet).
Hi AntDX316,
Neither LFS nor Asseto Corsa are on the supported games list, so they might or might not work. There are no guarantees with games that do not have a profile. Many will work (in most case without Stereo 3D), but not all.
To see the whole screen you can use vorpX’s EdgePeek feature (press middle mouse button). This and an few more useful things are explained in the quick reference in the documentation.
Also please make sure to run all games at a resolution of 1920×1080 for the DK2.
Just in case: Did you go through the DK2 setup guide in the documentation? In case of issues, please use the most compatible settings mentioned there (DK2 as primary display). Every step in the guide is important. If you use Windows 8, please also check the according sticky above.
Sounds like a neat idea, I just want to add a word of warning: A few days ago I got a report from a user who had problems using vorpX with a TeamViewer display driver installed.
If after trying the above vorpX doesn’t work anymore, uninstalling TeamViewer might solve the issue.
First thing you should do is to disable/disconnect your third monitor. You may add it later, but to get things running it’s better to exclude any possible additional source of errors.
Afterwards please check the DK2 setup guide in the vorpX documentation. You basically have two options: Using the DK2 as secondary display is more convenient, using it as primary display is more compatible. All steps in the guide are important.
Games should be set to 1920×1080 and launched in fullscreen mode.
If you use Windows 8, please also check the Win8 sticky above, unfortunately some Win8 related information did not make into the setup guide.
vorpX only makes monoscopic games playable on the Rift. It can not deal with older Rift native titles that already have Stereo 3D and lens warping.
This probably is an issue with conflicting refresh rates, similar to what many native demos show when running in extended mode. You can try the following things:
1. Enable Vsync if disabled.
2. Setting the DK2 to the same refresh rate that your monitor runs with
3. Using the DK2 as primary display (don’t forget to switch vorpX to “Use system settings” in that case.
4. Using the DK2 a only monitorThe game it itself is fast enough to run smoothly on almost any PC with vorpX.
The console command should work in all cases normally, it’s an internal Skyrim function that even works without vorpX being active. The only reason why it possibly could fail is maybe a mod that overrides that setting or a somehow messed up Skyrim install.
In case you use an international keyboard, make sure to use the key below the [ESC] key to open the console, in some cases it does not show the [~] symbol.
If that doesn’t solve the problem, trying a fresh Skyrim install without any mods may be worth a try.
The option you chose is the most compatible one, but for many games a more convenient setup also works. Simply set the DK2 as secondary display and then choose “Show only on Rift DK2” in the display selection box of the vorpX config app.
With this configuration vorpX tries to force games to the Rift. Just be aware that this does not work for all games, so in some cases you will still have to fall back to the configuration you use now.
I’m not 100% sure yet, but it may be possible that New Vegas in contrast to FO3 changes the resolution to something the DK2 doesn’t like to play logos/videos on startup.
Normally changing the GPU driver to GPU scaling instead of display scaling should be able to deal with something like that, but I had no luck with that either. Your mileage may vary though, so that is something you could try.
This sounds odd. Especially using the DK2 as primary display AND setting vorpX to “Use system settings” display wise shouldn’t cause any problems.
This way games simply open on the primary display like normal (the DK2 in that case) and vorpX should kick in just like it always did.
Just in case: If you changed anything on your machine since using vorpX last time with your DK1, please check whether there may be something installed that can interfere with vorpX. The trouble shooting guide in the documentation has a few hints in this regard.