Need pro help to trigger issues

[DL.PIGGY]

Hi. Ive been mapping for a few years now on my map and i think it has reached a breaking point of sorts. Having around 990 triggers (GUI, the whole map is in GUI) and about 1050 variables has caused my map initialisation to fail. Having tested it along with help and advice from phyrex1an, Ive narrowed the problem down to having too many, triggers/variables/lines of codes that has somehow caused the map initialisation triggers to break and fail. What phyrex1an has advised me was to change my map initialisation triggers to 'elapsed game time = 0.00s'. While this has worked, it has effectively caused a huge lag of about 5 seconds when the game starts. This being on my i5 computer would mean alot worse for some other comps when hosted online. Also the first 15 seconds is for gamemode typing and this would put a huge problem for my map.
My question is does anyone have any known solutions to this issue?

 

[Laiev]

What type of things you use in init/elapse 0?

if is variable to skills, use the variables in the spell when they are casted..

if are modes and etc, use when player use mode and etc...

probably lots of things that you can remove from map initializer...

also you protect the map?

Widgetizer (or something like this, don't remember the right name) + optimizer of vexorian and if need use the slk too

 

[DL.PIGGY]

Yap widgetizer and all.

I initialise unit arrays (hero map), their icons array (multiboard) and stuff. Everything ive initialised there are more or less for intialisation purposes. but yes i get your point. i should remove as much unwated stuff as possible.

 

[Never_Quit]

Sounds like memory leaks. Mind showing a few triggers?

Also, certain things do not intialize properly in test runs, while they work properly on bnet because of timing issues.

 

[Bogrim]

Spread out the map initalization triggers some more. Try and prioritize which triggers that has to be run right off the bat and which triggers that can wait until later. If you have settings for specific heroes, wait with setting them until that hero is chosen.

 

[Sui-cookie]

i get bad lag problems when i have 30+ on 0.00 triggers :/ what i do is set up a quick "initializing" cinematic in the very beginning, and have only one trigger run on time - 0.00 and have it go through and turn on all other triggers, one by one :/ this helps in game lag, as well as the initial "umph" of starting the map... if all else fails, try it.

 

[DuelPlayer]

Use warcraft optimizer if dont have
And just let the first 15 seconds to for them to load and laggers to settle like ID <<< i suppose you know


Offtopic - Did you see how i reply to your visitor message? If not, here

 

[Exide]

Sounds like your map has grown too big for Wc3 to handle.
Your best shot at fixing it would be to convert all your triggers to JASS and optimize them.
You can also remove tons of pre-placed stuff and add them via triggers at a later time.

Keep some triggers at Map Init and some at 0.0 sec elapsed. (Like 50-50)

 

[DL.PIGGY]

Sounds like your map has grown too big for Wc3 to handle.
Your best shot at fixing it would be to convert all your triggers to JASS and optimize them.
You can also remove tons of pre-placed stuff and add them via triggers at a later time.

Keep some triggers at Map Init and some at 0.0 sec elapsed. (Like 50-50)

This seems like the best explanation to my problem. But as of right now all my map initialization triggers have stopped working and I have converted all of them to 0.00 seconds.

 

[Exide]

This seems like the best explanation to my problem. But as of right now all my map initialization triggers have stopped working and I have converted all of them to 0.00 seconds.

So change the event of some of them back to Map init.
You can also merge a couple of triggers into one.