[FEEDBACK] Allow user specified bitrates on float/int parameters
Groxxy
Currently float and int parameters are hard-set as 8 bit parameters... This is fine for people who don't need a lot of parameters... but it uses more bit space than what is needed most of the time (as you will rarely see anyone use even close to 255 seperate values for every interger) and the radial float puppet does not allow going into the negatives despite it being synced. I think that allowing the user to use lower bit-rate floats or ints with the limiting factor being less precision, also for floats not allowing to go below 0, Example situation: Someone makes a radial float puppet that doesn't require a lot of precision, instead of using 8 bits with half of the range being unused due to a negative being involved, use only a 6 bit float that ranges from 0-1, which is still precise enough for most cases, and some cases can use only 4 bits if they need more room. (4 bits = 16 int limit, a single 0-1 float at 4 bits is a 0.0625 increment, this is still enough for most radial puppets)
Log In
Kiiyokо
I have many many issues with how the current avatar bits work--specifically with OSC. It is extremely difficult to have lots of OSC avatar parameters and to be forced to use the 8 bit SIGNED floats/ints (which usually wastes a bit) when constrained to the 256 avatar parameter limit. Being able to choose the bit precision and to also choose whether or not it's signed would be a genuine godsend. Plus I always want to save up on avatar memory usage, especially for assets I decide to distribute.
Being able to choose between 1-32 bits of precision would be great, preferably, 2, 3, 4, 5, 6, 7, 8 -> 16 -> 24 -> 32
Super necro bump, sorry.
e
el ff1493
or just add more slots vrchat