OSC Input for `/input/Voice` breaks keyboard and controller bindings.
closed
Raphiiko
The last bug for the OSC input addresses breaking input thankfully got fixed, but it's still not working correctly.
The current issue is that when the mute state is toggled through the
/input/Voice
address, the bindings for toggling the mute state stop working completely in-game. This is the case both for the keyboard binding (V), as well as the SteamVR controller binding.The mute state can still be toggled through the expression- or action menu.
The bindings start working again when the player manually disables OSC and re-enables it via the expression menu (Until the next time voice muting is toggled over OSC)
Relevant issue: https://github.com/Raphiiko/OyasumiVR/issues/83
Log In
_
_tau_
closed
Raphiiko
Ah I see, thanks for taking a look! That would explain why this is happening, sending another 0 seems to fix the issue indeed.
I would just maybe recommend documenting this behaviour on your "OSC as Input Controller" page. It does currently describe that for buttons you have to reset to 0 first, but it has no mention that you'd have to reset afterwards as well, to make sure other inputs remain available.
Other than that, consider it resolved!
_
_tau_
Raphiiko: Thanks for confirming! The docs on https://docs.vrchat.com/docs/osc-as-input-controller have been updated with a note now. We are also considering migrating this page to our creator docs in the near future, and probably overhaul it a bit in the process as well :)
_
_tau_
Hi! I've investigated this, and the behaviour appears to be working as expected for me.
Note that after toggling or muting the voice input, you must send a
0
to /input/Voice
to reset the OSC hold state on the setting. So the full procedure of toggling the microphone would be to send /input/Voice 1
followed by /input/Voice 0
.Is this a sufficient solution to this issue or is there something else broken here?
StormRel
tracked