Forum Replies Created
-
Posts
-
Looks all good, just using an Oculus profile is not recommended currently due to a bug in vorpX 0.71, which results in wrong distortion and a too small image with an Oculus profile selected.
Select ‘Do not use an Oculus profile’ instead and dial in the IPD manually. You’ll get a much better image this way.
You have to follow the short instructions in the license dialog and send us your request code first. We need this code to create your key.
If you can’t send an e-mail for some reason, you can also use the contact form link in the menu above, it may take a little longer to get the key this way though.
I don’t say this often, but this definitely is not a vorpX issue. Under normal circumstances setting the resolution to 1920×1080 is no problem. 1920×1080 is the native resolution of the DK2 and thus the recommended resolution to use vorpX.
If nothing else works you could try using the DK2 as only monitor. At least for testing purposes to see whether you are able to use 1920×1080 this way.
You can use the ingame menu (press [DEL] while in the game) to change and save settings per game. When you change settings there and close the menu with OK & Save settings are saved for the game in question.
A handful of settings is globally saved for everything, but the vast majority is saved per game.
vorpX has its own chromatic aberration correction BTW. It should have been enabled per defaut on DK2, but isn’t in most games unfortunately.
You can enable it on the display page of the ingame menu. There also is a software fix for the OLED black smear, which is quite useful in high contrast games.
Mmmh, that doesn’t sound right. Normally setting the game (actually any game) to the native res of the Rift is exactly the way it should work with vorpX. Other resolutions often aren’t displayed correctly.
The only explanation I would have for the behaviour you describe is that maybe your main monitor might be a bit older and doesn’t allow 1920×1080, which would make the resolution unselectable in the Skyrim launcher. Nothing vorpX could do about that, but you might be able to set 1920×1080 manually for Skyrim with an .ini tweak. That would at least be worth a try.
The other way around that would probably be to use the DK2 as primary monitor and set vorpX to “Use system settings” display wise (see the vorpX setup guide for details).
@ Locksmith: This thread and most information in it is not valid anymore. It was created before the current vorpX version was released.
Head tracking works just fine with the latest release of vorpX on the DK2.
I will close this thread since it is of no use anymore.
Hi Russbo,
Mirrors Edge has an entry in the game optimizer database to enhance the FOV (field of view), which is what you are looking for. You can find the optimizer in the vorpX config app, the menu entry is called Optimize Game Settings.
For more general information on the matter you can take a look at the “How to get the most out of vorpX” guide in the vorpX documentation. This is an issue with many games, vorpX has several functions to deal with it.
Please check the DK2 setup guide in the vorpX documentation.
If your DK2 is the scondary display, you have to force games to the Rift through the vorpX config app. The guide also explains a more compatible alternative, in case that fails.
Please follow all steps in the guide. Everything is important.
Normally Skyrim should run without any problems, the only thing you have to do is following the DK2 setup guide in the documentation.
Apart from that please make sure to set all games to the native res of the DK2 (1920×1080) prior to playing them with vorpX.
Please also check whether you can find a d3d9.dll in your Skyrim folder. Some mod might have copied it there. If you find a d3d9.dll in your Skyrim folder, please remove it.
You might get lucky with using the DK2 as primary or (better) only display. Inconvenient, but maybe the only option, if at all. Apparently FSX does very unusual things display mode wise…
I just performed a check myself, this may be one of so far two cases that might not be fixable in a decent way for the DK2, due to the DK2 not supporting clone mode and/or certain display modes the game switches to intermittently.
I’ll see what I can do, but no promises. For now the compatibility chart is updated to DK1 only for FSX to be on the safe side.
For games that allow you to change the FOV (field of view), you should rather do that instead of using the zoom.
For some games you can do this with vorpX, either by using the Game Settings Optimizer in the vorpX config app or by using the Geometry 3D FOV Enhancement (if a game has Geometry 3D support). For many other games you can find short tutorials by googling for FOV + game name.
If a game does not allow to change the FOV at all, using the zoom is a good alternative.
The first DK2 ready vorpX version is already out since August, 23rd. You can buy it right now.
Here are few videos showing it in action: https://www.vorpx.com/vorpx-oculus-rift-dk2-video/
OpenTrack probably is not updated to the current Oculus SDK yet and might block the Rift exclusively. You might have to wait for a new version.