Preload Abilities

[neo_sluf]

So i am confuse what do you preload from the abilities?..


Dummy's used?.. like SFX Dummies?..

Variables?.. (How do i preload a variable in your ability! what the heck)
Like how do you preload TempPoint?.. or do i need to preload variables?..

What type of variables do you need to preload..

Also about the FPS again..

I played my map when everyone cast a spell it drops up to 10 fps. But after it, it will rise up to 30 fps or even 40 fps. So do you think my map leaks or its just Special Effects lag?.. cause if it leaks it will cause a Fatal Error but instead it goes back to normal, I am right?..

 

[Doomlord]

You preload abilities that you will add to a unit (for example a +armor ability). Because there is always an inevitable lag upon first time an ability is added to a unit, we preload it to avoid it ruining the map's gameplay.

The framerate drop in your map may be caused by the spell being coded ineffectively or too many effects are used or the loop interval is too small etc. That is why it only lags when that flawed code is executed.

Leaks won't cause a fatal error unless the computer is too weak that it can't handle that much memory leaks (which is unlikely these days).

 

[Xonok]

Leaks won't cause a fatal error unless the computer is too weak that it can't handle that much memory leaks (which is unlikely these days).

Actually that error can come quite easily, since warcraft is limited to 2GB of memory.

 

[Doomlord]

Actually that error can come quite easily, since warcraft is limited to 2GB of memory.

=O

A leak is only a few bytes, I wonder how badly the code must be to reach that limit.

Anyhow, thanks for the clarification

 

[neo_sluf]

So if my spell is not MUI or MPI but all the leaks are cleaned is that INEFFECIENT CODING?..

 

[Xonok]

So if my spell is not MUI or MPI but all the leaks are cleaned is that INEFFECIENT CODING?..

If your spell is not MUI and MPI, then that alone won't break it.
What will break it is if multiple units cast it. Then it has a high chance to leak or simply work wrong.

 

[Doomlord]

So if my spell is not MUI or MPI but all the leaks are cleaned is that INEFFECIENT CODING?..

Efficient coding is more than just being leakfree. Efficient coding is about choosing what is the best approach for an issue. For example, GUI is inefficient comparing to JASS so coding in GUI is itself being inefficient. Or like a certain guy here always mention, repeated function calls (Thou shalt store anything you used twice or more into a variable) are inefficient. Indexing non-dynamically is also inefficient, etc.

But don't mind it too much though. It is your map after all

 

[Malhorne]

I though we can preload abilities like this :

set bj_lastCreatedUnit = CreateUnit( Player(15), 'h000', 0, 0, 0 )
call UnitAddAbility( bj_lastCreatedUnit, SPELL_ID )
call KillUnit( bj_lastCreatedUnit )

 

[deathismyfriend]

I though we can preload abilities like this :

set bj_lastCreatedUnit = CreateUnit( Player(15), 'h000', 0, 0, 0 )
call UnitAddAbility( bj_lastCreatedUnit, SPELL_ID )
call KillUnit( bj_lastCreatedUnit )

yes u can preload abilities by adding it to a unit.

@Doomlord
i guess u were quoting me ? lol

 

[Malhorne]

Ok

 

[Vinz]

@Doomlord
i guess u were quoting me ? lol

Yep, you are sure popular.

OT: It is not the Vars that are preloaded, but the spell effects.

 

[deathismyfriend]

Yep, you are sure popular.

OT: It is not the Vars that are preloaded, but the spell effects.

not sure if that was sarcastic haha ?

also nice thing about clarifying but its actually the model files that are preloaded.

 

[Doomlord]

@Doomlord
i guess u were quoting me ? lol

Well yes indeed I do ^^

Just a thing.

I see you post this a lot. I might not be completely true. I'd rather say "thrice or more" if a clear limit would have to be set.

For example in jass, you would have to declare a local variable and then possibly null it, so the speed difference decreases.

In GUI that could result in using more variables than needed to give one example.

 

[deathismyfriend]

Just a thing.

ya i noticed that message from maker b4 but i got told by nes that actually twice is already more work for the pc than setting it to a variable.