Quest 2, All of a sudden, Xbox Controller Issues in VR

[SanguisDiabolus]

I've played using SteamVR multiple times without issue, but now all of a sudden within the last few weeks, elite is having all kinds of problems seeing my xbox elite controller or seeing my bindings. I've followed lots of other various posts I've found from years ago, and a couple times I got it to work but only for that session. List of issues/facts comes down to:

1. In non-VR mode, game recognizes controller in bluetooth mode, sees my bindings, everything works fine.
2. In non-VR mode, game does not recognize controller in wired mode (it has before in the past, I use it wired in VR because thats the only way you can bind keyboard keys to the elite's paddles) and will not even function to navigate menus.
3. In VR mode, wireless controller works in menus, stops working in-game, except for the start button to open up the menu, but d-pad will work in menus.

I've used a tool to check the GUID, tried creating custom renamed bindings files, but now I can never get the ones I created to show up ingame, just "Custom". As best I can tell, the xbox controller GUID is 045E0B22 when connected wirelessly, but is 045E0B00 when connected wired. So I thought creating a custom binding file for each would be my solution but I can't get either of them to show up in the list ingame no matter how I connect the controller. I feel like it has to be something to do with the headset/running it in VR mode, because the controller works fine wirelessly non-VR, but booting up in VR it stops working.

 

[Arioch]

I've played using SteamVR multiple times without issue, but now all of a sudden within the last few weeks, elite is having all kinds of problems seeing my xbox elite controller or seeing my bindings. I've followed lots of other various posts I've found from years ago, and a couple times I got it to work but only for that session. List of issues/facts comes down to:

1. In non-VR mode, game recognizes controller in bluetooth mode, sees my bindings, everything works fine.
2. In non-VR mode, game does not recognize controller in wired mode (it has before in the past, I use it wired in VR because thats the only way you can bind keyboard keys to the elite's paddles) and will not even function to navigate menus.
3. In VR mode, wireless controller works in menus, stops working in-game, except for the start button to open up the menu, but d-pad will work in menus.

I've used a tool to check the GUID, tried creating custom renamed bindings files, but now I can never get the ones I created to show up ingame, just "Custom". As best I can tell, the xbox controller GUID is 045E0B22 when connected wirelessly, but is 045E0B00 when connected wired. So I thought creating a custom binding file for each would be my solution but I can't get either of them to show up in the list ingame no matter how I connect the controller. I feel like it has to be something to do with the headset/running it in VR mode, because the controller works fine wirelessly non-VR, but booting up in VR it stops working.

I had several issues running my Xbox One controller via Bluetooth which all went away after buying a wireless dongle for it.

Looking at your problems - my first thought is checking the Steam settings, like Steam and SteamVR are competing over the controller inputs. “Steam>settings>controller>Enable Steam Input for Xbox controllers” - try setting this to OFF and then try the game in VR.

 

[SanguisDiabolus]

I had several issues running my Xbox One controller via Bluetooth which all went away after buying a wireless dongle for it.

Looking at your problems - my first thought is checking the Steam settings, like Steam and SteamVR are competing over the controller inputs. “Steam>settings>controller>Enable Steam Input for Xbox controllers” - try setting this to OFF and then try the game in VR.

Already off. And the main issue is getting the controller to work in wired mode while in VR, because that's the only way you can bind keyboard keys to the Elite's paddles. When in VR I have keys bound to the controller paddles both for resetting the HMD position and for toggling orbit lines (they can become strange and unpleasant to look at sometimes for some reason).
The really bizarre thing is when I confirm the GUID of the controller when wired, and then use that in a control scheme, it doesn't work.

 

[Arioch]

Ah, sorry I can’t help then.

…and for toggling orbit lines (they can become strange and unpleasant to look at sometimes for some reason).

This is the third highest voted issue at the moment.

 

[Born Free]

in the winter, with dry air, i often shock my mouse and it stops working until the PC is shut down. after replacing several, i realized it was only disabling for that session.
just an idea, may not be related.

 

[SanguisDiabolus]

Ah, sorry I can’t help then.

This is the third highest voted issue at the moment.

Oh wow thats crazy I had no idea.

So with further work and testing, I'm becoming convinced that the problem lies solely with how Elite is doing its bindings folder/files. I completely deleted the folder and started from scratch, booting up the game so it would generate a new bindings folder with its files. I booted up the game normally with my controller wired and connected. It worked fine in the menus, and so I did all my bindings for VR. Closed the game, checked the bindings folder, and I see that the device was just called "gamepad". I rename that custom bindings file. I reboot the game with the controller in wireless mode, and do my bindings again, close the game, rename that file to something different. The I reboot the game in SteamVR with the controller wired. It doesn't work in the menus. Going into bindings, its set to Control Pad Default. I click the drop down menu, and my custom named VR binding is there and I select it for all 4 modes. Still doesn't work. I disconnect the controller so it switches to bluetooth, all of a sudden it works in the menus. I reconnect the wire, it switches to wired mode and continues to work. Load up the game, and controller now seems to work in my ship.
HOWEVER
I close the game again and relaunch it in VR with the wired controller and try to recreate what I just did, and I can't. It boots up to Control Pad Default when wired, I unplug the controller, and on its own the game switches all control schemes to my VR bindings. Controller works in menus, but then I get into my ship and it no longer works. I exit the game and check the bindings files, and now instead of 'Gamepad', theres the GUID '045E0B22' in all the bindings for both bindings files even though I created one while wired and one while wireless.
So I got it to work for one session, but then Elite changed my bindings files even though I had renamed them, and everything I've read about that says Elite isn't supposed to touch those files once you rename them.