We(not me yet) still suffers from REs and still dont have any improved online logging.
Tracking down a RE manually is just not working. I can spend weeks searching for a RE and I am not going to find anything. We need better tools for this!!!
The game simply computes a checksum of everything present on the map and tells other players "I have a checksum of 0xDEADBEEF for frame 12345". If the other player has a different checksum in that frame, it will panic and shoot itself with a desync. What specifically do you expect us to log here? We can't really tell why the checksum doesn't match given only 4 bytes.
We can change the Recon Error dialog so that you can create a memory dump when it happens, but we will still need more than one player's dump to diagnose anything, and unlike sync.txt, normal people can't read these dumps.
Actually we could hunt down AFAIK all recon posted up here. The reason was that TIB2 gained an new image and I forgot to put it's mix in. TIB2 could be spawned from harvesters and there is the third-ore from map issue.
And another one from standard Battle. http:// yras.cncguild. net/Ares/ issue1xxx2. 7z