ClientSimulator Camera may stop working in World SDK 3.5.2
complete
Wing_
After you enter Play Mode in Unity, and press the "CloseMenu" On "VRChat Client Simulator", the camera stop working therefore the screen shows "Display 1 No cameras rendering".
I have no idea how to reproduce this bug, but I heard (not sure) that it may be cause by gameobject with UdonBehaviour attached is Instantiated in a public event.
Downgrade to SDK 3.5.1, it works again.
Log In
This post was marked as
complete
This post was marked as
available in future release
Wing_
OMG thanks for fixing this bug you are the best
StormRel
tracked
_
_tau_
Merged in a post:
ClientSim: "display 1 no cameras rendering" while controlling robot in Base/World SDKs 3.5.2
Purpzie
I'm trying to test a world in Unity. With SDKs 3.5.1, this works flawlessly. After upgrading to 3.5.2 (with no other differences), exiting the clientsim menu to control the robot stops rendering anything. In the scene view, I can see that the robot is being controlled, but the game view gets stuck on an old frame.
After some digging, it seems to be the remote scale device from JetDog's scaling prefabs that's causing this. This doesn't seem to be their fault. It was working in the previous SDK and a prefab error really shouldn't affect clientsim this badly.
[01:08:51.434][ClientSimUdonHelper] Destroying uninitialized Helper. Object: /Main/New Stuff/Remote scale device/Canvas/Panel/Scroll View/Viewport/Content/Button ref(Clone)
UnityEngine.Debug:LogWarning (object)
VRC.SDK3.ClientSim.ClientSimExtensions:LogWarning (string,string) (at ./Packages/com.vrchat.worlds/Integrations/ClientSim/Runtime/Utilities/ClientSimExtensions.cs:54)
VRC.SDK3.ClientSim.ClientSimExtensions:LogWarning (object,string) (at ./Packages/com.vrchat.worlds/Integrations/ClientSim/Runtime/Utilities/ClientSimExtensions.cs:59)
VRC.SDK3.ClientSim.ClientSimUdonHelper:Start () (at ./Packages/com.vrchat.worlds/Integrations/ClientSim/Runtime/Helpers/ClientSimUdonHelper.cs:47)
kurotori
I have confirmed similar symptoms.
This symptom will definitely occur if a game object with UdonBehaviour attached is instantiated during OnPlayerJoin.