Forum Replies Created
-
Posts
-
vorpX does not really support SBS output since it is solely focused on VR. When using the generic headset mode, you can however remove the lens distortion in the vorpX ingame menu.
Setting ‘Play Style’ on the main page to ‘Full VR’ and the three lens distortion related settings on the display page to 0.0/0.0/1.0 will get you as close possible.
You don’t need to upload a profile to save settings. All profiles on the ‘Local Profiles’ page in the config app are already on your PC and you can save customized settings for them simply by pressing the ‘OK & Save’ button in the vorpX ingame menu.
Profiles can be uploaded in the config app, but you only need to do that if you want to share your settings with others.
Unreal Engine 3 DirectVR at times can be a bit finnicky unfortunately since there are several memory addresses that have to be catched by the scanner. If one is missed, the scan might look successful, while in fact it is not.
Things to try (in this order):
1. Run the scan multiple times.
2. Try a different location/savegame.
3. Restart the game.
4. Restart your PC and the game.3. and 4. can be useful to ensure a default memory layout.
If nothing helps, you can disable DirectVR head tracking in the vorpX menu and use the default mouse based tracking instead. FOV should still work since it is handled via .ini edits.
Yes, I have tried in Kingdom Come Deliverance, just for you, on a Saturday evening. I am really sorry, but I cannot replicate your issue.
Just checked it for you. Works as it should.
1. Click on the button (letter) you want to change
2. The button text changes to ‘…’
3. Press the key on your keyboard that you want to assignYou can freely remap the controller buttons in the vorpX menu on the VR Controller page.
To do that simply click on the “Change Button Mappings” button and adjust the mappings to your liking.
It’s best to always try the VR controllers in keyboard/mouse mode first since this is the most compatible mode. Consider the gamepad mode an optional mode that might or might not work for a particular game.
Mouse/keyboard is the primary mode for VR controllers, hence that is the default.
This message is only displayed if either vital files are missing (hence the recommendation to reinstall) or your Windows installation is corrupt.
If you use anything else than Windows Defender, you should try to uninstall your AV program. Some particularly invasive AV programs can’t really be disabled until you uninstall them and may delete vital vorpX files although you think you disabled your AV program. On Windows 10 Defender kicks in when you uninstall third party AV programs.
If you are 100% sure AV software is not your problem, pretty much the only option left is a corrupt Windows installation, especially considering that it worked for over a year (purchase date 01/2018 as far as I can tell) and now suddenly doesn’t.
Maybe you have to enable the gamepad first in the game’s input options.
If you can’t use VR controllers as gamepad in a game for some reason, you can use them as mouse/keyboard. That should be the default usually since it is the most compatible method. Buttons can be freely mapped in the vorpX menu.
There are already too many options in the menu, so to reduce menu clutter a few less important things are hotkey only. You can map ALT+F to your controller if you consider it important enough to be available anytime while you play standing.
Because in a handful of games drawing the vorpX menu has a severe impact on performance, so to avoid confusion the FPS counter is not shown in the menu.
Use the built in FPS counter (ALT+F). vorpX has two render-pipelines running in parallel: the game itself and a second one which renders the final image to the headset, both can have different frame rates. The built in FPS counter displays both.
In cinema/immersive mode you can get away with rather low game FPS. Even 25-30fps may work fine in that case if the game isn’t a super fast shooter.
Parallel projection definitely has to be on with vorpX since ‘normal’ games don’t consider the canted displays of the headset.
In regard to Portal 2 please double check whether you selected a 4:3 resolution like suggested by vorpX, otherwise you will experience heavy FOV flickering.
Not sure how vorpX could affect your SteamVR Home, only option I can think of is that it might hook some Pimax helper app. You can check what programs vorpX hooks into by creating a trouble shooting data archive in the config app. Inside this archive is a logfile. If you find anything that vorpX is not supposed to hook, you can add it to the exclude list (also in the config app).
Would also be nice if you could send your troubleshoot data archive to support |at| vorpx com. I don’t have access to a Pimax headset yet, so all I can really do currently is checking logfiles.