- Joined
- Jun 9, 2008
- Messages
- 308
I dunno. It's a strange thing I don't really understand right now.
I am making good progress on an elaborate 480x480 map, but I am worried I might lose it.
I imported triggers from earlier versions of the project, on other maps. Some of them work no problem, but others, even after I adapt them, crash the map when I test it, with an error message (something along the lines of "runs out of memory") or the map loads and after a few seconds it goes, in a word, bonkers - worker units become unable to harvest, and may even pop in and out of existence at random positions. Deleting or disabling the last trigger I worked on usually restores the map to functionality.
A key problem seems to be map initialization triggers - anything other than the minimum standard trigger kills the map.
One work-around I found is delay a bunch of triggers, have them start 5 seconds after intilialization. That, the map can usually handle. But yesterday I had to delete one trigger completely.
Thing is, I am a bit worried because right now I am fixing things "blind", not really knowing what's going on and going by trial and error, not knowing why the things that seem to be helping are helping. I only work with what I think are "simple" GUI triggers that worked fine on their original maps.
It slways seems to be linked to the trigger editor - another weird crash I got was when I tried to replace a region variable by selecting a new region on the map, and I got another "ran out of memory!!" scream in the world editor itself, not even a test run.
(When I repeated the same action after reloading the map, the editor didn't complain.)
So my question is, any ideas for trouble shooting, or what the core issue may be?
Could it be that the map itself is corrupt in some way, and how would one find out?
I am making good progress on an elaborate 480x480 map, but I am worried I might lose it.
I imported triggers from earlier versions of the project, on other maps. Some of them work no problem, but others, even after I adapt them, crash the map when I test it, with an error message (something along the lines of "runs out of memory") or the map loads and after a few seconds it goes, in a word, bonkers - worker units become unable to harvest, and may even pop in and out of existence at random positions. Deleting or disabling the last trigger I worked on usually restores the map to functionality.
A key problem seems to be map initialization triggers - anything other than the minimum standard trigger kills the map.
One work-around I found is delay a bunch of triggers, have them start 5 seconds after intilialization. That, the map can usually handle. But yesterday I had to delete one trigger completely.
Thing is, I am a bit worried because right now I am fixing things "blind", not really knowing what's going on and going by trial and error, not knowing why the things that seem to be helping are helping. I only work with what I think are "simple" GUI triggers that worked fine on their original maps.
It slways seems to be linked to the trigger editor - another weird crash I got was when I tried to replace a region variable by selecting a new region on the map, and I got another "ran out of memory!!" scream in the world editor itself, not even a test run.
(When I repeated the same action after reloading the map, the editor didn't complain.)
So my question is, any ideas for trouble shooting, or what the core issue may be?
Could it be that the map itself is corrupt in some way, and how would one find out?
Last edited: