You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 15, 2023. It is now read-only.
Turbones, when optimized simulation is enabled, uses the script-set on avatar update rate of dynamic bones. this behaviour differs from vrchat which overrides all dynamic bones to 60. If normally using an avatar with the script set to 60, and then vrchat overriding this it causes a conflict behaviour which results in jittering,
Setting dynamic bone update rate to 0 on all avatars prevents this jittering issue in vanilla (not sure if it also benefits performance), because it means it's just vrchat's override doing the work.
However, if this is set, turbones optimized simulation obeys the set update rate value, resulting in all bones that use gravity or force to be dragged along everywhere like they have zero elasticity.
This behaviour breaks some avatars.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Turbones, when optimized simulation is enabled, uses the script-set on avatar update rate of dynamic bones. this behaviour differs from vrchat which overrides all dynamic bones to 60. If normally using an avatar with the script set to 60, and then vrchat overriding this it causes a conflict behaviour which results in jittering,
Setting dynamic bone update rate to 0 on all avatars prevents this jittering issue in vanilla (not sure if it also benefits performance), because it means it's just vrchat's override doing the work.
However, if this is set, turbones optimized simulation obeys the set update rate value, resulting in all bones that use gravity or force to be dragged along everywhere like they have zero elasticity.
This behaviour breaks some avatars.
The text was updated successfully, but these errors were encountered: