anti-lag

[deama]

I saw a couple of maps have a anti-lag system, so I thought and I wanted to put one in my map but I don't know how to do it. Can anyone tell me?

 

[Assassins-Creed]

I don't believe there is an anti-lag system designed for every map but I believe you can create less lag like removing leaks and things but thats about it for any map.

 

[Axarion]

to prevent lag prevent leaks, avoid having masses of units or effects on the map and dont have to many corpses lie around.

 

[Miss_Foxy]

Is there another way to do it, like say, by scaling unit sizes down?

 

[-Kobas-]

Is there another way to do it, like say, by scaling unit sizes down?

Nah it won't work that way

Although some might argue, you can destroy your initialization triggers (on map initialization).
You know, the ones you'll never need again 100% for sure once they execute properly the first time.
You can also remove corpses of creeps - unless you have towers that can raise the dead in which case you might want to rethink that, but for the most part, removing corpses is amazing for anti-lag purposes.
Simply create a trigger that runs whenever a unit owned by the creep player dies, wait 2 seconds, and then remove the unit from the game, corpse and all.
However, the largest anti-lag issue relates to creating large numbers of units at one time, and ordering them to move.
Try to limit how many creeps appear per level to 20 or so.

From how to make TD map! Can help here I guess!

 

[jk2pach]

Don't you think you speak about GHost or GProxy who can prevent people to be kicked because of lag?


If it is about unit amount, in my own map (RC601) they are arround 400 units at the same time on the map (creeps,NPCs,buildings,heroes,dummies and fake destructables).

Creeps group is ordered to move each 6. seconds, and it cas have up to 80 units at the same time (+dummy units). There is no more lag since I delay the order to each unit of the different groups with a timer (I do not order creeps to move all at the same time, I delay it for 0.03 second per creeps).

You can also use players 13 and 14 for your creeps. The more players used for creeps mass, the less risk of lags.

 

[millzy]

this can also help for mass unit maps

• dead units
  • Events
    • Unit - A unit Dies
  • Conditions
    • ((Triggering unit) is A Hero) Equal to False
  • Actions
    • Wait 15.00 seconds
    • Unit - Remove (Triggering unit) from the game

more conditions may be needed depending on your map

 

[dardas]

hmm.. sry
what you sayd above does this:

a unit dies,
its a hero == false,
wait 15 seconds (aha! allready destroyed mui!)
remove unit.

i wanna hear what happends when using wait with many units?
1 dies, and another 1 dies at the distance of 1 ~ 15 seconds.
what happends?
1 unit is removed, the other WILL not.
so this is not helping.
most'ly ill do this:

• Anti Lag
  • Events
    • Unit - A unit Dies
  • Conditions
    • ((Triggering unit) is A Hero) Equal to False
  • Actions
    • Set MaxCount = (MaxCount + 1)
    • Set CurrentUnit[MaxCount] = (Triggering unit)
    • Set CurrentTime[MaxCount] = 15.00
    • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
      • If - Conditions
        • (Anti Lag 2 <gen> is on) Equal to False
      • Then - Actions
        • Trigger - Turn on Anti Lag 2 <gen>
      • Else - Actions

• Anti Lag 2
  • Events
    • Time - Every 0.05 seconds of game time
  • Conditions
  • Actions
    • For each (Integer A) from 1 to MaxCount, do (Actions)
      • Loop - Actions
        • Set CurrentTime[(Integer A)] = (CurrentTime[(Integer A)] - 0.05)
        • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
          • If - Conditions
            • CurrentTime[(Integer A)] Less than or equal to 0.00
          • Then - Actions
            • Unit - Remove CurrentUnit[(Integer A)] from the game
            • Set LocalCount = (LocalCount - 1)
            • Custom script: if udg_LocalCount <= 0 then
            • Custom script: if udg_CurrentUnit[GetForLoopIndexA()] == null then
            • Custom script: call DisableTrigger(GetTriggeringTrigger())
            • Custom script: endif
            • Custom script: endif
          • Else - Actions

make sure Anti Lag 2 is intially off.

 

[millzy]

lol no it is mui

the removed unit is TRIGGERING UNIT = STILL MUI WITH WAIT

 

[raft_pl]

@dardas

the removed unit is TRIGGERING UNIT = STILL MUI WITH WAIT

That's true, triggering unit is always MUI, trigger posted by millzy will work.
A skipped unit would be eventually removed either way, only after a longer period of time, due to decay mechanic.

 

[Masken]

That's because "Triggering unit" is an event response. It's no variable stored that can be overwritten it just checks whatever made it go off. (or am I wrong?)

 

[D4RK_G4ND4LF]

this can also help for mass unit maps

• dead units
  • Events
    • Unit - A unit Dies
  • Conditions
    • ((Triggering unit) is A Hero) Equal to False
  • Actions
    • Wait 15.00 seconds
    • Unit - Remove (Triggering unit) from the game

more conditions may be needed depending on your map

and if a player pauses the wait will continue running and all dead units will be removed instantly
could be abused to stop corpse explosion type spells

That's because "Triggering unit" is an event response. It's no variable stored that can be overwritten it just checks whatever made it go off. (or am I wrong?)

as far as I know it's a local variable and therefore won't be overwritten
triggers can't return stuff which is not saved somewhere

hmm.. sry
what you sayd above does this:

a unit dies,
its a hero == false,
wait 15 seconds (aha! allready destroyed mui!)
remove unit.

i wanna hear what happends when using wait with many units?
1 dies, and another 1 dies at the distance of 1 ~ 15 seconds.
what happends?
1 unit is removed, the other WILL not.
so this is not helping.
most'ly ill do this:

• Anti Lag
  • Events
    • Unit - A unit Dies
  • Conditions
    • ((Triggering unit) is A Hero) Equal to False
  • Actions
    • Set MaxCount = (MaxCount + 1)
    • Set CurrentUnit[MaxCount] = (Triggering unit)
    • Set CurrentTime[MaxCount] = 15.00
    • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
      • If - Conditions
        • (Anti Lag 2 <gen> is on) Equal to False
      • Then - Actions
        • Trigger - Turn on Anti Lag 2 <gen>
      • Else - Actions

• Anti Lag 2
  • Events
    • Time - Every 0.05 seconds of game time
  • Conditions
  • Actions
    • For each (Integer A) from 1 to MaxCount, do (Actions)
      • Loop - Actions
        • Set CurrentTime[(Integer A)] = (CurrentTime[(Integer A)] - 0.05)
        • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
          • If - Conditions
            • CurrentTime[(Integer A)] Less than or equal to 0.00
          • Then - Actions
            • Unit - Remove CurrentUnit[(Integer A)] from the game
            • Set LocalCount = (LocalCount - 1)
            • Custom script: if udg_LocalCount <= 0 then
            • Custom script: if udg_CurrentUnit[GetForLoopIndexA()] == null then
            • Custom script: call DisableTrigger(GetTriggeringTrigger())
            • Custom script: endif
            • Custom script: endif
          • Else - Actions

make sure Anti Lag 2 is intially off.

your local count is weird
and you don't really need 0.05 sec timer for units which are dead already

 

[deama]

Here's another question. If a person starts to lag and if someone pauses the game (normal pause, menu and pause) for 20 seconds or so then will he stop lagging?

 

[dardas]

well.. it wont do much,
but the pause game option does balance the game more,
because fps goes back to normal.. cuz no instance is running,
thought if the player's inet connection is in a bad state,
he will still lag. no matter what.

 

[-Kobas-]

Omg guys just change unit death time in Gameplay Constants!

 

[Assassins-Creed]

One trigger,MUI,lagless,tested,might be long but whatever it works.

• Events
  • Unit - A unit Dies
• Conditions
  • ((Triggering unit) is A Hero) Equal to False
• Actions
  • Set DyingUnit = (Dying unit)
  • Unit Group - Add DyingUnit to UnitGroup
  • Set UnitCountReal = (UnitCountReal + 1.00)
  • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
    • If - Conditions
      • UnitCountReal Greater than or equal to 2.00
    • Then - Actions
      • Set UnitCountReal = 0.00
      • For each (Integer A) from 1 to 3, do (Actions)
        • Loop - Actions
          • Unit Group - Pick every unit in UnitGroup and do (Actions)
            • Loop - Actions
              • Unit - Remove (Random unit from UnitGroup) from the game
    • Else - Actions

 

[Kamulec]

What's the sens of using this trigger if u can just:

change unit death time in Gameplay Constants!

 

[aider]

Isnt the Death time in Gameplay Constants just for how fast the "Dying" animation works? When it goes from living, to being a corpse on the ground, sinking into the ground.

 

[-Kobas-]

Yes, this way units are removed faster from game!

Dead unit is still unit, WE engine check them each time when you cast spell and do shit!

Some abilities: Rise Dead, Resurrection

There is no need for corpse in TD maps for example, up to 5 sec is ok, just to show unit dead animations and a little of bones ^^

 

[axleion]

There is no need for corpse in TD maps for example, up to 5 sec is ok, just to show unit dead animations and a little of bones ^^

that would depend on the TD's mechanic, the mapper might want to use the corpse for something in the map.

 

[-Kobas-]

Maybe but 5 sec can be enough time!