Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.2.X, 2018.3.X
Votes
0
Found in
2018.2.8f1
Issue ID
1085466
Regression
No
Syncvar refresh is not being updated in sequence
Reproduction steps:
1. Open the attached project.
2. Create a Standalone build.
3. Open the built project.
4. Click 'LAN host(H)'.
5. Play the 'SampleScene' in the Unity project.
6. Click 'LAN Client(C)'.
7. Check the Console.
Actual behavior:
- You should see "ERROR: 'serverCounter = X' should not be less or equal than 'counter = X'" error message in the Console when syncvar is not being updated in sequence.
Notes:
- Check the original case description for a potential solution.
- Screenshot attached.
- The project doesn't work with 2018.1 and older Unity versions.
Reproduced with:
2018.2.13f1, 2018.3.0b6, 2019.1.0a4
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
jose_caetano_neto
Feb 01, 2019 03:41
This update appears to introduce a new error.
New clients don´t get current syncvar values on connect, after this update.
jose_caetano_neto
Feb 01, 2019 03:39
Same as arfish here.
Unity 2018.2.19, Unity 2018.2.20 and Unity 2018.3.0f2 NetworkTransform fails enterily on clients side.
SomeAlexander
Jan 30, 2019 15:16
Syncvars broken in Unity 2018.2.20, Unity 2018.3.3f1. Work in 2018.2.18.
ifdef_ben
Jan 17, 2019 16:06
Indeed, since that fix in 2018.2.19 we're getting errors when deserializing syncvars.
We have multiple NetworkBehaviour on the same game object and I suspect that the deserialization does not occur in the same order as the serialization.
We've tried implementing OnSerialize and OnDeserialize ourselves and noticed the NetworkWriter and NetworkReader indexes are not the same. So we're getting garbage when Deserializing (either with or without the manual implementation of the serialization functions). The behavior was correct in Unity 2018.2.18.
ifdef_ben
Jan 17, 2019 16:04
Indeed, since that fix in 2018.2.19 we're getting errors when deserializing syncvars.
We have multiple NetworkBehaviour on the same game object and I suspect that the deserialization does not occur in the same order as the serialization.
We've tried implementing OnSerialize and OnDeserialize ourselves and noticed the NetworkWriter and NetworkReader indexes are not the same. So we're getting garbage when Deserializing (either with or without the manual implementation of the serialization functions). The behavior was correct in Unity 2018.2.18.
Aurimasp
Dec 20, 2018 12:43
Hey,
Could you please report this issue using our bug reporter?
jykholodia
Dec 20, 2018 11:10
Same as arfish here.
Unity 2018.2.19, Unity 2018.2.20 and Unity 2018.3.0f2 NetworkTransform fails enterily on clients side.
arfish
Dec 18, 2018 14:01
This update appears to introduce a new error.
New clients don´t get current syncvar values on connect, after this update.
It works fine in 2018.2.18, and fails in 2019.2.20.