Forum Replies Created
-
Posts
-
Good idea, should be relatively easy to make the menu scale dependent on the set ImageZoom to a certain degre.
The other option would be to reset the Zoom to default while the vorpX menu is open. One of these will be in the next update.
Glad you got it sorted out.
For the head tracking sensitivity there is no single best setting. The best value depends on the mouse sensitivity you have chosen in the game.
My personal suggestion would be to set the mouse sensitivity in the game fairly low, and then adjust the vorpX head tracking sensitivity until rotating your head feels right.
@ sidni : Maybe your Skyrim config is messed up somehow. Normally this key opens the text console in Skyrim (a semi transparent window that slides in from the bottom of the screen). Not sure how to help you if you can’t open it. There probably are a lot tutorials on the internet. Google for “Skyrim FOV” or “Skyrim console” (without the quotes).
I’d really like to help you directly, normally the steps mentioned above are all you need to do.
In regard to head tracking latency please check the new “G3D Latency Enhancement” on the input page of the ingame menu. It does wonders in low framerate situations (but causes a few visual glitches in Skyrim and probably other games too – everything has its price).
Please make a factory reset of your vorpX in the vorpX config app (just in case) and try again.
On the Optimize Game Settings page of the config app you can apply ini-tweaks for various games. Just select the game you want to play, and hit Apply Settings. Be sure to read any hint that may be given there carefully.
Setting the FOV through the Skyrim console works 100%. This is not a vorpX function, it’s something built into Skyrim. If you enter everything correctly, it does work.
If you are new to things like this, try without vorpX on a normal monitor first to see what happens.
1. Open the console with the [~]-key (the key left of the [1]-key. On international keyboards it may look different.
2. Type fov 120
3. Press [Enter]
4. Close the console with the [~]-keyIssue confirmed. For Fallout 3 I found that changing the line iAdatper=0 in FalloutPrefs.ini to iAdapter=1 fixes the problem, for Fallout NV this doesn’t seem to help.
The above presumes that the DK2 is set as secondary display.
Try the following ini-tweak:
In your FalloutPrefs.ini change the line iAdatper=0 to iAdapter=1 .
With the DK2 configured as secondary display this worked for me in Fallout 3 but not in Fallout NV.
Status is still the same: The issue can not be replicated here so far unfortunately, which means there is no way to find a possible cause inside vorpX.
With Skyrim “Direct To Rift” mode in the Oculus Rift display config may work, but from my experience it’s even more sensitive in regard to stuttering when a games runs below 75fps (which almost certainly is the case in Skyrim).
Apart from that you could try to enable/disable VSync. That’s all I can think of.
Here’s a short tutorial. Just be aware that this, while better than no head tracking at all, in most cases is not comparable to the normal head tracking, especially due to higher latency.
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, your headtracker is now a gamepad axis. The final, but very important 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 any other gamepad axis.
I would suspect that this may be refresh rate issue. VorpX itself isn’t slower than before, but the DK2 is more difficult to handle in many ways unfortunately. The DK2 runs at 75Hz while your monitor probably runs at 60Hz. This may lead to stuttering/syncing issues when you use vorpX configured with the DK2 as secondary display.
Two things you can try:
1. Set the DK2s refresh rate to 60Hz. Your monitor and the DK2 should use the same refresh rate in this case. For nVidia cards this can be done in the nVidia control panel. Not sure about AMD currently, but there probably is a similar option.
2. Set the DK2 as primary display in Windows and vorpX to “Use system settings” display wise (details are in the DK2 setup guide in the documentation). In this case also make sure to select a refresh rate of 75Hz in the game options if the game allows to select this.
In both case please make sure to only tip the [SPACE], respectively the [DEL] key briefly. Otherwise the action might not get registered a key press by vorpX.
Works here when selecting the secondary display adapter in the Underworld setup program.
Default 3D is a bit weak, you might want to raise “3D Strength” close to the max. Will fix the default for the next update. There’s also a GUI-issue, which might not be fixable. Still playable.
Also make sure to set the “3D-FOV Enhancement” to the max, and maybe zoom the image out a bit, FOV still isn’t perfect, even with 3D-FOV Enhancement set to max.
Sounds like the resolution of the game isn’t set to 1920×1080 (DK2 native res).
I had this when trying Oblivion for the first time with the DK2, so it’s not unlikely that this may be your problem.
BF4 can be tricky sometimes, in the easiest case you may just have to try a few times.
Apart from that here are a few things to try:
1. Disable the in-game overlay in Origin.
2. Switch from the 64bit to the 32bit version of BF4 or vice versa. Maybe one works better for you.
3. Go to offline mode in Origin. This circumvents Battlelog and might help with vorpX. However, you will lose online gaming, so do this as a last resort only.BTW: For whatever reason, the FOV can only be changed in multiplayer, in singleplayer one of the letterbox aspect ratio modes in vorpX is the better option. Less immersive, but better than a cramped FOV.
BTW2: You may have to configure your Rift as primary display in Windows and use “Use system settings” display wise in vorpX for BF4. Not 100% sure currently, but IIRC forcing to the Rift doesn’t really work with BF4.