AdamBebko
commented
2 years ago This is a common unity issue, not related to bmlTUX. It means you have two event system components somewhere in the scene. You can use Unity’s search tools to help diagnose the problem. You only need one ever. They collect input events from the user, and shouldn’t be collected twice. You should keep the event system that is the “longest lived” in the scene. So if one is attached to a game object that won’t survive the whole scene, maybe delete it, and create a new one at the root of your scene that lasts for the lifetime of your scene.
On Mar 23, 2022, at 10:15 AM, Michael W @.***> wrote:
Hi Adam
After updating to v3.0.1, Unity will start complaining about the following:
"There are 2 event systems in the scene. Please ensure there is always exactly one event system in the scene UnityEngine.EventSystems.EventSystem:Update ()".
This message would disappear if I were to disable either the experiment runner object or the SteamVR Player object.
https://user-images.githubusercontent.com/15709552/159719623-34a1ed7a-7e81-4ce2-9f09-a320e675cdd4.png This does not affect the execution of the experiment; rather, it just produces thousands of warnings. Is this something that others also experience? Thanks!
— Reply to this email directly, view it on GitHub https://github.com/BioMotionLab/TUX/issues/65, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKKFU45XT4HJ53ZYX3XOMEDVBMRO7ANCNFSM5ROFW7LA. You are receiving this because you are subscribed to this thread.
xywang01
Hi Adam
After updating to v3.0.1, Unity will start complaining about the following:
"There are 2 event systems in the scene. Please ensure there is always exactly one event system in the scene UnityEngine.EventSystems.EventSystem:Update ()".
This message would disappear if I were to disable either the experiment runner object or the SteamVR Player object.
This does not affect the execution of the experiment; rather, it just produces thousands of warnings. Is this something that others also experience? Thanks!