Forum Replies Created
-
Posts
-
@ cole00
Motion controller gestures are a new feature in the upcoming vorpX release, currently available as a beta:
@ romandesign
DirectVR head tracking:
DirectVR (memory scanner) tracking mainly means that head tracking data from the headset is directly written to a game’s camera values in memory. The main advantages are super low latency and perfect 1:1 tracking without the need to tweak any sensitivity values. There are *some* vorpX profiles that also separate head/body rotation, e.g. Cyberpunk in the vorpX beta (or standalone mod), but that requires even more game specific work. Might be possible for Starfield down the road once Bethesda releases the modding tools.
Technically the memory scanner scans through a game’s memory in a reasonably clever way to automatically find the game camera. Once the addresses are known vorpX adds head tracking data directly to the game’s internal camera rotation/position instead of simulating a mouse for head rotation.
Just wait and see. Provided things work out as they did in all other Bethesda RPGs all you will have to do is pressing a button, and – poof – you have perfect 1:1 6DOF tracking with a camara FOV that just as perfectly matches the FOV of your headset.
Gamepad override:
The gamepad override is a decently feature rich mouse/kb > gamepad remapping tool, built directly into vorpX. Whether the input comes from an actual gamepad or a joystick doesn’t matter. The important thing to understand is that by mapping gamepad/joystick input to mouse/keyboard controls it let’s you use gamepads/joysticks together with mouse based head tracking even if a game can’t handle simultaneous mouse/gamepad input.
You won’t have to care about any of that once the official profile is ready. It’ll either have DirectVR tracking, which resolves this issue perfectly, or at least I’ll preconfigure the gamepad mapper to work out of the box with the game.
Should work perfectly fine with a 2080ti. if you get a black eye, you probably have enabled DLSS or some other post fx option in the game settings that doesn’t play well with G3D. Try to reset the graphics settings to default and if that doesn’t help, specifically check for DLSS and similar options.
You need the beta. There is a brief introduction video in the beta post, including an explanation how to bind gestures to actions yourself. Incidentally using Titanfall 2 as a showcase.
Control bindings are stored in the user portion of profiles, so you should be able to configure the official profile the same way. Unfortunately there is no merge/transfer utility though. However, if you don’t mind I’d happily take a look at what you did so far and factor it into the official profile as much as that makes sense.
If I can get DirectVR (memory scanner) head tracking working, the mouse/gamepad issue won’t be an issue anymore. That’s how this gets addressed in other Bethesda games. So far that worked out in all of them, so I’m reasonably hopeful. Fingers crossed.
What you can do in user profiles in such cases is enabling the X-Box gamepad override and mapping mouse/keyboard to the gamepad. Resolving headtracking conflicts like this one is actually what the override is made for primarily. If you are lucky, a partial override of the right stick will suffice. Judging from older Bethesda games you’ll probably need a full override (and remap everything) though.
The action label idea is noted under ‘nice to have’. Not something I’ll be able to whip up on short notice though. Requires extending the labeling system quite a bit.
I see your purchase, but no key request e-mail seems to have reached us, otherwise you should have a gotten an automated reply with the key a few minutes later.
Make sure to follow the instructions displayed in the license dialog to get your key.
You have to send an e-mail with the machine specific request code that gets displayed in the dialog. Without this code the license server can’t compute your key.
No official profile available yet.
I was on vacation – windsurfing without wind ;) – for the last two weeks and thus haven’t looked into the game yet. Not that I didn’t try, due to the mildly infurating lack of wind I had a lot more time at hand than I wanted to. The laptop I had with me just didn’t cut it unfortunately though.
As most of the time with larger first person titles you can shortly expect a profile with lots of settings automation and all the extra bells and whistles I can muster, including (if possible) low latency DirectVR head tracking which directly accesses the game camera, and (definitely) motion controller gestures.
The motion controller stuff alone will almost certainly make this the closest-to-native-VR way of playing the game.
If you happen to have the beta installed, make sure to check the gestures. Gestures are the biggest change that have been added to the profile recently.
Straight forward shooters like this feel surprisingly close to native VR games with just a few motion controller gestures. There’s just no way to go back to mouse keyboard or gamepad afterwards, even when playing seated. :)
That doesn’t sound right. The tray icon is supposed to be displayed on Win 11 just as always. My main dev machine is a Win 11 machine since quite a while and I also have never heard of this issue before, so there is definitely something weird going on here.
Sounds as if the 32bit part of vorpX (which displays the tray icon) exits or gets shut down for whatever reason. If you happen to use another antivirus than Windows Defender, get rid of it.
BTW: you can pin tray icons you want to be visible all the time via drag and drop to the taskbar area on the right side of the up arrow (and back).
That’s weird. Easiest way to address this is probably resetting the database with a factory reset (trouble shooting page).
Caveat: a factory reset removes all user profiles and settings you may have dialed in. if you have profiles/settings you want to keep, you can easily backup/restore them as files via drag and drop from/to the local profiles list.
First please reset the game’s graphics setting. Double check that stuff like DLSS and similar post fx are disabled.
If that does not help:
Issues like this often are caused by other applications also hooking into a game, which sometimes may work fine and sometimes may cause a fatal conflict. Try to disable *everything* that potentially may hook into games. Especially any GPU/CPU tools, including all bloatware some PC or GPU vendors provide, but also messengers, recording apps etc. Don’t suspect any background app not to hook into games. If in doubt always assume some tool running in the background hooks into games and thus can potentially be problematic.
Use Link/Airlink with vorpX set to native Oculus or alternatively OpenXR. Adding an additional element into the pipeline always poses the risk of creating weird issues. Unless you have to use VD for some reason it’s better to avoid using it together with vorpX.
From the FAQ post above:
I bought vorpX before but don’t have the web installer anymore.
Please request a new download link here.
The brief video below explains how gestures work in general. Just the basics, but should be enough to get you going:
If you are currently using the regular vorpX, try the beta. I recently took another stab at this completely unexplicable Bioshock 2 crash issue, but couldn’t replicate it anymore here. I’m still unsure whether it really is gone, since I didn’t change anything spcifically to address it, so I might just have gotten lucky, but it’s worth a shot. Maybe it’s really gone this time.
As far as the remaster is concerned, you should easily be able to run it at 90fps. While the Bioshock remasters technically are fairly bad DX9>DX11 ports with an insane amount of unnecessary overhead caused by replicating DX9 behavior with DX11 instead of rewriting the game renderer in ‘true’ DX11 fashion, on your rig that shouldn’t be an issue.
Not much to recommend here except checking for tools that might interfere by also hooking into games.