[Feature Request] Define custom perf ranks based on the server side provided avatar stats (and automations based on them (hide avatars)) #859

New Issue

MrUnknownDE · 2026-04-05T16:30:19+02:00

MrUnknownDE commented

2026-04-05 16:30:19 +02:00

Originally created by @TayouVR on 5/9/2024

Explain in detail what your suggested feature would be used for.
It would allow you to define when an avatar is performing badly and mark it as such.
It would be also great if you could automatically hide any avatars that exceed certain user defined limits (e.g. vram) (this may not be possible immediately in game as the game probably doesn't update that information from external changes until the avatar is reloaded)

Describe how it would look if it requires a UI.
Grid Layout with rows for each measured stat, columns for ranks. (there could be e.g. 4 pre-defined at the start, or it could be dynamic)
each field then has a input field allowing the user to configure the maximum value that the avatar is allowed to have for that rank

Explain why people would want to use it.
it would give quick and easy information on how avatars perform.
If the automations are integrated each rank would have a "action" selection defining what should be done with a avatar in that rank, allowing you to automatically hide badly performing avatars.
The advantage of using this over VRChats built in systems would be, that you can adjust what should be hidden and what not based on your hardware and pain tolerance. (low FPS)

*Originally created by @TayouVR on 5/9/2024* **Explain in detail what your suggested feature would be used for.** It would allow you to define when an avatar is performing badly and mark it as such. It would be also great if you could automatically hide any avatars that exceed certain user defined limits (e.g. vram) (this may not be possible immediately in game as the game probably doesn't update that information from external changes until the avatar is reloaded) **Describe how it would look if it requires a UI.** Grid Layout with rows for each measured stat, columns for ranks. (there could be e.g. 4 pre-defined at the start, or it could be dynamic) each field then has a input field allowing the user to configure the maximum value that the avatar is allowed to have for that rank **Explain why people would want to use it.** it would give quick and easy information on how avatars perform. If the automations are integrated each rank would have a "action" selection defining what should be done with a avatar in that rank, allowing you to automatically hide badly performing avatars. The advantage of using this over VRChats built in systems would be, that you can adjust what should be hidden and what not based on your hardware and pain tolerance. (low FPS)

MrUnknownDE closed this issue

2026-04-05 16:30:19 +02:00

Sign in to join this conversation.

No Label Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/VRCX#859