Forum Replies Created
-
Posts
-
I’ll check this. When the profile was originally done it worked, but maybe something has changed in the meantime.
I’m thinking about making it adjustable, no promises though. The strange thing is that so far there was very inconsistent feedback about this, ranging from too weak over just perfect to too strong, so statistically I would say it’s probably OK. ;)
That’s often similar with the default 3D-settings, but in this case I really would have thought everybody senses it more or less the same way.
Positional tracking is Skyrim only currrently. More games to follow.
Regarding FOV please refer the the “How to get the most out of vorpX guide” in the documentation. There are several strategies how to deal with this.
For Bioshock vorpX offers a pretty easy one by using the ‘Game settings optimizer’ in the config app. If the optimized settings are not applied for some reason in your case, you can also use the built in “3D FOV Enhancement” or edit the according .ini manually. You can usually find short tutorials for many games by googling for “FOV + gamename”.
Please send a screenshot of the processes tab of your task manager showing all running processes to support |at| vorpx com . Maybe we can spot something you overlooked. Skyrim is definitely not known to cause such issues regularly, this almost certainly is a local issue.
Along with it please also send your vorpx.log after trying to launch the game a few times. The logfile can be found in your temp folder. Usually C:\Users\[Username]\AppData\Local\temp
This will be looked into tomorrow. It’s very late here already, also Sunday.
Did you try other games BTW?
This indeed sounds like something preventing vorpX from hooking into the game. Please check whether there is a d3d9.dll present in your Skyrim folder. Might be there from a so called ENB mod for example. Remove it if you find one.
There are more things that can block vorpX. If you haven’t done so already please go through the trouble shooting guide in the documentation.
Works fine here using the Rift as secondary display and forcing output to the Rift through the vorpX config app (tested with DK2). ME is one of the usual test cases here.
Just in case: Please check whether there is a d3d9.dll in your ME folder. Might be the case if used other stereo drivers.
The game is for vr-pros only btw. due to pretty heavy head bobbing. Makes many people nauseous fast.
You can restore the old behaviour by using the logarithmic aspect ratio mode (formerly known as “smart”) on the display page of the ingame menu. This was the default before but isn’t anymore.
Please note that this introduces additional image distortion (just like before).
Setting the FOV higher is the better solution in regard to a more natural image. Take the time to read the “How to get the most out of vorpX” guide in the documentation. It’s worth it.
Please check the “How to get the most out of vorpX guide” in the documentation.
It contains several strategies how to deal with FOV. In the best case you can set the FOV ingame or via an .ini tweak. The second best option would be to use vorpX’s FOV function. The last option would be to switch to another aspect ratio mode.
@ zneeger: reversed images should not be possible. There are however three things that can make it hard to converge:
1. The game is not set to the correct resolution (should be 1920×1080 for DK2)
2. The IPD is wrong: Dial in your IPD manually. Experiment with the setting, especially too high values cause problems. This can either be done in the config app or ingame.
If you use an Oculus profile in the vorpX config app, please set this option to “Do not use an Oculus profile”. Reading values from Oculus profiles is buggy in this vorpX version.
3. The 3D-Strength is set too high. If you changed this setting in the vorpX config menu, please lower it to the default value (1.0).
It’s not officially supported, but you should be able the use ENB with the ENB injector (can be downloaded from the website of the origial ENB author). The versions where DLLs are copied into the Skyrim directory will probably not work.
That being said, there are absolutely no guarantess regarding any ENB mod.
Please send a mail to support |at| vorpx com with a description of the problem. I don’t have a real solution at this point in time, but if you use a DK1, I can provide you with an option to roll back to the previous version of vorpX.
Please make sure to set the FOV to a value around 120°. Doing so will provide a very natural looking image.
vorpX can help you with this in Bioshock using the Game Settings Optimizer in the config app.
If you haven’t done so until now, you definitely should check the documentation, especially the “How to get the most out of vorpX” guide. It has a lot of information about FOV and other things that are of interest when using vorpX.
Do you run Skyrim windowed or force it to be windowed through some external tool? If so, please do not do this. Make sure the game runs in true fullscreen mode.
Not sure what else may cause this, especially with the Rift as primary display and vorpX set to “Use system settings” display wise, which is the most compatible option.
Trying ‘Direct To Rift’ mode might also be worth a try. It’s not officially supported by vorpX at all currently, but may work in Skyrim.
vorpX only provides head tracking in games with mouselook per default. Positional tracking is Skyrim only currently.
You can setup vorpX to act as gamepad on the input page of the ingame menu for some head tracking in F1 2013 and similar games, but that’s not the best option. It’s better to use an external program like OpenTrack (which might not be DK2 ready yet though). Unfortunately we can’t implement similar TrackIR emulation due to legal reasons.
If you use Windows 8, please check the Windows 8 sticky in the general forum section.