[798] Don't block an avatar if it exceeds the dynamic bone limiter
complete
H
Hugo Zink
There is some partial overlap with this suggestion here, although I feel this particular thing deserves its own post: https://vrchat.canny.io/open-beta/p/798-prefer-graceful-downgrading-to-avatar-blocking
Right now, you can use the dynamic bone limiter to completely disable avatars' dynamic bones or collisions. Despite an avatar's dynamic bone being blocked, it is still counted in the performance ranks. Not only that, but in the beta, this means that an avatar can now be completely blocked over a component that
is no longer doing anything.
If I'm blocking all dynamic bones through the dynamic bone limiter, then dynamic bone should be left out of the performance rank equation entirely. If a Very Poor avatar becomes Good rank without the dynamic bone, then it makes no sense to still block this avatar.
Log In
Tupper - VRChat Head of Community
complete
This was implemented a while back-- if an avatar exceeds the DB limit, we simply turn off DB on that avatar.
ZaBoss
Yeah I defiantly agree with this
FloydianSound
to my knowledge, the graceful downgrade is working as intended.
dynamic bones count will not trigger the avatar performance limiter to "grey-man" you out.
i would like to add, however, that having more granular control over this downgrade and the dynamic bones/limiter would be a very welcome feature for me and lot of other people. i have wished for this for a while but didn't feel like it would get attention on canny.
i can devise a few things if there is interest. things like material counts and polygons comes to mind. i'm sure you all have your own things you'd like a bit more control over.
it could be implemented in the config.json file, or be impremented in the menu (much preferred imo, but i can understand it would take more work)
xxx_red_xxx
How was this not considered from the start?
Tupper - VRChat Head of Community
interested
As stated in the other post, the "graceful downgrading" system was already part of the eventual iterative process on the Minimum Rank system.
DB Limiter will serve as a user-configurable "layer" on top of the minimum ranks. At least, that's how I see it working. Marking this as planned. Can't give an ETA yet, though.
owlboy
This is a good point.