Click lag problem

[tlstkwjr]

This started happening on my map at some point.

Commands such as unit training or movement commands are ignored for a while. If I click on another unit or click ground, problem is resolved after some time. (The animation that looks like the button is being pressed looks normal).

Is anyone else experiencing this issue?

 

[Pyrogasm]

Sounds to me like the player has WAY too many units and the order is delayed because of that. Wc3 unit pathing (and orders) can get weird when the owning player has too many units to control at once (pathfinding breaks down).

Approximately how many units are controlled by the each player when these issues start to appear?

 

[tlstkwjr]

Sounds to me like the player has WAY too many units and the order is delayed because of that. Wc3 unit pathing (and orders) can get weird when the owning player has too many units to control at once (pathfinding breaks down).

Approximately how many units are controlled by the each player when these issues start to appear?

I already know and suffer from that mass unit moving lag problem, but this problem is different. It's not stutters on movement commands. ignores move order completely, and ability use and training too.

 

[tlstkwjr]

I noticed an interesting phenomenon while investigating replays: when the click lag occurs, the unit does not appear to be selected in the replay. (The player claims that he clearly selected the unit and gave the command, but nothing happened.) I suspect this is because the unit to be selected only locally.
but I still don't know what in the my map is causing this, as I seem to be the only one experiencing it.

 

[Uncle]

I noticed an interesting phenomenon while investigating replays: when the click lag occurs, the unit does not appear to be selected in the replay. (The player claims that he clearly selected the unit and gave the command, but nothing happened.) I suspect this is because the unit to be selected only locally.
but I still don't know what in the my map is causing this, as I seem to be the only one experiencing it.

Well, if you're the only one that experiences it then it's probably a personal hardware/software issue.

But you may also always be playing as the "host" which could be say Player 1 (Red) which has it's own unique trigger/code logic. Perhaps there's a trigger that is clearing unit selection or modifying unit selection. You can use the Object Manager to find these functions.

 

[tlstkwjr]

Well, if you're the only one that experiences it then it's probably a personal hardware/software issue.

But you may also always be playing as the "host" which could be say Player 1 (Red) which has it's own unique trigger/code logic. Perhaps there's a trigger that is clearing unit selection or modifying unit selection. You can use the Object Manager to find these functions.

many players playing my map are complaining, so it's not a personal issue. trigger regarding unit selection is turned off after 8 minutes, but the problem still occurs after that time. I'm going to experiment with destroying that trigger next time.

and I'd like to share with the community that I was previously sufferd by a fatal error. It was reproducible under certain circumstances, and after much testing, I found the answer. When I removed the trigger that changed the unit's ownership based on whether the player selected/deselected the unit, the issue disappeared. I'm pretty sure there was a synchronization issue with unit selection.

 

[Uncle]

many players playing my map are complaining, so it's not a personal issue. trigger regarding unit selection is turned off after 8 minutes, but the problem still occurs after that time. I'm going to experiment with destroying that trigger next time.

Ah, you mentioned it seemed to only happen to you, but I suppose it was just a misunderstanding. Anyway, that could work, I recall an issue in the recent past where a disabled trigger was somehow running.

and I'd like to share with the community that I was previously sufferd by a fatal error. It was reproducible under certain circumstances, and after much testing, I found the answer. When I removed the trigger that changed the unit's ownership based on whether the player selected/deselected the unit, the issue disappeared. I'm pretty sure there was a synchronization issue with unit selection.

I recall there being safe to use Selection actions and unsafe ones. Clear Selection FOR PLAYER and Add Unit to Selection FOR PLAYER should be the safe ones if I recall correctly. But you could still create an infinite loop if these are not used properly which could crash the game. Furthermore, changing the ownership of a unit likely runs some Selection code under the hood since anyone that had that unit selected will need to be notified and possibly updated based on the outcome. For example, I have my allies Hero selected, then the trigger runs and makes them an Enemy, the game has to update to inform me that I now have an Enemy selected instead of an Ally, which changes the Selection circle and other UI elements.