Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[1.1.8] Udon sync mode getting set to Continuous when a NoVariableSync is on the same GameObject as a Manual sync #134

Open
techanon opened this issue Jun 4, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@techanon
Copy link

techanon commented Jun 4, 2023

Describe the bug in detail:
Under the condition of having two udon behaviours on a single gameObject, when the first one is set to NoVariableSync, and the second is set to ManualSync, the gameObject will implicitly default to Continuous regardless of the second script.

Provide steps/code to reproduce the bug:
Create two scripts, one with NoVariableSync mode and the other with Manual.
Add a synced variable, like a string for example, to the Manual synced script.
On the manual sync script, add the OnPreserialization and OnDeserialization events with a log statement in each.
Add both scripts to the same game object. The order of the scripts don't matter.
Build and test and watch the logs get spammed with the serialization logs.

Expected behavior:
The GameObject should have sync mode of the first script in the order on the game object that is not of NoVariableSync. NoVariableSync should not be taken into consideration when choosing sync mode.

Additional Information:
Here's a sample video of the issue occurring:

Unity_2023-06-03_21-25-47.mp4
@techanon techanon added the bug Something isn't working label Jun 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant