Some input on VRChat are wrong

[MikemaFBS]

Both sticks controls are wrong. If I move the stick, the avatar does gestures. If I press the stick and move it, I walk. They are inverted, it supposed to be on the contrary.

[polygraphene]

I know the contrary is introduced in Quest version of VRChat.
Does Rift(with SteamVR) version have the same mapping?

It is possibly difficult to solve the problem by fixing ALVR.
Can you re-mapping those behaviors in SteamVR settings?

[MikemaFBS]

I'm preety sure it doesn't work like that on rift. Also the A button just doesn't work. I think it's because the game detects Quest controllers as Vive, because the pointer in game is on the handle instead of the quest/rift/rift S trigger. The gestures works with the sticks instead of the rest of the buttons (like in this video https://youtu.be/DZIaAHJRQzI). basically the input is the same as VRChat Quest version. I'm almost sure that the problem (and maybe every input problem in other games, are because the game detects that you're using a Vive controller instead of a Rift one.

[MikemaFBS]

You can try to play VRChat QUest version and see how the controls are, I can confirm that the input are the same as Rift. Maybe if you see how is in Quest, you can figure out how it works on Rift and maybe that can help you to fix input problems. But again, I think the problem is that VRChat detects that you're playing with Vive controllers (beacuse that is what the shows when you want grab some objects)

[DigitalStyx918]

I have attempted remapping to no avail in Steam. They work as expected in Quest VR. For whatever reason it will not allow the joysticks to work without being pressed. I tried mapping the joystick touch to joystick click and that won't work.

[MikemaFBS]

I know. I think it's because the game recognizes the controllers as Vive controllers instead of Touch for Rift, Rift S or Quest. And you can't jump either, A button just doesn't work. @DigitalStyx918 @polygraphene

[DigitalStyx918]

It looks like, barring a change of course from Oculus, for this to be successful we need a custom mapping tool. It seems all the buttons function in some capacity through various apps except for maybe the touch sensors, but SteamVR doesn't offer enough options to make use of them.

It seems like some sort of openVR tool could be made to allow the Quest Touch to function as touch at least in respect to buttons, triggers, and sticks with an app to correct the mapping. Not ideal, but at least it keeps it somewhat practical for most users. I don't know the odds of me self-teaching myself the necessary skills to pull this off in a timely manner, but I'm disappointed to see no hint of a discussion of a solution for this, only an acknowledgment of the limitation. @MikemaFBS @polygraphene

[MikemaFBS]

I don't even know about a solution as well. I'm just testing and if I find a bug or something that can be improved, I just report it to github. Let's see how Polygraphene fixes this problem, and if he doesn't, he is making a wonderful work anyways. He can be proud of what he archieved until now.

[DigitalStyx918]

A solution should be possible. Three apps that I know of now make Quest and SteamVR possible. All of them stop at the controllers not binding correctly. Now we just need someone who knows what they are doing with OpenVR to make a binding fix as the buttons and joysticks clearly work and are read there is no reason they can't be made to function as intended on a touch. I'm not sure about all the capacitive touch sensors but the joystick responds to touch. If you move it without touching the top of the stick it does not gesture. If you put your thumb on it it gestures. Click to gesture and touch to move would be a much better setup, and most games using touch expect to touch to move not click.

[DigitalStyx918]

The controllers track in SteamVR and all the buttons seem to register which means a solution is possible outside of Oculus. Whether any Dev can do it with Unity and openVR I don't know, but Steam could certainly create a solution with SteamVR on their end. They could call it a Quest touch, Alternative Touch, generic touch or something and simply have it as an option for Dev's to report their controllers as and Quest users may then desire to take their Steam library to Index when they are ready for the next level. Especially with Index available with even more buttons and sensors available, that should leave plenty available input options for fully mapping a touch to. It might even create a scheme that would be beneficial in getting developers to incorporate the Index controllers in their games.

[polygraphene]

I tried to change HMD model name (Prop_ModelNumber_String). But no luck.
I found the log file of VRChat in AppData\LocalLow\VRChat\vrchat
I will check detail of how VRChat detect touch controller.

2019.05.31 15:43:45 Log        -  AmplitudeWrapper initialized
2019.05.31 15:43:45 Log        -  LimitedConcurrencyLevelTaskScheduler created, threads: 1
2019.05.31 15:43:45 Log        -  LimitedConcurrencyLevelTaskScheduler created, threads: 1
2019.05.31 15:43:45 Log        -  VRC Analytics Initialized
2019.05.31 15:43:45 Log        -  OpenVR initialized!
2019.05.31 15:43:46 Log        -  [VRCFlowManagerVRC] waiting for UI Manager
2019.05.31 15:43:46 Log        -  InitVRSDK: OpenVR success! loadedDeviceName: 'OpenVR'
2019.05.31 15:43:46 Log        -  Connected to Oculus Tracker:OculusRift-001
2019.05.31 15:43:46 Log        -  Steam tracking system name: 'Oculus Tracker'
2019.05.31 15:43:47 Warning    -  The referenced script on this Behaviour (Game Object 'LoadingIcon') is missing!
2019.05.31 15:43:47 Warning    -  The referenced script on this Behaviour (Game Object 'Checkboxes') is missing!
2019.05.31 15:43:47 Warning    -  The referenced script on this Behaviour (Game Object 'BlueprintDetailsPopup') is missing!
2019.05.31 15:43:47 Warning    -  The referenced script on this Behaviour (Game Object 'Checkboxes') is missing!
2019.05.31 15:43:47 Warning    -  The referenced script on this Behaviour (Game Object 'Checkboxes') is missing!
2019.05.31 15:43:47 Log        -  [VRCFlowManagerVRC] showing disconnect reason
2019.05.31 15:43:47 Warning    -  OvrLipSync Awake: Queried SampleRate: 48000 BufferSize: 1024
2019.05.31 15:43:48 Log        -  STEAM Tracking System: Oculus Tracker
2019.05.31 15:43:48 Log        -  VRCInputProcessorVive: using vive controllers = True
2019.05.31 15:43:48 Log        -  STEAM Tracking System: Oculus Tracker
2019.05.31 15:43:48 Log        -  VRCInputProcessorViveAdvanced: using vive controllers = True
2019.05.31 15:43:48 Log        -  VRCInputProcessorTouch: using touch controller = False

[polygraphene]

VRChat seems to check Prop_TrackingSystemName_String.
And it seems to expect lower case of "oculus".
Now I get Oculus Quest like input bindings.

[DigitalStyx918]

Awesome Polygraphene. Hopefully you are knocking on the door of the fix, but I did have success getting some better controller binding to work. It should be shared, but I'm not seeing it show up as shared yet,

It is named: "Shared binding from DigitalStyxDIY for using Oculus Quest with SteamVR VRchat."

Also I was able to confirm that the capacitive senors fully report touch as well as buttons and triggers all work with the lone exception of the Quest. It is definitely fixable.

[polygraphene]

Try alpha5.
https://github.com/polygraphene/ALVR/releases/tag/v2.4.0-alpha5

[satyaloka93]

VRChat seems to check Prop_TrackingSystemName_String.
And it seems to expect lower case of "oculus".
Now I get Oculus Quest like input bindings.

Could this be the key to other games with incorrect mappings, specifically Fallout 4VR?

[polygraphene]

@satyaloka93
Maybe.
I implemented that fix on alpha5. Try it.