I'm just saying to make sure to restart your comp periodically, it helps! I'm like you though and in most games that are more than 4 people; someone gets desynced eventually... I tend to make a mental note of the times things like this happen is always when mills upgrading to next lvl (like lvl 2-lvl 3 [alot of mills]) or when mobs generate... I've noticed a number of desync's happen when the first invis wave generate, and as usual the game splits if it can into two groups, normally the one desyncer and the rest are left behind so to say. I wish I could help more because it is sad to see it happen frequently, and I'm not 100% sure but if those desyncer's would turn their graphics down I bet might desync less (or not at all as in my case)
Constant Desync
#22
Dedicated Survivor
Posted 02 September 2014 - 11:31 AM
Well, my computer is an i7/16GB memory/GTX670. So I am absolutly sure that performance is not the issue.
Since I dont have any memory of ever geting desync in any other map I've played. The problem could be within ENT's bot, or a bug on the map, or whatever other reasons.
The fact is that I was not the only one disconnected, that makes me sure that the problem is not me!
When leaks are existant in the map, they build up and cause calculation delay eventually. This in time causes any user to be in a state of processing while other computers may not be. This means for those who aren't processing the game continues. Once the player is done with the processing, the game is desynced. That would be the reason why if the map has those kind of bugs. However, when your network connection reinitialised (due route DHCP release) this problem can happen also. If you think it is a network issue, be sure to check your firewall and otherwise your DHCP release in network adapter settings/details. The warcraft 3 game is old and I am not even sure if its multithreaded. This could mean that the entire program may run on a single processor. Even if you have a high end computer, they usually consists out of multiple cores. As for ram, no, that couldn't be the issue.
#23
Dedicated Survivor
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
