Ralf

[Ralf]

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.

[Ralf]

Looks perfectly normal except for the renamed udk.exe.

[Ralf]

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.

[Ralf]

@ 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.

[Ralf]

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.

[Ralf]

I’m on it right now. It’s basically working, but I still can’t promise anything yet due to a potential issue with the Uplay DRM.

You should be able to get into the game though with the current build (no 3D of course without a profile):

1. Go offline in Uplay. This is highly important. Online the game will exit after establishing the connection to the Uplay server, even if the inital hook is successful. Probably Uplay checks for anything unusual in memory and exits if something is found.
2. Disable the ingame overlay in Uplay (might not be necessary but can’t hurt).
3. Hooking probably will take several tries.
4. Once you make it into the game start an offline campaign.

There may be issues with saving checkpoints in offline mode. I’m not 100% sure of that yet. Would be nice to get some feedback in this regard.

[Ralf]

FRAPS should work fine in most cases. I will make vorpX’s built in debug FPS counter available for everyone in one of the next versions.

[Ralf]

Theoretically that could be used for decoupled look in some games, but it would cause too severe artifacts, missing geometry depending on view direction etc, so unfortunately that’s unfeasible.

[Ralf]

You should be able to use 0.4.3 with the current vorpX version, I’m not aware of any ill side effects. If you want to stay on the safe side and don’t absolutely need 0.4.3 for something else, I would recommend to stick with the version vorpX installs though.

The vorpX installer does a version check to avoid installing an older runtime, but unfortunately Oculus changed the registry key they store the version number in with 0.4.3. So this check fails in some cases (like yours). Will be fixed with the next update.

[Ralf]

Please set everything up as shown below. Do not leave out anything. When you follow all five steps, every game will open on the DK2 automatically, even without the config app.

1. Reinstall vorpX to reset everything to default
2. Set the Rift to Extend Desktop mode with the Oculus Config Tool
3. Make the the DK2 the PRIMARY display in Windows
4. Set the orientation of the DK2 to “Portrait” or in Win8 possibly “Landscape flipped”
5. Run all games at 1920×1080 in fullscreen mode, not windowed.

Yoy should also make sure to set the FOV to 120. Depending on the game from best to worst here is what you can do in this regard:

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)

[Ralf]

There seems to be an issue when using Z-Buffer 3D (although it doesn’t look like your description), but the game runs fine in Geometry 3D here using the Steam version of the game.

We also didn’t receive any other reports about something like this as far as I’m aware of. At this point I can only assume that this is specific to your system or setup, so all I can give you are a few general hints unfortunately:

1. Check whether the game runs in 1920×1080, other resolutions might not work correctly
2. Reset the game profile in the vorpX config app
3. Do a factory reset or reinstall vorpX (this resets everything)

[Ralf]

There already is an option called “G3D Latency Enhancement” on the input page of the vorpX ingame menu which eliminates input lag almost entirely. It applies head rotation directly in vorpX, completely circumventing the games input pipeline.

You can experiment with that in every Geometry 3D game. Setting it to something around 0.3 should usually suffice, above 0.7 lag is even gone in games that run below 60/75fps (read Skyrim).

One small caveat: enabling this in Skyrim creates a slight rendering artifact with far clouds/fog when turning your head. But that’s not really bad.

In case you haven’t done that already the other thing you can/should do is adjusting the head tracking sensitivity in vorpX until turning your head feels fully natural.

Can’t say anything in regard to the mod unfortunately.

[Ralf]

The only correct resolution for using vorpX with the DK2 is 1920×1080. Other resolutions probably lead to games being displayed wrong one way or the other,

Please also make sure to set the Rift to “Portrait” mode in the Windows display config (Win7), or maybe “Landscape flipped” (Win8).

With this setup vorpX will work just fine whwn using the DK2 as primary display. This is actually the most compatible option.

In regard to the config app crash temporarily disabling or uninstalling your virus scanner may be worth a try.

If that doesn’t help, you can use vorpX with the above setup. Most things that can be done in the config app can also be adjusted ingame after pressing [DEL].

[Ralf]

Currently not, but you won’t have to wait long for that anymore. The next update which will include this option will definitely happen this month.

Won’t work for all games in regard to playing with the mouse, but Skyrim (and probably all other Bethesda RPGs) is among them.

When using a gamepad with vorpX’s internal gamepad handling it will work with everything (including games that normally don’t work with a gamepad).

[Ralf]

Thanks for letting us know. They probably whitelisted the current vorpX version know. If it breaks again after a future vorpX update, you may have to disable Kaspersky again temporarily (or add an exception).

[Author]

Posts