World/Udon Bugs & Feature Requests

Ever since I went ahead to update my world with the latest update in mind (SDK 3.9.1-beta.1], anyone trying to join it will receive an "Unusual Client Behavior" and be kicked out of the world immediately. I tried to delete any changes done in the world in the hope to pinpoint the problem but the problem still occurred and even after downgrading to SDK 3.9.0 it still gives the error. If it helps to solve the issue, I noticed that messing with my PlayerObject pool (despite the fact I have not touched it once for the update) and removing then adding back some object prevented the error from showing up. Alas when I decided to arrange it after I noticed some script were broken with the newer PlayerObject setup in the world that fixed the error, the error showed up again, even when I used the backup scene I saved that worked before, that one ALSO DIDN'T WORK. This is the world currently being affected by this issue : https://vrchat.com/home/world/wrld_37abea33-f34c-4706-8e6b-2f69e414fc5d/info I have tried everything to see if the problem came from my world but the problem feels way too random for it to be the case.

I tried this both with udon graph and udon sharp. Both times, when calling the Respawn function, the udon script throws an error and halts. It says that the reference is not set to an instance of an object, even though every time, I check, and there is an object with a VRCObjectSync attached to it that Respawn() is called from. And Respawn() is called from the VRCObjectSync, and not the GameObject. This is the error I get from udon graph: [UdonBehaviour] An exception occurred during Udon execution, this UdonBehaviour will be halted. VRC.Udon.VM.UdonVMException: The VM encountered an error! Exception Message: An exception occurred during EXTERN to 'VRCSDK3ComponentsVRCObjectSync.__Respawn__SystemVoid'. Parameter Addresses: 0x00000000 Object reference not set to an instance of an object ---------------------- Program Counter was at: 28 ---------------------- Stack Dump: ---------------------- Heap Dump: 0x00000000: Microphone (VRC.SDK3.Components.VRCObjectSync) 0x00000001: Microphone (VRC.SDK3.Components.VRCObjectSync) 0x00000002: VRCSDK3ComponentsVRCObjectSync.__Respawn__SystemVoid ---------------------- Inner Exception: ---> VRC.Udon.VM.UdonVMException: An exception occurred during EXTERN to 'VRCSDK3ComponentsVRCObjectSync.__Respawn__SystemVoid'. Parameter Addresses: 0x00000000 ---> System.NullReferenceException: Object reference not set to an instance of an object at VRC.SDK3.ClientSim.ClientSimObjectSyncHelper.RespawnObject (VRC.SDK3.Components.VRCObjectSync sync) [0x00000] in .\Packages\com.vrchat.worlds\Integrations\ClientSim\Runtime\Helpers\ClientSimObjectSyncHelper.cs:18 at VRC.SDK3.Components.VRCObjectSync.Respawn () [0x00009] in <6ff4ff48394b436282bb70dc0ff277c2>:0 at VRC.Udon.Wrapper.Modules.ExternVRCSDK3ComponentsVRCObjectSync.__Respawn__SystemVoid (VRC.Udon.Common.Interfaces.IUdonHeap heap, System.Span`1[T] parameterAddresses) [0x0001d] in <b001fa9908f1453c979dae8b67f4c4f7>:0 at VRC.Udon.VM.UdonVM.Interpret () [0x00273] in <62e4a0d35446446b8fa1f8e5755bcfaa>:0 --- End of inner exception stack trace --- at VRC.Udon.VM.UdonVM.Interpret () [0x0033c] in <62e4a0d35446446b8fa1f8e5755bcfaa>:0 --- End of inner exception stack trace --- at VRC.Udon.VM.UdonVM.Interpret () [0x00436] in <62e4a0d35446446b8fa1f8e5755bcfaa>:0 at VRC.Udon.UdonBehaviour.RunProgram (System.UInt32 entryPoint) [0x00063] in .\Packages\com.vrchat.worlds\Runtime\Udon\UdonBehaviour.cs:1098 UnityEngine.Debug:LogError (object,UnityEngine.Object) VRC.Core.Logger:LogError (string,string,UnityEngine.Object) VRC.Udon.UdonBehaviour:RunProgram (uint) (at ./Packages/com.vrchat.worlds/Runtime/Udon/UdonBehaviour.cs:1112) VRC.Udon.UdonBehaviour:RunEvent (string) (at ./Packages/com.vrchat.worlds/Runtime/Udon/UdonBehaviour.cs:1306) VRC.Udon.UdonBehaviour:ManagedUpdate () (at ./Packages/com.vrchat.worlds/Runtime/Udon/UdonBehaviour.cs:551) VRC.Udon.UdonManager:Update () (at ./Packages/com.vrchat.worlds/Runtime/Udon/UdonManager.cs:354)

There are issues with trolls loading into a world with an avatar that VRChat's logs report like this: Error - [AssetBundleDownloadManager] Avatar 'avtr_becb0302-64b5-47b3-ab0d-2a0dcbdef294' did not pass initial checks and won't be downloaded: AssetBundleBadPerformance The users are in the world able to listen in on conversations and manipulate objects like the image loader, but have no physical presence in the userlist for any active moderation. VRChat should not permit any user in a world with an invalid avatar like this. At the moment since their names and avatars are getting logged, I'm seeing if there are anti-troll measures that can be taken against such users and logging/reporting more verbose information. But to prevent them from actually causing harm in the world, I'd need to work with world creators to develop our own anti-troll systems to ensure such malicious hackers do not interrupt events. In this case, they disrespected people sharing stories about their loved ones who passed away during Dia de Muertos. That was disrespectful to the highest degree and they have been banned from the group. I've already reported the user and sent all my info to VRChat's ToS team for investigation so they do not cause harm to anyone else. This isn't just a bug, this is a signficant security risk.

Over the past few days, I’ve received multiple reports from Quest 2 players saying that VRChat crashes while loading my world Jetski Rush ( https://vrchat.com/home/world/wrld_2ad5bb30-adf7-4de1-ba50-ae9b6b4689fe/info ). There’s no error message, the client just closes during the loading screen. I haven’t updated the world recently, and it was working fine before. I tried to reproduce the issue myself but wasn’t able to. The world loads and runs normally for me and several other players. We don’t have access to the logs from affected users, so it’s difficult to pinpoint the cause. It might be related to a recent VRChat update, since the crashes only started happening recently without any changes on our side.

What I'm going to describe is a very niche bug, that won't bother a lot of people, but it's been preventing me from porting some cool worlds like "Thad Recursive Room" to Quest, because it relies on some render tricks with multiple cameras. If you have a camera without a render target, it will render on screen. And if you set the "depth" parameter greater than 0, it will render after the main camera, effectivly acting like an overlay camera. So far, everything works. But doing that with more than 1 camera does not work. So if you use a second camera with an even higher depth value, it's content won't show up on the screen as long as the first overlay camera is still on (That is, if the content of the second overlay camera is actually performing a z test). But it gets stranger from here: if I open and close the menu a few times and also click on some of the menu tabs like the world menu. Every now and then it causes a glitch that will make the content of the second overlay camera sort of appear from there on out. What I can see then, is that when I move my head, it moves away an invisible shape that was blocking the content of the second overlay camera. And that shape fits perfectly the object it is supposed to render. It is as if the z values of the second overlay camera are already written to the depth buffer before the actual rendering of the second overlay camera begins and then the z test fails against its own values. But after the menu glitch, the occluding depth image seems to be frozen in place and I can partly move it out of the way by changing my view. Also: one time I tried something similar with cameras rendering before the main camera (depth parameter is set to a negative value, and main camera is set to clear nothing). Results were similar, and after I managed to get something visible with the menu glitch, it appeared as if the cameras that render earlier than the main camera were very pixelated, which was also surprising. I've been also experimenting with manually calling render() on multiple cameras that are supposed to render on screen during several render related events (for example in OnPostRender of the first overlay camera), but no luck getting their content to show in any way.

Issue: VRCCameraSettings.ScreenCamera is supposed to be the way to get the currently used camera for the player. This is especially useful when using it to try to attach things like a HUD etc to the player. However, when using Focus View on mobile the scene camera is no longer correct and reports it's position and rotation as the world origin. Reproduction Steps: Go to my Modern UIs Demo World . Go to the wall in front of you and click on any of the notification buttons to enter Focus View . Press the Send Notification Button to send a notification. If you then exit Focus View you will see the notification, but once you enter it it will be gone again. Note: If you go to the back of the wall and use the buttons there you can actually see it flying back to 0 0 0. Expected Behaviour: VRCCameraSettings.ScreenCamera should always represent the camera currently used by the user, even while in Focus View . Attachments: Here is a video showcasing the issue:

Events like: InputUse InputJump InputMoveHorizontal InputMoveVertical InputLookHorizontal InputLookVertical Are still called even if the GameObject is disabled with SetActive(false) (See screenshots). But disabling the script with enabled = false; works. I am not sure if this is an expected behavior, but personally that issue confused me, If I disable a GameObect I would expect everything to be disabled, not just certain events like Update(), FixedUpdate(), OnDeserialization()...

This has been broken for a long while, since I can remember, Auto Hold does not work for Oculus, or Index, but does work for Desktop, and (last I checked) Vive.

Defining a method parameter of a user-defined enum type with a default value causes the UdonSharp compiler to throw during binding. The same method compiles successfully when the default value is removed. This issue does not reproduce with Unity/SDK-defined enums (e.g., UnityEngine.HumanBodyBones , VRC_Pickup.PickupHand). Reproduction using UdonSharp; public class EnumTest : UdonSharpBehaviour { // Compile error public void TestMethod(TestEnum testEnum = TestEnum.ValueB) { } } public enum TestEnum { ValueA, ValueB, ValueC } Actual Behavior Compile fails with Assets/Main/Misc/Enum/EnumTest.cs(6,0): System.ArgumentException: Type provided must be an Enum. Parameter name: enumType at System.Enum.ToObject (System.Type enumType, System.Int32 value) at System.Enum.ToObject (System.Type enumType, System.Object value) at UdonSharp.Compiler.Symbols.ParameterSymbol..ctor (...) at UdonSharp.Compiler.Symbols.UdonSharpBehaviourTypeSymbol.CreateSymbol (...) ... (Full message attached below) The exception is thrown inside ParameterSymbol when UdonSharp tries to evaluate a parameter’s default value using Enum.ToObject(enumType, value) during compilation. For user-defined enums, this call receives an argument that is not recognized as a valid enum type for some reason, which causes System.ArgumentException: Type provided must be an Enum . Workarounds Avoid using default parameter values for enums and provide an overload as a pseudo-default instead public void TestMethod(TestEnum testEnum) { } public void TestMethod() => TestMethod(TestEnum.ValueA);

Shorts and Longs cannot be used in modules that ask for a Float as a parameter, but the regular 32 bit integer works.