Avatar Performance Versions
DarkSwordsman
This feature request is asking for the ability to upload a secondary "optimized" version of an avatar to the same blueprint ID.
Description:
Users can already upload their own fallback avatars and even generate impostors, but what if I had a "Very Poor" avatar with a "Medium or better" version?
This would mean that I could upload an "unoptimized" version of my avatar with all the bells and whistles, but then I could also upload a Medium or Good version of the avatar that people can opt to see instead of my slower avatar.
Technical Details:
- In the VRCSDK, the user would have an option to upload a "medium or better" version of their avatar on the same blueprint ID.
- Considers the performance afteroptimization scripts run.
- Inherits the existing avatar show system (show, hide, shield), where shield would likely show the Medium or better version if they are hiding Poor/Very Poor.
Benefits:
- Overall instance performance can remain good without needing to hide most avatars.
- Creates a stronger market for "optimized avatars" or avatar optimization tooling.
- Improves immersion since you can see more avatars as intended.
- Has the same drawback as impostors (mismatched state), except it's likely more accurate.
- Users wouldn't need to change avatars as often, since they can already be in their "event" avatar.
- It's like the fallback system, but per avatar.
Drawbacks:
- More storage required on VRC's end.
- Still a chance of avatar state mismatch.
- Would probably be best combined with a "temporary show" feature for avatars
- Fallbacks and Imposters already exist which may disincentivize the feature from being made
Log In
lackofbindings
I like this idea, especially since they’re deprecating fallbacks. This is what fallbacks always should have been imo.