Mirror clone scale constraint apply weirdly for armature
available in future release
SpaceJackalTim
Since the latest update, personal avatar scalers like the Jackal scaling system and Mag's scale adjuster have been broken for the local mirror clone. This means that in mirrors or cameras, the scale seems to be getting applied twice.
It appears this has to do with constraints not running in the mirror clones.
Dexvoid highlighted a temporary workaround, although this is undesirable and also doesn't guarantee this will keep working in the future as the behavior will get changed again.
To make them work again for now there is a workaround to add source to the constraint on the armature that looks at the head bone with a weight of 0. This makes the local version be incorrectly scaled twice up as well, which then can be compensated by having all scale animations be the square root of the original value.
I've attached a couple images of the discord message, workaround fix applied to the constraint in unity, and a screenshot of in-game showing the issue. Here a scale of .4x has been selected. You can see the eye height is a little below the pool table, but in the mirror the local clone got a lot smaller than .4x
Log In
This post was marked as
available in future release
Dexvoid
The reported bug is due to this asset conflicting with VRChat's built-in avatar scaling system after attempts to further optimize VRChat constraints.
We're looking at restoring this use case for now in a way that does not require the workaround I suggested to another user on Discord, but please note that we can't guarantee this will remain possible forever.
SpaceJackalTim
It is good to hear that this is being looked into. And yes, these scalers have had a bit of trouble since the vrchat built in scaler got released. The vrchat scaler is great for what it offers but it is limited for a more niche group of people. Specifically those looking for more extreme sizes. These scalers do provide the freedom for a lot of people in this niche though, so I am glad to hear that at least for now things might get back to working around without even more workarounds.
Hopefully in the future if the possibility to use these custom scalers comes into question again, then at least the team can consider ways of accommodating this niche with a more proper solution.
Dexvoid
tracked