I can understand why VRChat would want to have this implemented. When you take X X , it scales pretty quickly. If we assume this as 40 avatars and 10 per second for update rate (which I believe it is), that is 51,200 bits per second (50 Kbps). On top of Udon's limits (392 Kb per serialization on manual, and 1,600 bps continuous), it makes sense. I never see VRChat use more than 1 Mbps when under use, even in a dense instance, and I assume this is intended to make the game as accessible to anyone as possible.

However, assuming the network sync is a custom system made by VRChat, there is nothing stopping them from doing custom data types for, say: 2 bit, 3 bit, 4 bit, and 6 bit. This would allow 4, 8, 16, and 64 different values, respectively, instead of needing to waste an 8 bit INT for something that doesn't even need 16 or even 8 variations.

:shakingfishface:

Now on Open Beta. Go test it!

I think the problem isnt the amount of data itself but the amount of data while being approachable to work with. Yeah you can get away with only using the 128 bits but it can be challanging to work with if youre new. Maybe its possible to add a compression system of some sort that could make more than 128 bits available in the editor but optimize it for upload. If possible that would be the best option imo

People assuming you can have thousands of combinations from only 128 bits seem to be forgetting that you're only able to save one parameter at a time.

So how might one fill up the 128 limit?

Here are six common floats:

Primary and secondary controls for hue, saturation, and brightness

8x6 -> 48/128

How about some audiolink bools and influence controls, if you have toggles for the bands along with a float for a radial control, then that's around 12 more on the stack. -> 60/128

What if the character has dozens of swappable accessories in different positions? Pretty simple ints, but say you've got them on the head, eyes, nose, mouth, back, ears, tail, feet, chest, etc...

That's about nine ints which maths out to 72 bits

So now we're at 132/128

Dang... Over the limit we haven't even added resets, local utility params, a size float, gesture, animation or skin ints.

Perhaps my ambitions are too high -- or maybe y'all know something I don't?

ive quite literally never hit the cap, even on my most complex avatars. nor have i talked with any creators who have hit it, its honestly pretty forgiving.

Re-use your puppet floats. You can't puppet more than two things at a time. No need to have separate variables for each one.

128 is plenty.

Uhh you will hit the avatar size limit WAY before reaching 128bits

How are you running out?

128 bits gives you 340,282,366,920,938,463,463,374,607,431,768,211,456 possible avatar customization combos on a single avatar.

Are you really using that many? I doubt it.

I think you may be misunderstanding something.

You only need to add a parameter to the parameter file if the data needs to be network synced. Local-only helper parameters do not need to be listed if they will do the same stuff remotely anyway.