Forum Replies Created
-
Posts
-
Still works here, also no other reports like this recently.
Unreal Engine 3 memory scanning is a bit sensitive to how the memory is allocated though, which can vary based on the machine, the number of programs running and even between multiple starts of a game, so there is an inherent chance of failure.
Try to launch the game directly after booting up Windows and minimize the amount of programs running in the background to exclude as many potential sources of interference as possible.
The only reason I can imagine why that might happen is a renamed tesv.exe, which would prevent vorpX from loading the correct profile. Using Mod Organizer in itself should not have any adverse effects.
Make sure to run Bioshock in DirectX 9 mode by adding -dx9 to the launch options in Steam. With DX9 you get full Geometry 3D. You should see a notification stating that when you start the game. Tomb Raider 2013 is Z3D only currently.
This functionality is part of the DirectVR settings optimizer for Crysis 3 and only applies to the actual Crysis 3 profile.
When you make a copy of that profile to try an unsupported game, the routines doing the image zoom/fov calculations aren’t invoked.
It’s capped on purpose in Crysis 3, the game does not allow to set the camera field of view high enough for the screen to be fully used vertically while maintaining a correct FOV. The alternative would be a fully used screen with a too low FOV, resulting in image distortion. You would definitely not want that.
I can’t really suggest anything else than above, sorry again. The Revive method was worth a shot, but obviously not guaranteed to work.
With an actual Oculus headset it’s working just fine in Oculus mode. I will remove the game from the supported games list nonetheless to avoid future confusion, the game devs broke vorpX support with their updates one time too often.
Your other option is the desktop viewer method described above. For your convenience:
1. Setup the game to use windowed or windowed fullscreen mode.
2. Exit the game.
3. Launch the vorpX desktop viewer
4. Right click the vorpX tray icon and disable the watcher.
5. Launch the game.Just as a reference: vorpX is the only stereo 3D app with OpenGL support at all, not even nVidia’s stereo driver has that.
However, OpenGL support in vorpX was never meant for anything else than older fixed function OpenGL games. There are just not enough games out there using OpenGL to justify the amount of work required for a more complete implementation like Direct 3D. It was a big surprise in the first place that the first No Man’s Sky version had working G3D.
You can also still play the game with vorpX, nothing really speaks against that. Just the stereo 3D part isn’t working anymore with recent NMS versions, vorpX still provides head tracking and auto-adjusts the FOV for your headset.
Looks like the game does some weird things that cause SteamVR to fail during its very first init call. Like the error message suggests it’s not a vorpX error, SteamVR cannot be initialized from within the game anymore.
Still works fine with Oculus though, so you could try Revive (https://github.com/LibreVR/Revive) with vorpX in Oculus mode. Revive translates Oculus calls to SteamVR. Didn’t try that, but it’s worth a shot. Your other option is the workaround explained above.
Some newer Ubisoft games incl. WatchDogs 2 use Easy Anti Cheat, which prevents vorpX (and other tools) from hooking. Theoretically the EAC makers could whitelist vorpX, apparently they do that for a handful of widely used overlays, but so far any attempt to contact them was met with silence.
Might make sense for you as users to take action. The more people reach out to them (and/or Ubisoft), the more likely they are to at least react somehow eventually. You can contact them via their support page: https://www.easy.ac/support/.
The camera height setting might require positional tracking to be enabled, not 100% sure ATM. I will check that and either enable it without positional tracking or make sure that the option is only shown when it actually does anything.
Thanks for the hint.
Sorry, not everything can be investigated here in detail immediately. Thanks for your understanding.
As a workaround for now you can play the game via the desktop viewer instead of letting vorpX hook into it.
1. Setup the game to use windowed or windowed fullscreen mode.
2. Exit the game.
3. Launch the vorpX desktop viewer
4. Right click the vorpX tray icon and disable the watcher.
5. Launch the game.Provided your issue can be replicated here it will be looked into before the next update.
I would highly recommend not to use the camera height setting at all in profiles you share. Leave the decision to the player.
Game breaking issues are probably rare, but changing the camera height will often cause more subtle glitches in regard to shader effects and potentially head tracking that may get unnoticed first, hence the warning that is shown in the vorpX menu.
I’d rather avoid adding more options that can cause both good and evil at the same time. Similar to the camera height setting this would be good for one thing but may cause other issues depending on the game, thus making it easy for users to break a game completely by trying to solve an issue that already has a working solution.
You can handle aiming down sights glitches by temporarily disabling 3D via a hotkey, the default is ALT-X. Can also be automated for aiming down sights by using a game’s ADS key instead of the default.
Hint: this shortcut works as a short key press to toggle 3D on/off and also as press->hold->release.