Forum Replies Created
-
Posts
-
Unfortunately there are games that do not allow mouse and gamepad input at the same time. Whenever vorpX requires to emulate a mouse for head tracking in such a game, you cannot use a gamepad natively. To deal with such games vorpX has a built-in gamepad to mouse/keyboard mapper (freely configurable in the vorpX ingame menu).
So whenever the gamepad to mouse/kb emulation is enabled in a game profile that is probably done because otherwise there would be a conflict between native gamepad and mouse based head tracking.
If I had to guess, I’d say that about 20% of games fall into that category.
For AMD cards vorpX can’t check the global VSync state, so as precaution the message is always shown.
On a sidenote: vorpX typically circumvents Vsync and uses its own frame timing instead, so unless a game has some hardcoded FPS limit you can ignore VSync settings anyway in most cases (>90%). Whenever possible vorpX handles it on its own.
Never tried it since it’s not an officially supported game, so I can’t really do anything else than giving the ‘usual’ hooking issue hint:
Most of the time hooking issues are related to conflicts with some other program your PC. The pinned trouble shooting guide on top of this sub-forum has more details on the matter.
Might also be worth a shot to enable ‘Alternative Hooking’ in the config app. Keep in mind though that the alternative method is not better per se, some games require default hooking. So always switch back to default even if the alternative method helps in a particular case.
Shouldn’t really matter, but starting the Mixed Reality Portal before SteamVR sounds more logical to me.
What’s also important for WMR is to ensure that input isn’t redirected to VR controllers exclusively. Per default WMR does that unfortunately when the headset gets enabled and you have to press WIN+Y to get mouse/keyboard input back. This rather annoying behavior can be turned off in the WMR Portal settings.
You can invert the direction in the vorpX menu, but that would make things even more odd. Changing the actual behavior of a third person camera is something only the game devs can do usually.
Still fun to try third person FullVR though. Personally I would prefer immersive screen mode for third person games, which feels more like one would expect a third person game to work in VR camera wise, but there is no harm in trying FullVR mode if you keep the slightly odd camera behavior in mind. One certainly can get accustomed to it.
The game is not officially supported, but there are a bunch of user made custom profiles available that you can try. You can import user profiles in the config app.
You can be sure that it always does what it is supposed to do. Maybe I didn’t explain well enough what it does so that you imagine it to be more than it actually is.
This just addresses a small annoyance, you don’t have to care about in any way. The only reason I posted about it was that it took way too long to implement. You probably wouldn’t even have noticed that there was something to fix in the first place without this post.
if that‘s the case, then it probably should work normally. Not sure why it does not for you.
Either way, you can easily address your „problem“ by using the mouse/gamepad emulation instead, which except for analog movement should work just as well as the gamepad emulation (after re-mapping a handful of keys).
Like said above, unfortunately there are games that do not allow mouse and gamepad input at the same time. Whenever vorpX requires to emulate a mouse for head tracking in such a game, you obviously cannot use a gamepad natively. vorpX can’t magically remove such limitations if the game devs decided not to allow mouse/gamepad input at the same time.
What vorpX can do however is offering you a solution by emulating mouse and keyboard with your VR controllers to handle such cases, the alternatives would be either no head tracking or no Vr controller support at all in affected games.
If using the controllers as gamepad does not work as expected for a particular game, the best course of action is to use them as mouse/keyboard. That’s why both options exist. Typically that’s the case in games that do not allow mouse (emulated by vorpX for head tracking) and gamepad input at the same time.
You can freely change the button mapping to you liking in the vorpx menu.
I’m reasonably confident that it will be possible to update the profile to DX11, I just haven’t checked yet. No promises though, can’t guarantee anything without having tried.
The Rocket League profile currently is DX9 only. I haven’t check yet whether DX11 will be possible, so for now using he -dx9 launch option is the way to go.
If vorpX can’t hook into any game at all the issue almost certainly is related to some other program on your PC interfering. I know you said you already read through the trouble shooting post, but please double check whether there may be still something running in the background that could potentially interfere.
The best way to trouble shoot this is to disable/uninstall every program/tool that you have running in the background.