#Syncvar Modifying In edit mode (18.0.1)
14 messages · Page 1 of 1 (latest)
looks like part of the issue also that k__BackingFieldNetId doesn't get set in the Inspector properly it's 0
this error comes from setting fire code the one above
I don't know what 18.0.1 is supposed to mean, but netId's don't exist until runtime, so trying to edit a SyncVar of type Network Identity is sure to fail. NI/NN/GO shouldn't be in SyncVars anyway because whaterver they reference might not exist on the client, so they'd turn to null.
humm, yeah they came across that issue,
the best workaround I found for doing it is just on start setting it manually so picks up all the IDs and stuff
support could be theoretically added if it uses the scenes ID ( vaguely remembering that something )
shouldn't be a problem for too long since, will be moving to loading maps in runtime and that should work fiine
doesn't matter - it's a race condition. By "exist" I meant "spawned"
Almost always when this comes up, there's a better way than SyncVars, or you're trying to get client to do server stuff
certainly true with the service since its, synchronising a state of how machines are connected just for the admin UI,
technically would be better practice to just write something custom to send the data over how stuff is connected, but I did want the map saving system to have the most complete picture of the server map it could
found a workaround for it and, the planned future roadmap we won't be using scenes , so wouldn't be an issue for too long
shall I mark as a result?
*resolved
sure