SDK Bug & Feature Requests

In newer SDK's [currently tested 3.10.3] the GameObject's layer that the VRC_Pickup component is added to doesn't auto swap the layer to [Pickup] anymore. This is an issue as the pickup layer had passthrough on collision and stopped pickups from stopping movement, flinging players around, or worse though the world breaking experiences. A previous project I had [SDK 3.8.1] retains this functionality. So I'm unsure when this stopped being changed or why. This would prevent new world creators from having to set the layers manually if they even learn of these issues.

When a Gameobject with a VRC Raycast component scales, the ray distance should optionally scale with it. This would be useful for keeping raycast distances proportional to the avatar scale. This could be a toggle on the component? Example scenario: A raycast on a gameobject at the avatar's chest bone with a distance of 0.2. If the avatar is scaled up, this raycast is now doesn't reach outside of the body. The current solutions for this (animating the distance based on the scale parameter or making the distance unnecessarily large to begin with) seem like they'd be negative to performance. This ability would also be very useful for those distributing prefabs to less technical users. The user installing a prefab with a raycast just has to scale and adjust it into position on their avatar ~ no need to find the component to adjust the distance.

If a contact is enabled in the editor play mode while contacts are being processed in their background thread, the addition of that contact crashes with the following stack trace, and fails to process from that point on. This issue is new in VRCSDK 3.7.3 and still exists in 3.7.4. InvalidOperationException: The previously scheduled job ContactManager:UpdateReceivers writes to the Unity.Collections.NativeArray`1[VRC.Dynamics.ContactManager+ReceiverData] UpdateReceivers.receivers. You must call JobHandle.Complete() on the job ContactManager:UpdateReceivers, before you can read from the Unity.Collections.NativeArray`1[VRC.Dynamics.ContactManager+ReceiverData] safely. Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle.CheckReadAndThrowNoEarlyOut (Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle handle) (at <cb81df0c49c643b1a04d9fc6ccca2433>:0) Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle.CheckReadAndThrow (Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle handle) (at <cb81df0c49c643b1a04d9fc6ccca2433>:0) Unity.Collections.NativeArray`1[T].CheckElementReadAccess (System.Int32 index) (at <cb81df0c49c643b1a04d9fc6ccca2433>:0) Unity.Collections.NativeArray`1[T].get_Item (System.Int32 index) (at <cb81df0c49c643b1a04d9fc6ccca2433>:0) VRC.Dynamics.ContactManager.FindAvailableId () (at <18f19c27e14b4ae6a2e430e7e9917e85>:0) VRC.Dynamics.ContactManager.AddContact (VRC.Dynamics.ContactBase contact) (at <18f19c27e14b4ae6a2e430e7e9917e85>:0) VRC.Dynamics.ContactBase.Start () (at <18f19c27e14b4ae6a2e430e7e9917e85>:0) VRC.Dynamics.ContactReceiver.Start () (at <18f19c27e14b4ae6a2e430e7e9917e85>:0) And then every frame after that (because the contact was not added to the manager properly): IndexOutOfRangeException: Index 65535 is out of range of '4096' Length. Unity.Collections.NativeArray`1[T].FailOutOfRangeError (System.Int32 index) (at <cb81df0c49c643b1a04d9fc6ccca2433>:0) Unity.Collections.NativeArray`1[T].CheckElementReadAccess (System.Int32 index) (at <cb81df0c49c643b1a04d9fc6ccca2433>:0) Unity.Collections.NativeArray`1[T].get_Item (System.Int32 index) (at <cb81df0c49c643b1a04d9fc6ccca2433>:0) VRC.Dynamics.ContactReceiver.UpdateContact () (at <18f19c27e14b4ae6a2e430e7e9917e85>:0) VRC.Dynamics.ContactManager.HandleDynamicsFrameComplete () (at <18f19c27e14b4ae6a2e430e7e9917e85>:0) VRC.Dynamics.VRCAvatarDynamicsScheduler.FinalizeJob (System.Boolean force) (at <18f19c27e14b4ae6a2e430e7e9917e85>:0) VRC.Dynamics.VRCAvatarDynamicsScheduler.OnCameraPreCull (UnityEngine.Camera cam) (at <18f19c27e14b4ae6a2e430e7e9917e85>:0) UnityEngine.Camera.FireOnPreCull (UnityEngine.Camera cam) (at <cb81df0c49c643b1a04d9fc6ccca2433>:0)

When the editor option "Enter Play Mode Options" is checked, and "Reload Domain" and "Reload Scene" are unchecked, dynamics / contacts no longer work in play mode after the first session. This is because VRCAvatarDynamicsScheduler._latestCompletedFrameNumber is not being reset to -1 when domain reloads are disabled, so the next time you enter play mode, it has to wait until the frame number of your last session before SignalFrameComplete gets run again. These play mode options are selected by default for all projects using VRCFury, so this is a very widespread issue. This is a new issue in 3.7.6.

In VRCSDK 3.8.1 and later several log invokations ( VRC.Core.Logger.Log() ) in internal SDK assemblies (e.g. VRCSDKBase-Editor.dll and VRCCore-Editor.dll ) as well as VRC.SDKBase.Editor.EnvConfig.cs do not define the log category anymore, resulting in excessive console logging with no real added value to the end user. In 3.7.5 and earlier SDKs with old logger, DebugLevel.All enum was passed as a parameter every time these messages would be logged, resulting in nothing being visible to the end user. From 3.7.6 up to 3.8.0 after SDK logger rewrite, "All" string was passed as a parameter due to the DebugLevel enum getting replaced by a generic category string parameter, still resulting in all messages being hidden. In previous versions of the SDK not a single log entry would appear in the editor's console unless something important was actually happening and the end user should be informed about it. In 3.8.1 many of the category parameters were mysteriously removed, resulting in 14 entries appearing in the console on every assembly reload (see attachments). The increased logging takes up third of the console window's footprint on every assembly reload and makes it very difficult to spot actually important log entries. Below I have listed the different messages originating from DLLs in the SDK with their stack traces. (The rest are primarily from VRC.Editor.EnvConfig:ConfigurePlayerSettings() located in the VRC.SDKBase.Editor assembly) Reloading Assemblies UnityEngine.Debug:Log (object,UnityEngine.Object) VRC.Core.Logger:Log (string,string,UnityEngine.Object) VRC.SDK3.Editor.EditorAssemblies:OnCompileScripts () No local config found at 'C:/Users/[REDACTED]/AppData/LocalLow/[REDACTED]/[REDACTED]\config.json' UnityEngine.Debug:Log (object,UnityEngine.Object) VRC.Core.Logger:Log (string,string,UnityEngine.Object) VRC.Core.LocalConfig:FetchConfig (System.Action,System.Action) VRC.Core.LocalConfig:.ctor (string,bool,bool) VRC.Core.ConfigManager:.cctor () VRC.Editor.EnvConfig:ConfigureSettings () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/EnvConfig.cs:125) VRC.Editor.EnvConfig:EditorUpdate () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/EnvConfig.cs:91) UnityEditor.EditorApplication:Internal_CallUpdateFunctions () No local config found at 'C:/Users/[REDACTED]/AppData/LocalLow/[REDACTED]/[REDACTED]\null' UnityEngine.Debug:Log (object,UnityEngine.Object) VRC.Core.Logger:Log (string,string,UnityEngine.Object) VRC.Core.LocalConfig:FetchConfig (System.Action,System.Action) VRC.Core.LocalConfig:.ctor (string,bool,bool) VRC.Core.ConfigManager:.cctor () VRC.Editor.EnvConfig:ConfigureSettings () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/EnvConfig.cs:125) VRC.Editor.EnvConfig:EditorUpdate () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/EnvConfig.cs:91) UnityEditor.EditorApplication:Internal_CallUpdateFunctions () FetchConfig UnityEngine.Debug:Log (object,UnityEngine.Object) VRC.Core.Logger:Log (string,string,UnityEngine.Object) VRC.Core.RemoteConfig:FetchConfig (System.Action,System.Action) VRC.Core.BaseConfig:Init (System.Action,System.Action,bool) VRC.Editor.EnvConfig:ConfigureSettings () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/EnvConfig.cs:128) VRC.Editor.EnvConfig:EditorUpdate () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/EnvConfig.cs:91) UnityEditor.EditorApplication:Internal_CallUpdateFunctions () finshed fetching and set config UnityEngine.Debug:Log (object,UnityEngine.Object) VRC.Core.Logger:Log (string,string,UnityEngine.Object) VRC.Core.RemoteConfig/<>c__DisplayClass1_0:<FetchConfig>b__0 (VRC.Core.ApiContainer) VRC.Core.APIResponseHandler/<HandleResponse>d__5:MoveNext () Cysharp.Threading.Tasks.CompilerServices.AsyncUniTaskVoid`1<VRC.Core.APIResponseHandler/<HandleResponse>d__5>:Run () (at ./Packages/com.vrchat.base/Runtime/VRCSDK/Plugins/UniTask/Runtime/CompilerServices/StateMachineRunner.cs:104) Cysharp.Threading.Tasks.Internal.ContinuationQueue:RunCore () (at ./Packages/com.vrchat.base/Runtime/VRCSDK/Plugins/UniTask/Runtime/Internal/ContinuationQueue.cs:194) Cysharp.Threading.Tasks.Internal.ContinuationQueue:Update () (at ./Packages/com.vrchat.base/Runtime/VRCSDK/Plugins/UniTask/Runtime/Internal/ContinuationQueue.cs:159) Cysharp.Threading.Tasks.Internal.ContinuationQueue:Run () (at ./Packages/com.vrchat.base/Runtime/VRCSDK/Plugins/UniTask/Runtime/Internal/ContinuationQueue.cs:118)

Like the Physbone and Contact components, I believe the new Raycast component could benefit from having it write a couple parameters to the animator. These parameters would help simplify some setups that already exist which use constraints and contacts to get similar information out of FinalIK raycasts. Name below is the name given by the user for the parameter name similar to how it's done for Physbones. Name_Ratio - Ratio of (Current Raycast Distance/Max Raycast Distance) Name_Distance - Current distance of raycast Name_Colliding - Boolean that returns true when raycast is colliding with something. If anyone else has any parameters that they would like to suggest feel free to write in the comments.

Using UdonGraph and UdonSharp, any attempt to load from a url (String, Image, and Video) fails to run, resulting in an UdonVM error. This issue can be reproduced in any project attempting to load a URL on the 3.10.2 SDK. The Graph shown in the screenshot never has OnStringLoadSuccess/Error trigger, as the error occurs during the LoadUrl step. The issue appears to stem from Udon communicating with UniTask. I have provided the resulting error using an UdonGraph here: ----- [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 'VRCSDK3StringLoadingVRCStringDownloader.__LoadUrl__VRCSDKBaseVRCUrl_VRCUdonCommonInterfacesIUdonEventReceiver__SystemVoid'. Parameter Addresses: 0x00000000, 0x00000001 Method not found: Cysharp.Threading.Tasks.UniTask Cysharp.Threading.Tasks.UniTask.WaitWhile(System.Func`1<bool>,Cysharp.Threading.Tasks.PlayerLoopTiming,System.Threading.CancellationToken,bool)

On miss the raycasters aligned rotation is inverted from what is expected. a raycast commonly only collides with surface normals that face towards the caster, because of this it is pretty standard that the onMiss rotation defautls to a normal direction that faces the caster, but the VRCRaycast seems to invert this behavior. where on miss the result has a normal direction facing away from the caster. if the raycaster was used for range limited grounding behavior this would result in the object flipping upside down the moment the raycast no longer hits the ground which is generally undesired. Either flipping the normal or providing a value that allows us to specify a onMiss rotation would resolve this issue and allow for more specialized usecases too.

If Reload Domain is disabled, VRC Raycast components will break when you enter playmode a second time. This setting can be accessed by enabling Enter Play Mode Settings under Project Settings -> Editor Full error: ObjectDisposedException: Cannot access a disposed object. Object name: 'The NativeArray has been disposed, it is not allowed to access it'. Unity.Collections.NativeArray`1[T].Dispose () (at <cb81df0c49c643b1a04d9fc6ccca2433>:0) VRC.SDK3.Avatars.Components.VRCRaycastHandler.EnsureBuffers (System.Int32 requiredCapacity) (at <b248cace5bfa4db7b5740a80497509a1>:0) VRC.SDK3.Avatars.Components.VRCRaycastHandler.SubmitRaycasts () (at <b248cace5bfa4db7b5740a80497509a1>:0) VRC.SDK3.Avatars.Components.VRCRaycastHandler.UpdateRaycastHandler () (at <b248cace5bfa4db7b5740a80497509a1>:0) UnityEngine.Debug:LogException(Exception) VRC.SDK3.Avatars.Components.VRCRaycastHandler:UpdateRaycastHandler() VRC.Dynamics.VRCDynamicsScheduler:SignalFrameComplete() VRC.Dynamics.VRCDynamicsScheduler:CompleteDynamicsFrame() VRC.SystemsPlayerLoop:OnAvatarDynamicsComplete()

For Contact Receiver layouts, a 'Box' ShapeType would be a convenient option for buttons because they are flat (less chance of unintended input) and many buttons are square.