I'm not sure what causes it, but I think it's when too many units are made, or too many actors (I noticed on a map with water ripples is the worst) it causes all triggers on the map to not work. It goes on and off, likely because units have died off. Anybody know about this bug and how to prevent the triggers from shutting down?
I won't say "bug" but engine limits. I don't know why you would do that.
Enable the debugger in editor config and look at it on runtime. You might find precious information like how many times a specific thread is checked and/or executed.
Another thing, if you did an overflow, that means you need reached the maximum number of a thread. Pay attention to wait some time before creating new threads of a kind.
The only problem with trying to use the debugger is the glitch only appears on some random bnet games, and maybe 1 out of 10 games. I would have to run games in the editor with the ai fighting itself, for dozens of hours, hoping to find it, not sure what to look for, with no promise the editor games will replicate the problem, but I would also have to be playing to know when the triggers went off before they go back on again. This is impractical. I wish there was a way to get an error dump after a game on bnet.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I'm not sure what causes it, but I think it's when too many units are made, or too many actors (I noticed on a map with water ripples is the worst) it causes all triggers on the map to not work. It goes on and off, likely because units have died off. Anybody know about this bug and how to prevent the triggers from shutting down?
Hello.
I won't say "bug" but engine limits. I don't know why you would do that.
Enable the debugger in editor config and look at it on runtime. You might find precious information like how many times a specific thread is checked and/or executed.
Another thing, if you did an overflow, that means you need reached the maximum number of a thread. Pay attention to wait some time before creating new threads of a kind.
In reply to Phosphatidylinositol_:
The only problem with trying to use the debugger is the glitch only appears on some random bnet games, and maybe 1 out of 10 games. I would have to run games in the editor with the ai fighting itself, for dozens of hours, hoping to find it, not sure what to look for, with no promise the editor games will replicate the problem, but I would also have to be playing to know when the triggers went off before they go back on again. This is impractical. I wish there was a way to get an error dump after a game on bnet.