[946] UdonSync now fails with UInt64
complete
Reimajo
Since last Update (946):
UdonSync now fails to accept UInt64 on client-side when network packets are received, claiming it is unsupported, while it is officially supported and worked before:
-----------------------------------------------------------------------
[FlatBufferNetworkSerializer] Caught ArgumentException while encoding UdonSync: Unsupported type UInt64
-----------------------------------------------------------------------
Our synced variable is declared like this:
[HideInInspector, UdonSynced(UdonSyncMode.None)]
public ulong _syncData1 = 0;
Log In
Phasedragon
updated the status to
complete
Not sure when, but this was fixed. All primitive types are now supported including UInt64.
EvolvedAnt
Is there any update on this bug? Using ulong with bit shifting is super efficient for sending more networked data without bogging it down or reaching the networking limits.
Most worlds are going to have to send twice as much network data because of this bug forcing us to use less efficient data types.
I wrote a significant amount of code I spent all day on, only to find out this data type no longer works.
Tested on the latest SDK version as of Jan 12 2021: VRCSDK3-WORLD-2020.12.09.04.44_Public
ReadyPlayerEmma
This appears to still be the case. At least it was for me. I can get normal int64 / long to work fine though. It also works for unsigned 32-bit integers. It seems to only be unsigned 64-bit (ulong) that fails.
I also see that same log message when encountering the issue.
This is on the current Udon SDK release, with the current non-beta client.
SDK used: VRCSDK3-WORLD-2020.08.07.18.18_Public.unitypackage
Reimajo
Adding a few details: The sending side is always the instance master and there are no errors at all on master-side. Client-side is only reading the value and completely fails to do so for all our test-users, every time the master changes the value. Client side never attempts to change this value, the error message from VRChat with "encode" in it is a bit misleading. We've used the lates Client, latest SDK, latest version of UdonSharp.