Programming Shift Functions on Motion Controller

[pschimpf]

I’m trying to program the shift functions of either joystick to be the up, down, left, right keyboard keys. The in-game menu accepts them, but they do not work on either joystick. I’ve tested in places where the keyboard keys work, such as looting a body and talking to an NPC. I’m playing Fallout 3, where you can’t exit an NPC conversation without scrolling down and selecting a particular response. This is very tedious because the down arrow on the dialog selections is tiny, and difficult to land on with a joystick-controlled cursor. It’s bad enough that I have to revert to an XBox controller to play effectively. I am a newbie here, so apologies if this has been answered. I searched the forums but did not find anything. Headset and controllers are quest 2.

[Ralf]

Make sure you run the DirectVR scanner as indicated by vorpX. Once the scanner ran successfully, you can use your motion controllers in gamepad mode (should be the profile default).

The kb/mouse emulation before running the scanner is only necessary because the game doesn’t support simultaneous mouse/gamepad input and vorpX needs to emulate a mouse for head tracking.. After running the scanner vorpX accesses the game camera directly for head tracking, which provides better head tracking and also let’s you use motion controllers as gamepad since vorpX doesn’t have to simulate a mouse anymore for head tracking.

That aside shift mappings work fine here. Just in case: If you use some third party VR runtime to send the image to the headset, try Meta Link to check whether maybe the runtime is the culprit.

[pschimpf]

Thanks Ralf. Couple of things:

1) I switched to Gamepad input mode and things ran pretty well (outside of Fallout 3’s occasional confusion in not recognizing there is a gamepad attached). In that mode I noticed that the scanner always fails rotation unless I set Override XBox controller to Full or Partial, which is no big deal (but see item 3). However, when running outside of VorpX Fallout 3 adds options to the Pipboy when a gamepad is in use. The most important, to me, is (X) to drop an item. When gamepad input is disabled, those options are not displayed and an item is dropped using RMB. With VorpX I never see these options whether I am using Gamepad or Keyboard/Mouse input. As a result, I recently switched back to Keyboard/Mouse input and mapped (Shft-Rclick) to RMB so that I could drop items.

2) The downside in keyboard mode is navigating the pipboy screen and dialogs with NPCs. I’d rather not use head tracking and right joystick to navigate those, although it is tolerable if I turn the right joystick sensitivity way down. This is why I wanted to map something to up, down, left, right. Shft-Rstick was logical, but didn’t work (Rstick would be even more logical for me if we were allowed to map that). I thought maybe this was the not-allowed mapping of Rstick extending to broken mapping of Shft-Rstick, so I tried mapping Shft-A and Shft-B to up/down and that didn’t work either. So I’m unable to map anything to those keys. When running outside of VorpX I have to make sure the cursor is pointed away from anything for those to work, so when I’m in VorpX I make sure to gaze away or use RStick to get the pointer out of the way. Meta Link does not filter any controller functions. It’s hard to see how it could be a Fallout problem because it doesn’t know where key codes come from. My best guess would be that Vorpx is generating keycodes that are different than what the keyboard generates for those. Can you verify that you are able to map something to the cursor keys?

3) This is not particularly relevant, but I think I’m confused about the difference between setting gamepad override to full and setting input mode to keyboard/mouse. I thought the former would only apply to using an actual gamepad, which I’m not using. But then why does my scanner always fail unless turn that on, or set input mode to keyboard/mouse? Does it also apply when controllers are set to gamepad mode?

[Author]

Posts