-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Driving /input/Voice
with pythonosc
Unexpectedly Changes Controls
#108
Comments
Tested and repeatable on my system with Python 3 using PythonOSC & pyOSC3, as well as Lua using OscCore using /input/Voice and /input/MoveForward, same symptoms appear. |
If done while the user is in VR, it forces the arms into desktop animations. Reproducible with axes ( |
Confirming that this still causes issues, at least on desktop - the Mute/Unmute keybind stops working, although the menu no longer switches to the vive controls. Have not tested on VR. |
Still causes a force of desktop animations in VR. |
McArdellje on the canny pointed out some more information on this along with a workaround. "This specifically only occurs when using any |
Can confirm I'm running into the same issue here. I cannot use |
This issue appears to be resolved on VRChat's most recent Open Beta. (Build 1340) |
Describe the bug
When driving the endpoint
/input/Voice
with thepythonosc
library, input properties change unexpectedly. The same does not happen when using Hexler TouchOSC.On Desktop, the Mute/Unmute keybind stops working, and the "Bindings" menu shows Vive controls instead of Keyboard/Mouse controls.
On VR, the controllers appear to stop tracking in-game. Menus appear in front of the HMD as though controllers are disconnected. Buttons and joysticks on the controllers still work.
To Reproduce
Steps to reproduce the behavior:
0
/1
) or a bool to the endpoint/input/Voice
using thepythonosc
library with "Toggle Voice" in any state.Expected behavior
Driving this endpoint should not cause input properties to change.
Screenshots
Desktop "Bindings" screen before/after driving
/input/Voice
:Video of issue occurring:
gtW14SYWPr.mp4
Info (please complete the following information):
Additional context
Issue was observed on two separate machines, both using
pythonOSC
with Python 3. TouchOSC was noted to not have the issue on the Desktop/1170 machine.The problem is reminescent of #107, with strangeness in input, but the two may be entirely unrelated.
H/T to @CatGirlEddie for helping narrow this down, and testing on beta 💯
Minimal example python code:
The text was updated successfully, but these errors were encountered: