Forum Replies Created
-
Posts
-
IIRC the Scholar of the First Sin version has only Z3D with vorpX. For full Geometry 3D please use the original DX9 based Dark Souls II version.
While the view is indeed slightly asymmetrical on the y axis, the rendered image center is exactly in your view’s center as it should be. Both CV1 and Vive apparently use an asymmetrical view to optimize for human vision that is better at looking down than looking up, with the goal of spending more precious screen pixels for the more important lower image ‘half’.
Simply offsetting the image does not work as it moves the image center down and thus introduces distortion when the view rotates. This was actually done in the first CV1 release of vorpX, but thrown out again soon after due to said distortion.
Long story short: If you want to get rid of the small bottom border that is visible in some games, set the image zoom in the vorpX ingame menu to 1.0 and choose a slightly higher FOV. Doing it this way keeps the image center where it belongs and does not introduce distortion.
In general this is still valid, although 8:9 isn’t the best aspect ratio anymore for CV1/Vive (still possible but slightly too narrow). A good idea are 5:4 and 4:3 resolutions, which do not have to be added to the Windows resolution list manually, making this easier.
If your monitor does not support the resolution you want to try, you can try to run games windowed. This often allows them to run at resolutions that are larger than the monitor would allow in fullscreen mode. Best possible 4:3 resolution quality wise would be 1920×1440. Probably too taxing for most newer games though.
If you are using multiple users on your PC, please make sure to give your everyday user admin rights during the vorpX install. Otherwise vital files will end up in the admin user’s user directory, making vorpX non-functional for your normal user account.
After doing this make sure to start both vorpX and your games with your normal user to not run into similar problems when running the games.
I would generally advise against a distinct admin user. Since Windows Vista and the introduction of UAC that is not necessary anymore for security reasons. It more or less only makes sense in a corporate environment where admins often restrict rights to install programs and access system functionality for normal users.
That is no problem, no need for a new monitor. The monitor refresh rate does not matter at all with vorpX. Provided your PC is fast enough to run a game at 90fps, it will run at 90fps in your CV1.
Hello James, Provided you used the same mail address that you used for registering to the forum here (*.cox.net), your support request did not reach us unfortunately for some reason.
I will send you the DK1 instructions to this address. If the mail does not reach you, please either use this thread or the contact form in the “Support” menu above to prvovide us with an alternative e-mail address. Thanks.
That sounds rather odd. There is no background process or anything similar that remains active after closing vorpX. vorpX only hooks into other programs while it is running.
Only possible thing I can imagine is that vorpX maybe hooks into a SteamVR component while it is active and then remains hooked after closing the vorpX control app, which then might cause unwanted behavior.
You can check for that with the following procedure:
- Reboot your PC
- Start vorpX and SteamVR
- Start a few games
- Close vorpX
- If you now observe the unwanted bahavior, open the vorpX config app and create a trouble shoot data archive, which contains a logfile. Do not start vorpX again before doing this! Otherwise the logfile is flushed.
- Check the logfile in the archive for any programs that vorpX wasn’t supposed to hook into while it was running and add them to the exclude list in the config app.
Please let me know your findings! If there is indeed some unwanted hook, I will add the program(s) in question to the exclude list per default for the next update.
@ DeltaChris : The game is not supported, so as stated above it might or might not work. BTW: There are several corporate videos on your company’s YouTube channel using vorpX for marketing your product. This requires a commercial license. Please contact support |at| vorpx com in this regard. Thanks.
Was never tested here, so I can’t say anything definite, but it’s worth a try to create a vorpX desktop shortcut (vorpX tray icon right click menu) to the game’s main .exe. No guarantee for that to work, but these shortcuts can be more reliable than the auto detection in some cases.
While vorpX is active it tries to hook into every game you start. That includes VR games. To avoid this either exit vorpX before starting a native VR game or pause the injection watcher (tray icon right click menu).
If vorpX isn’t running, it doesn’t do anything. It’s just a normal program that only is active while it is running.
After starting vorpX you should see a tray icon in your taskbar which indicates that vorpX is running.
Please also make sure that SteamVR is running. Your issue sounds like something that can happen if SteamVR is not running with Vive.
If both of the above are true and vorpX does still not hook, there might be an injection conflict with some other program on your PC. The trouble shooting guide in the help has more detailed information in this regard.
Please create a trouble shoot data archive in the vorpX config app ans send that to support |at| vorpx com. Thanks.
There aren’t many reasons for something like that besides an antivirus or security software blocking vorpX. Without further information it’s impossible to give any specific advice.
You nned to enable mouse look in the game. The default shortcut key for that is ‘U’ IIRC. If not, you can find it in the game’s keymap options.
If changing the FOV in the ini with the Game Optimizer fails for some reason, try “fov 120 120” in the console (without the quotes). That should set the first person FOV.
If you didn’t do that already, please reboot your PC. Just in case the Oculus runtime is in use, blocked or something similar.
Apart from that please check your PC for possible injection conflicts. The trouble shooting guide in the help lists what to look out for.
If you can’t solve the issue by going through the trougle shooting guide, please create a trouble shoot data archive in the vorpX config app and send that to support |at| vorpx com. This archive contains a logfile and some information about you system which might help to identify a possible problem.