Allow driving local parameters with OSC (parameters not in the VRCExpressionParameters list)

[ocirne23]

Allowing driving local animator parameters would allow for more complex behavior not limited by 128 bits.

It wouldn't sync over the network but there are plenty of cool use cases for local parameter control.

[PokerfaceCactus]

While we're at it could we also allow local parameters to be driven from the radial menu's so we can have menu buttons designed specifically for OSC controls.

[Demirramon]

Please!!!!! This would make it so much easier, and no one other than you would be affected by it. Maybe we could have a list of not synced parameters with a bigger limit (or none) if the SDK needs the parameters to be in some sort of list to work.

[DrBlackRat]

I think having local Avatar Parameters in general would be cool as someone mentioned before (should work the exact same as networked parameters, so Action Menu controll, etc can also be used).
With it we could drive only local animations, save up some synced parameters. OSC output to control devices / our PC, because those defiantly don’t need to be synced over the network to others.

[PokerfaceCactus]

More examples for this would be ideas like using OSC to control things like voice mod voices, muting discord, media controls and I'm sure there's many other convenience buttons that people could come up with to require less tabbing in/out of vrchat/the vr overlay