1. Updated Resource Submission Rules: All model & skin resource submissions must now include an in-game screenshot. This is to help speed up the moderation process and to show how the model and/or texture looks like from the in-game camera.
    Dismiss Notice
  2. DID YOU KNOW - That you can unlock new rank icons by posting on the forums or winning contests? Click here to customize your rank or read our User Rank Policy to see a list of ranks that you can unlock. Have you won a contest and still haven't received your rank award? Then please contact the administration.
    Dismiss Notice
  3. Join the 6th Melee Mapping Contest for a chance to have your map featured in this year's Hive Cup!
    Dismiss Notice
  4. Shoot to thrill, play to kill. Sate your hunger with the 33rd Modeling Contest!
    Dismiss Notice
  5. Do you hear boss music? It's the 17th Mini Mapping Contest!
    Dismiss Notice
  6. Weave light to take you to your highest hopes - the 6th Special Effect Contest is here!
    Dismiss Notice
  7. Check out the Staff job openings thread.
    Dismiss Notice
Dismiss Notice
60,000 passwords have been reset on July 8, 2019. If you cannot login, read this.

Unit Stutter Step & Triggers

Discussion in 'World Editor Help Zone' started by Pinzu, Aug 16, 2019.

  1. Pinzu

    Pinzu

    Joined:
    Nov 30, 2007
    Messages:
    1,184
    Resources:
    3
    Spells:
    2
    Tutorials:
    1
    Resources:
    3
    Does having more running triggers cause unit movement lagg to happen earlier?

    When a player is moving large amounts of units they can begin to stutter step (unit lagg). Does the threshold for when this occurs vary depending on triggers running?
     
  2. Prince Aerrus

    Prince Aerrus

    Joined:
    Aug 8, 2019
    Messages:
    137
    Resources:
    0
    Resources:
    0
    I believe that running more trigger does induce more lag, but it also depends on the version of warcraft you are running as well as your computer.
     
  3. BizzaroFukuro

    BizzaroFukuro

    Joined:
    Dec 11, 2009
    Messages:
    198
    Resources:
    2
    Maps:
    2
    Resources:
    2
    1. Depends on the triggers. Contents of actions matter mostly.
    2. WC 1.31 overall has some major issues with performance. 1.30 was running very smooth for me.
     
  4. Pyrogasm

    Pyrogasm

    Joined:
    Feb 27, 2007
    Messages:
    3,788
    Resources:
    1
    Spells:
    1
    Resources:
    1
    My understanding is the stuttering is from the sheer number of units trying to pathfind at once, not any triggers involved. Rough estimate of how many units are on the map when this happens?
     
  5. Dr Super Good

    Dr Super Good

    Spell Reviewer

    Joined:
    Jan 18, 2005
    Messages:
    26,047
    Resources:
    3
    Maps:
    1
    Spells:
    2
    Resources:
    3
    Triggers are not directly related. Triggers may be indirectly related in that triggers causing a player to have more units moving will have an effect.

    The path finder issues movement updates at a fixed rate. This is done at a rate like 50 times per second per player in a staggered way. Each movement update lasts for a finite time, depending on the pathing complexity of the local area and if the unit collides with anything. Unit collisions will instantly discard the last movement update causing the unit to come to a stop and wait until another movement update is issued to it. Like wise issuing a new order that requires a unit move will also discard the current movement update for the unit. Movement updates can be replaced with newer ones issued to the unit, and a unit without a movement update will not move. If too many units are moving or colliding at once the rate at which movement updates are issued to the units is not sufficient to keep the units from running out of movement updates and hence the units will appear to periodically stop or "stutter step".

    This means that the maximum number of fluidly moving units a player can have is based on how complex the pathing is that the units are moving through as well as how often unit on unit collisions occur. This is why TD maps often disable unit collision and rely on very simple lane designs.

    Game speed, frame rate, network latency and CPU performance have nothing to do with this. A work around can be to divide the units over more players as the limit is on a per-player basis. Additionally avoid triggers that issue of a lot of orders requiring units move as each time such an order is issued the unit will require another movement update before it can begin to move.

    This issue is completely different and unrelated to the retarded unit movement bug. If too many map cells are mapped to regions then the path finder breaks in rather absolute way and will no longer move units around in a way that makes sense. For example it will fail to find paths between two points that are obviously connected and will think nothing of marching units repeatedly against a dead end in an almost cartoon like fashion. This is why one should only use a single "a unit enters (playable map area)" event.