SDK Bug & Feature Requests

So I have been trying to get this avatar to upload on vrchats avatar sdk 3.9.0, keeps saying thumbnail image is reuired, and check console for logs. The problem is I have an image in the slot it saved. Was able to upload another avi a couple days ag, but this new project is'nt working. attached is image of my vrchat sdk, and the console.

I believe it is time to get a solution to the most plaguing issue (in my opinion) of AVPro: Audio Filters I do not think this is a "can't fix" situation. In this proposal I will go over the problem, considerations that have been discussed historically, and the solution I believe is feasible to implement with working sample code. ### Previous Cannys 1) https://feedback.vrchat.com/open-beta/p/986-avpro-player-ignores-lowpass-reverb-and-other-filters 2) https://feedback.vrchat.com/sdk-bug-reports/p/avpro-video-player-audio-filter-issue 3) https://feedback.vrchat.com/sdk-bug-reports/p/sound-effects-are-not-applied-to-audiosource-using-avpro-that-comes-with-sdk3 4) https://feedback.vrchat.com/feature-requests/p/usharpvideo-stream-audio-does-not-support-filters ### Crux of the issue As previously discussed in above canny #1, the current way of handling the AVPro speaker component (type named AudioOutput ) is that the component is implicitly created via AddComponent on the same game object. This has the critical drawback of being unable to respect any audio filters due to the DSP filter chain being _component order dependent_. The second half of this issue is that Unity has no runtime native way to change the ordering of components without fully reconstructing the references. This causes very obvious issues in regards to dependent scene references. (TCL's comment in canny #1 clarifies this as well) ### What has been considered Detecting and destroying/rebuilding known filter components after the implicit component is added. This is bad because all scene references to those components would be lost (eg: UI Events or public Udon variables). To avoid the lost components issue, a full scene search would be required in order to update the references which is costly and fragile. Placeholder components (shims) for each filter type that gets implicitly created after the implicit AudioOutput This is bad because it does not allow users to reference the actual filter components in the inspector (namely an issue for UI Events) Allow adding the AudioOutput script manually in scene and have the speaker search for it before trying to implicitly add the component. This is bad because it requires that the user import the AVProTrial package to be able to use built-in unity audio filters. This needs to be compatible with situations where the user does not wish to import that package so the dependency is decoupled from the feature itself. ### Proposed Solution A shim script that inherits from the AudioOutput class combined with a compiler flag for detecting if AVPro is present, and if not, then have a stub type of the _same namespace and type name_ which is _ONLY_ present in the sdk. Then update the VRCAVProVideoSpeaker to check for the existence of the shim component before creating an implicit AudioOutput, using it instead if found on the game object. This ensures that when the main shim script is loaded in editor, it is already a valid AudioOutput component and the component order is correctly retained so the Audio Filters will work correctly. In the SDK, the script type will check for the existence of AVPro through a version define, and if NOT present, will enable the AudioOutput stub class of the same namespace. An example of what it might be like: https://gist.github.com/techanon/41efc336604e148dde55862bff1778d9 I've tested this specific example in editor and it works there. Can't test in-client obviously.

Currently, the VCC always creates Windows projects by default. When installing Unity, the VCC should install the modules required for Android and iOS. It would be nice if users could choose Android or iOS directly instead of switching to it after project creation.

VRC Object Sync by default is a continuously operating script that pings locations to all players even when objects are at rest or behind the player/occluded by the world. As a result, once the object pool reaches higher numbers, over 200, frame times are permanently hindered as the game waits for all these pings. I'd tested in my world the difference between VRChat's default Object Sync script and MMMaellon's Smart Object Sync on about 212 objects. Performance with default object sync raised frame times to 16.7-17ms. MMMAellon's Smart Object Sync brought framerates down to 2.4-3ms, an overall savings of around 4-5x performance improvement. And this is not on a slow PC - this is on a Ryzen 7 7800x3D with a Noctua NH-12s cooler, an RTX 4070, and 64 GB of RAM. You cannot simply add power to fix the problem. MMMaellon's script does a lot to improve performance, but the core function allows objects at rest to stop pinging unless exerted by an external force. They are also developing a newer version of the script that cuts bandwidth in half. As VRC adds more dynamic global objects through the inventory system, I fear this issue will only become more exasperated the longer global sync gets ignored. I highly recommend enabling higher performance syncing methods by default for newer worlds and enabling the older sync system only when absolutely necessary. As many maps feature QV pens, pool tables, grabbable pillows, coffee and drink prefabs, and other grabbable synced objects, this will have an immediate performance impact across the entire game, and it's something all creators need to be made aware. https://github.com/MMMaellon/SmartObjectSync

I was making an Avatar where the Cube was 1mx1mx1m had a View Position 500 Meters Above the Model and it was fine no matter where I put it but when I change the Z Axis to be even 5 Meters Behind It, the avatar automatically switches it to the center since it was behind the model, I can't do it in front either. I was trying to have it 1000 Meters behind the Model but it still switches to the center when I was Trying to have it Behind The Model On Purpose. The Cube does not have Any Rig at all so why won't it let me do it no matter what I do. I put the cube behind the object, elongated it to be 500m long wirh the Z Axis at 500m behind the GameObject and even moved the Game Object with the Z Position and It still puts it in The Exact Middle where I don't want it to be. Is there anything I can do to Move the Z Axis for the Cube to be Behind or In Front of the Actual Model? (2022 SDK)

It would be a big help if constraints that do rotation had angle limits just like physbones have. Currently when I need an angle limit I need to use a physbone with an inside-out collider that is then constrained, which is wasting an entire physics simulation just to limit the rotation angle. This is becoming increasingly important since physbones have gotten so jittery and unstable that its difficult to use them with colliders at all anymore.

As the title states, when updating VRCSDK Base and Avatar to version 3.8.2 or later, bones edited in Play Mode revert to their default positions after a few seconds. Even after upgrading to version 3.9.0, this behavior persisted. Is this intended behavior?

In the new SDK 3.7.6, it's now possible to build a world on Linux, but it is not possible to launch a local test with proton. Pls add proton support, similarly to: https://github.com/BefuddledLabs/LinuxVRChatSDKPatch

I have come across a very annoying bug that can be reproduced every single time in Unity using VRC SDK version 3.9.0 on Unity 2022.3.22f1, this bug carries over into VRChat if the avatar with the bug is uploaded. Steps: Use Avatar SDK 3.9.0 and Unity 2022.3.22f1 Create a simple on/off toggle In the menu step of the toggle creation process, make sure your menu type is a "Toggle" or "Button" and "Value" is unchecked. Use any testing tools that goes through the menu (Not anything that directly changes the parameter value), if the toggle already has the spinning wheel you will realize that you cannot un-toggle it. The value will remain stuck. Otherwise you can only toggle once then never again. If you Upload the avatar with this bug present, the bug will also occur in VRChat. Showcase: https://www.youtube.com/watch?v=9qoz5K-07zM Avatar uploaded with the bug from a new bare-bones avatar project (Resolver + base sdk + avatar sdk, not project seen in video) https://vrchat.com/home/avatar/avtr_4015214d-c4a1-45f5-b6c0-1a9c9832d383 This is not caused by end user error, this bug happened to me today on another project, thinking I had a broken project I remade it, I then realised the bug is persistent across projects so I tested it with a very simple boolean setup and the most bare-bones possible (Only using the required sdk and resolver package + Gesture manager for showcasing the bug). The end of the video shows the toggles working properly if the menu "Value" is true/checked I do not show this in the video, but also manually checking the box in Gesture Manager's debug menu makes the toggles/buttons appear to work as they should when they actually don't, this leads me to think this issue is with the menu itself. Both menu type Button and Toggle are affected as far as I have tested, I didn't test the other menu types.