i keep getting this error:
00:00:00.00 WARNING: Message handling stack has reached maximum depth. All messages beyond this depth are ignored. Unexpected results may occur. x22
i have turned triggers off in groups... run a test (get error) turn the ones i turned off back on and them move on to the next group of triggers.
Lordabyss suggested that i turn them all off at the same time (run the test) and see if i still get the errors. (yea that didnt work)
I would suggest to delete actor objects in groups, just like you did with triggers. Also, did you run the game with the debugger window yet? Sometimes it provides more useful information than the ingame messages.
what do you mean... how do i find those. Kueken i tried to take all my actor our of actor groups but it still gave me the error... i selected all my doodad and ungrounded them. still got error
what do you mean... how do i find those. Kueken i tried to take all my actor our of actor groups but it still gave me the error... i selected all my doodad and ungrounded them. still got error
The cause of the warning for me was a specific unit, so you want to find out which unit is causing the problem.
Turn off triggers that create units or remove units that spawn initially and see if the message goes away.
In my case, I had a trigger that created a unit which caused the messages to pop up. It was easy for me to pinpoint since the message popped up every time the actor for the unit did the "Attack" animation.
From what I can tell, this is mostly caused by some actor messages creating some kind of infinite loop (had this issue, when using some timers in actors and did not care about their names enough)
i keep getting this error: 00:00:00.00 WARNING: Message handling stack has reached maximum depth. All messages beyond this depth are ignored. Unexpected results may occur. x22
i have turned triggers off in groups... run a test (get error) turn the ones i turned off back on and them move on to the next group of triggers.
Lordabyss suggested that i turn them all off at the same time (run the test) and see if i still get the errors. (yea that didnt work)
Are you sure, this is trigger related? Sounds like actor messages for me...
@Kueken531: Go
uh idk what that is or how to fix it... any ideas. should i spam post this somewhere else?
I would suggest to delete actor objects in groups, just like you did with triggers. Also, did you run the game with the debugger window yet? Sometimes it provides more useful information than the ingame messages.
Definitely look at your actor events/messages, I had the same problem and fixed it after cleaning them up.
Tool Time.
EDIT: Nevermind, I misread your post title as "Anybody know what time it is?"
Oh, well.
Rkmx52
what do you mean... how do i find those. Kueken i tried to take all my actor our of actor groups but it still gave me the error... i selected all my doodad and ungrounded them. still got error
Encountered this problem as well. Any ideas?
Whatever you do, wholeheartedly, moment by heartfelt moment, becomes a tool for the expression of your very soul.
The cause of the warning for me was a specific unit, so you want to find out which unit is causing the problem. Turn off triggers that create units or remove units that spawn initially and see if the message goes away.
In my case, I had a trigger that created a unit which caused the messages to pop up. It was easy for me to pinpoint since the message popped up every time the actor for the unit did the "Attack" animation.
WARNING: Message handling stack has reached maximum depth. All messages beyond this depth are ignored. Unexpected results may occur.
That's what the debug window says.
Whatever you do, wholeheartedly, moment by heartfelt moment, becomes a tool for the expression of your very soul.
@GnaReffotsirk: Go
From what I can tell, this is mostly caused by some actor messages creating some kind of infinite loop (had this issue, when using some timers in actors and did not care about their names enough)
Thanks, kueken.
Man, I've got lots of actors on here. But no timers though.
Strange that this wasn't here before the patch.
Whatever you do, wholeheartedly, moment by heartfelt moment, becomes a tool for the expression of your very soul.
The patch did just include new error messages for test mode; the errors were there before the patch, but you had no way of noticing them.
Also the error messages appear only, when testing the game. So if you don't care, just publish and they should disappear.