SDK Bug & Feature Requests

Currently, upon reviewing the request headers, there does not seem to be any way to differentiate between string and image loading requests for the same URL. With the limitations of VRCUrl, it would be very nice to have a way to tell them apart. Some potential solutions include specifying a value for the Accept header, extending the User-Agent header, or adding a new VRChat-specific header. I believe the last option would be the least likely to break any existing worlds, but there are various pros and cons of each. An example use-case would be a system to download a mesh (binary data, string loading) and its texture (image loading) using a single URL. The server could use the headers to determine which content it should respond with. This would also be useful for decreasing the size of VRCUrl pools as used in YTS and other worlds. We are already using useragent-dependent responses between video player and string loading useragents, but we'd like to do the same with image loading too.

Make it so after entering your info into the SDK login window, you push the Enter button on your keyboard and it acts the same as if clicking the Sign In button with your mouse. It would be a Quality of Life addition for people who make lot of projects all the time, like avatar creators who work on avatars everyday. I am sure it would be beneficial for world creators too.

In VRCSDK3 Avatars, if BlendShapeNormals in FBX is Calculate, the validation is displayed. If I press AutoFix here, LegacyBlendShapeNormals will be enabled. But I think LegacyBlendShapeNormals is an old method as it is named Legacy. Since relying on AutoFix in VRCSDK is not a way to get out of the old method, we would like to change it to use the new method. Instead of enabling LegacyBlendShapeNormals, I would like to change BlendShapeNormals to None. Incidentally, depending on the new Blender FBX export settings, LegacyBlendShapeNormals may break mesh normals. So I am trying to find a way to avoid using LegacyBlendShapeNormals. I am using VRCSDK3Avatars 3.6.0. Thanks.

Clicking the Auto Fix button will throw an error, because the component type its trying to add (VRC_SpatialAudioSource) is abstract. The correct type name would be VRCSpatialAudioSource.