SDK Bug & Feature Requests

Constraints latch the "target transform" on Awake during play mode, even if the constraint is not yet active, this makes it impossible to add a constraint and configure it on the same frame programmatically without first disabling the game object that the constraint is added to (preventing Awake from firing) and re-enabling the object after configuring it.

When setting up a (parent) constraint that is only meant to freeze an object to the world and otherwise return it to it's original location (i.e. back to the hand), doing so with 0 sources (as there's really no need for any sources) will cause the object to be offset instead of snap back, this behavior is gone if any source is added, even if the source/constraint weight is 0. Repro: Add a parent constraint to an object that's placed on the hand, leave it with 0 sources Activate "Freeze to world" Move away from the object Disable "Freeze to world" Observe the object being unfrozen, but offset Adding any source (with a transform) fixes this, regardless of weights. Update: It appears to work in editor, but in game offsets are almost always still baked, which makes this even weirder.

Using the pop-culture reference "Something 2: Electric Boogaloo" in a VRC world name results in "Boogaloo" being changed to "Bogeyman". It was actually difficult for me to find out why - extremist American anti-government movements don't feature much internationally - and so I very much doubt anyone would read this other than a whimsical reference to the 1984 breakdancing movie. Can we NOT let the racists ruin everything nice please?

The current logo has no spacing between VR and Chat. Launch an avatar project from VRChat Creator Companion/ALCOM with SDK 3.10.5 installed. Open the VRChat SDK Splash Screen (navigate to VRChat SDK → Splash Screen from the title bar). Open the VRChat SDK Control Panel (navigate to VRChat SDK → Show Control Panel), check the Authentication, Content Manager and Settings panels.

Right now, rim lighting applies everywhere based on view angle, which makes light bleed into weird spots on Quest avatars like inside hair crevices, clothing folds, and mouth cavities. A simple grayscale mask slot (or channel selector) to multiply against the rim intensity would fix the glow artifacts and make Quest fallbacks look way cleaner and closer to PC toon setups (like Poiyomi/lilToon).

So I sent I thingy but in the wrong category and this time I have photo's :>. But I was having this issue and I don't know if anyone else has had it. Buuuut this has happened with THREE avis (so far) that I have been working on. But having the avatar descriptor seems to fully disable scene preview and animation recording for some odd reason. I recreated a new project and it did it, I made a new scene, it worked for a day then I went to do something, came back and the bug resurfaced. Please help ;-;

Please add a warning with Auto Fix button if Post-process Layer component attached to Reference camera has Anti-aliasing set to anything except None. Right now SDK only warns if TAA is selected but not FXAA or SMAA. Any of these methods produce blurry visuals in worlds and making distant text unreadable while in VR and SDK should discourage people from using them (or maybe even block uploads). They also does not play well with built-in MSAA that provides much higher quality image.

As a content creator, selecting colors for customizing avatars is a common use of the radial slider on avatars. However radials are not the best use of a color selector as they have no real preview and often need multiple radials to control one color. It would be nice if we could have an actual color picker widget type for expression menus.

SDK Version: 3.10.3 When a UdonSharpBehaviour contains an SDK-proxied event method (such as public void OnAudioFilterRead ) that isn't referenced externally elsewhere in the program, the UdonSharp compiler fails to export the symbol under the expected proxied event name. The entry point ends up exported as something like __0_OnAudioFilterRead (the internal/mangled name) instead of _onAudioFilterRead . This causes the entry-point check inside UdonBehaviour to fail, so the event proxy is never registered and the user's method silently never fires. Reference code path on the SDK side: if (_program.EntryPoints.HasExportedSymbol("_onAudioFilterRead")) { RegisterEventProxy<OnAudioFilterReadProxy>(); } Because HasExportedSymbol("_onAudioFilterRead") returns false, RegisterEventProxy<OnAudioFilterReadProxy>() is never called and the proxied event is never delivered. Steps to reproduce: Create a UdonSharpBehaviour with public void OnAudioFilterRead(float[] data, int channels) . Don't reference the method from any other script, UI event, or SendCustomEvent call. Enter Play mode with an audio source that should drive the filter. Observe that OnAudioFilterRead is never invoked. Inspect the compiled program's exported symbols — the entry point is __0_OnAudioFilterRead instead of _onAudioFilterRead . Note: OnAudioFilterRead is also not available in udongraph

Any project prefab containing a UdonSharpBehaviour will be recreated after being deleted. The same will happen even if the files are deleted from the file explorer. It's also happening silently without any warning in the console. Creators unaware of this could run into serious issues. This was not an issue under 3.10.4. Environment World SDK 3.10.5 Reproduction Create a project prefab with a UdonSharpBehaviour Delete that same Prefab from Unity