Forum Replies Created
-
Posts
-
Not sure about the framerate issue, didn’t experience that when doing the profile. Shadows are disabled in G3D, no way around that, at least for now. Sorry.
Hey guy :),
You have two options to use vorpX:
A. The convenient one (may 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 the Rift DK2 to “Portrait” mode in Windows
(might be “Landscape flipped” in Windows 8)
4. 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 the Rift DK2 to “Portrait” mode in Windows
(might be “Landscape flipped” in Windows 8)
4. 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.
@ goshops: Just in case you didn’t find the EdgePeek function until now: by pressing the middle mouse button (usually the mousewheel) you can look around the whole screen. There should be no need to take off the lenses normally.
@ Sven: Did you try to select “Show on Rift DK2” in the monitor selection of the vorpX config app when your Rift is set to secondary? That should work with almost any game, definitely including F1 2014.
Interesting. Looks like a simple enumeration and using primary, secondary etc. as names is indeed the more reliable option… Will look into this for the next release.
Geometry 3D for Metro requires the DX9 renderer currently. The Redux versions are DX11 only. There doesn’t seem to be much that makes the Redux versions superior anyway.
The black smear is caused by the DK2s OLED display. vorpX has a software fix on the display page of the ingame menu. Didn’t try it in Metro, but it should do the trick (may be dependant on a game’s gamma setting though).
There were reports of some weird cases were the monitor names are swapped for some reason earlier, so selecting ‘Show on [Your other monitor]’ might be worth a try. Never had the chance to investigate that.
Should probably change that to ‘Show on primary/secondary’. Persuading Windows to reveal meaningful monitor names and attribute those to the primary/secondary monitor is a PITA, possible that it doesn’t always work as intended.
Regarding menus that aren’t visible, please check the EdgePeek function (middle mouse button). In case you didn’t do so already, please also check the Essential Game Hints and the Quick Reference. Both have valuable tips how to deal with this and other inherent issues.
For head tracking in most Codemasters games you basically have two options. Personally I also like playing these games simply with EdgePeek constantly enabled for some pseudo head tracking, but you might not like that.
1. Using OpenTrack for TrackIR emulation (preferred method), I’m not sure though whether F1 2014 still has TrackIR support.
2. Emulating a gamepad axis with the head tracking. This is not ideal for various reasons, but better that nothing:
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.
5. Map the emulated ‘gamepad’ to the look around functions in the game you want to play. Do not leave this step out, it’s vital!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. There is a shortcut for centering.
rFactor 2 is not supported and might or might not work. Many unsupported games will work with no 3D vut VR functionality available, but there are no guarantees.
Your convergence issues are almost certainly caused by a wrong resolution like moarveer mentions (1920×1080 is mandatory for the DK2) or by a non-ideal IPD setting. You can adjust the FOV on the display page of the vorpX ingame menu (deselect using an Oculus profile in the config app if the setting is unavailable).
Please send a mail to support to get a new web installer. You should keep a copy of it, it always installs the latest version.
Do you by any chance run vorpX in XP compatibility mode? That would make vorpX and the subsequently started updater believe it runs on XP.
Huh, that sounds odd. The installer does the exact same version check that it ever did. Just double checked the installer script, absolutely nothing has changed there.
Could you please do the following:
1. Open a command prompt (type cmd [Enter] in the searchbox of your start menu)
2. In the command prompt type winver [Enter]
3. Send a screenshot of the window that pops up now to support |at| vorpx com.The version number should show 6.1 for Windows 7.
If reinstalling the latest Oculus runtime and rebooting does not solve the issue, please send a mail to support |at| vorpx com to recieve a downgrade option for a DK1 version of vorpX that does not rely on the Oculus runtime.
vorpX 0.7.5 with a bunch of new supported games, new game optimizer entries and a huge amount of changes and bugfixes is available now.
If you already own vorpX, it should auto-update when you start vorpX Control next time. If it doesn’t for some reason, simply use the web installer that you received when you purchased vorpX. It will download the latest version available.
Happy Holidays to all of you!
For details and a complete changelog please click here.
I apologize that you have to wait a few days longer. Thanks again for your amazing patience.
Status update from two days ago, which clearly says that a few more games and optimizer profiles are added before release: