Desync Loop (crc issue)
Posted: Wed Dec 03, 2014 5:27 pm
*Edit* I think should have been posted in bugs.
I understand this is alpha and am not complaining. I would just like to get some ideas as to either prevent this loop in the future or fix the one we are experiencing.
Info:
My buddy and I have been playing a game which is about 10-14 hours old.
We have had occasional desyncs but they are far and few apart.
We play with 90ms lat.
We use DyTech mods less tools (because the tool crafting button will not appear in mp games)
Problem:
My friend will continually desync every 3 seconds. He has a ton of crc errors in his logs.
Potential Causes:
I did pick up damaged items, I have since removed but to no avail.
We built a base almost on top of the enemy spawning area. Could the proximity of the structures be causing to many messages causing the desync?
Attempted Fixs:
We deleted the temp and temp-cache.
We increased lat
We matched thread count to 2.
Questions:
Is the loop recoverable?
How can we prevent this moving forward?
What is a crc error mean?
Any help diagnosing this would be greatly appreciated. We will be doing some more testing this evening on a new map trying to recreate the error.
Thanks,
I understand this is alpha and am not complaining. I would just like to get some ideas as to either prevent this loop in the future or fix the one we are experiencing.
Info:
My buddy and I have been playing a game which is about 10-14 hours old.
We have had occasional desyncs but they are far and few apart.
We play with 90ms lat.
We use DyTech mods less tools (because the tool crafting button will not appear in mp games)
Problem:
My friend will continually desync every 3 seconds. He has a ton of crc errors in his logs.
Potential Causes:
I did pick up damaged items, I have since removed but to no avail.
We built a base almost on top of the enemy spawning area. Could the proximity of the structures be causing to many messages causing the desync?
Attempted Fixs:
We deleted the temp and temp-cache.
We increased lat
We matched thread count to 2.
Questions:
Is the loop recoverable?
How can we prevent this moving forward?
What is a crc error mean?
Any help diagnosing this would be greatly appreciated. We will be doing some more testing this evening on a new map trying to recreate the error.
Thanks,