Running into a weird issue. Partway through testing my map it seems like triggers just stop working altogether. To test this, I made a trigger that simply displays a message when I type "Q." Even this trigger gets disabled and stops returning my debug text when I test.
It doesn't always happen, but when it does it's obviously gamebreaking. Any idea what causes this?
Running into a weird issue. Partway through testing my map it seems like triggers just stop working altogether. To test this, I made a trigger that simply displays a message when I type "Q." Even this trigger gets disabled and stops returning my debug text when I test.
It doesn't always happen, but when it does it's obviously gamebreaking. Any idea what causes this?
execution to long maybe
Try to turn off some triggers before it load, and run your game. If your trigger work, its because your execution is to big! To fix this, put a game wait of 0.0 time into the trigger that is not working (or stop running). This will reset the execution and it should work
This can occur if you keep too many trigger threads alive. SC2 limits you to a finite number of trigger threads at any given time. If a trigger thread calls a blocking native (eg the Wait action) then it will persist between deterministic frames, possibly forever (Wait with a very long timeout). If enough trigger threads block in such a way it will eventually hit the SC2 trigger thread limit after which no further trigger threads can be created. Since no further trigger threads can be created, no further events can be responded to and it may appear all triggers stop working. When this happens a clear error is usually printed informing you the thread limit has been reached so the event could not be responded to.
Without the map it is impossible to determine the exact cause. If you would like help finding and fixing the problem it might be a good idea to post the map.
Running into a weird issue. Partway through testing my map it seems like triggers just stop working altogether. To test this, I made a trigger that simply displays a message when I type "Q." Even this trigger gets disabled and stops returning my debug text when I test.
It doesn't always happen, but when it does it's obviously gamebreaking. Any idea what causes this?
<Click Here> To See My Epic Single Player Campaign (LifeForceCampaign.com)
execution to long maybe
Try to turn off some triggers before it load, and run your game. If your trigger work, its because your execution is to big! To fix this, put a game wait of 0.0 time into the trigger that is not working (or stop running). This will reset the execution and it should work
egod
there are always error messages when something like this happens. i don't believe you have none.
When the exicution is to large no error message. Everything just stop so it might be the problem
This can occur if you keep too many trigger threads alive. SC2 limits you to a finite number of trigger threads at any given time. If a trigger thread calls a blocking native (eg the Wait action) then it will persist between deterministic frames, possibly forever (Wait with a very long timeout). If enough trigger threads block in such a way it will eventually hit the SC2 trigger thread limit after which no further trigger threads can be created. Since no further trigger threads can be created, no further events can be responded to and it may appear all triggers stop working. When this happens a clear error is usually printed informing you the thread limit has been reached so the event could not be responded to.
Without the map it is impossible to determine the exact cause. If you would like help finding and fixing the problem it might be a good idea to post the map.
@Bilxor: Go
You might want to test with the debugging windows open and keep an eye on the thread tab to see if the problem comes from there.
Working on projects: