Forum Replies Created
-
Posts
-
@ angelayla : If you happen to use any mods for the game, please remove them. According to an earlier post that helped someone else with an issue similar to yours.
In immersive/screen and cinema mode there is a setting called „Focal Offset“ which, if I understand you correctly, is what you want. You might have to enable expert settings in the config app to see it though. In FullVR Mode vorpX, like all VR-apps, uses a fixed convergence value far away.
There is one more thing to consider in VR besides the focal point though, which is the field of view (FOV). In FullVR mode the FOV of the game has to exactly match the FOV of your headset for things to look right. This is something you probably never cared about with a traditional 3D-driver, for VR however it‘s easily the single most important thing above everything else.
vorpX can do that automatically for almost 200 games, for other games however you will either have to do it manually or use a workaround if that is not possible. Check the „Essential Hints Guide“ and the „1-2-3 Game Setup“ in the help for more detailed information on the matter.
It‘s not supposed to be that way. If you have the game installed on a harddrive, try a SSD if possible to minimize hitches caused by streaming in new geometry/textures. Also try without any mods if you have mods installed and last but not least try to delete your fallout3.ini, the game will create a new one on start.
If you didn’t do so already, please try a factory reset in the config app (trouble shooting page). Sounds as if the profile might be messed up somehow.
Disable ‚Use headset audio device‘ in the config app. I had similar issues with Rift-S a few times in the past, looks like unfortunately it doesn‘t like how vorpX switches the audio output when a game starts. This is unrelated to the latest update. I was hoping Oculus would fix this over time, but apparently that won‘t happen anytime soon. I’ll probably disable the auto switching per default for Rift-S with the next update.
Instead you can switch the audio output manually from the Windows taskbar before starting a game with vorpX.
Sometimes the scanner may find values that look like the right ones, but actually aren‘t. In most cases you can resolve that by running it again. if that doesn‘t help, play with the default mouse based head tracking, which also works quite well.
Almost certainly a virus scanner problem. please exclude the vorpX program folder (usually C:\Program Files (x86)\Animation Labs\vorpX) From your AV scanner.
If vorpX can‘t hook into games anymore after an update, please first and foremost try to disable your virus scanner and see whether that helps. If so, exclude the vorpX program folder from your scanner. Some AV scanners unfortunately create a false positive detection with almost every new vorpX version.
If you use vorpX’s gamepad mapper (‘X-Box Gamepad Override’ set to ‘Full’), you should be able to map the G3D/Z3D hotkey to your gamepad. Don’t recall what that is ATM, but you can find the full list in the config app.
Similarly you could map the hotkey for the VR-Hotkey menu to your gamepad. That’s probably the most underused feature ever BTW. It allows you to map 16 key-combinations to a 4×4 button window that appears in front of you when you press SHIFT + middle mouse button. Simply press and hold SHIFT+MMB, look at the action you want to perform and release MMB. Pretty useful.
19/09/06
vorpX 19.2.4 has been released.This is a maintenance release with the below changes and fixes.
New/Changed:
- New D3D9 font renderer: fixes severe FPS degradation (up to 70%) during the first minutes (while the start hint is shown) with Half-Life 2, Portal, The Darkness II and possibly other D3D9 games.
- Improved D3D11 G3D heuristics (~30% G3D performance gain in Blair Witch).
- Improved binary settings file support for the DirectVR settings optimizer.
Bugfixes:
- G3D camera height modifier should now always work again without positional tracking. Please note that the setting may behave different with/without positional tracking enabled in some cases.
- Settings for official profiles could not be uploaded anymore in the config app.
- Final headset render target size re-evaluated when the game resolution changes. Fixes low render target size in games that open a small window on start before switching to full res.
New Game Profiles:
- Blair Witch: G3D/Z3D, FullVR, scalable 3D HUD, DirectVR: FOV, resolution, tracking.
Check the “1-2-3 Game Setup” in the help. Aside from getting a first person mod and a FOV mod that’s what you will have to do unless there happen to be first person user settings in the cloud.
You don’t have to care about that. I did :). Two or more profiles in the local list with the same .exe assigned cannot occur.
If you import settings for an official profile, such a collision is impossible by design since user settings for official profiles do not contain the .exe assignment in the first place.
If you import a full user profile that has the same .exe assigned than an existing user profile in your local list, the .exe is removed from the prior profile on import. IIRC vorpX should show a message in that case, but I’m not 100% sure ATM, mght also happen silently.
If you are using a Pimax headset, please make sure that “parallel projections” is turned on in PiTool.
Some not quite as important, but also useful additional Pimax related hints can be found in the Pimax section of the vorpX help.
I’ll look into it. This extra check was added with the last update, but is only supposed to affect full profile uploads, not settings uploads. I’ll check whether something doesn’t work as intended in that regard. Thanks for the heads-up.