Describe the bug
Using OSC, you can push the value of a float past 1.0 or below -1.0, the defined limit normally allowed by VRChat float parameters. After swapping off and back to the avatar, the value is clamped back down within range.
While being able to bypass the standard range has its potential benefits, this behavior appears to be unintentional and conflicts with other systems expecting that defined limits.
To Reproduce
Steps to reproduce the behavior:
Send an OSC message with a float value above 1.0 or below -1.0
Open the parameter debug menu
See parameter outside of defined range
Expected behavior
Float parameters are clamped within the defined range of -1.0-1.0
Screenshots
Info (please complete the following information):
Type: Desktop
VRChat version 22.1.1-a221aaba5b
Additional context
When you set a float to MaxValue, other fun math errors occur.
while this may be a bug, till #2 is implemented this should not be fixed, some users are using un clamped range of the float to have local only functionality.
Describe the bug Using OSC, you can push the value of a float past 1.0 or below -1.0, the defined limit normally allowed by VRChat float parameters. After swapping off and back to the avatar, the value is clamped back down within range.
While being able to bypass the standard range has its potential benefits, this behavior appears to be unintentional and conflicts with other systems expecting that defined limits.
To Reproduce Steps to reproduce the behavior:
Expected behavior Float parameters are clamped within the defined range of -1.0-1.0
Screenshots
![image](https://user-images.githubusercontent.com/3047793/154442103-e10ec006-5a98-4175-a822-3b99b22e9041.png)
Info (please complete the following information):
Additional context
![image](https://user-images.githubusercontent.com/3047793/154444888-c74cb249-870a-4d7e-afac-dc52ea7ff901.png)
When you set a float to MaxValue, other fun math errors occur.