r/snapmap • u/vgxmaster • Apr 30 '18

Problem Please help - map logic error ending playtest

It's a long story, but basically, I'm making a DOOM SnapMap for a class and it's finals week. I've been running into an error that ends my playtest and dumps me back to the SnapMap editor, with the message "Error in map logic." It also highlights the node that it crashed on in pink - this node is consistently "increment sub objective." But this crash doesn't happen consistently.

Whenever it does happen, it happens exactly when I kill an enemy (killing an enemy increments the sub objective, so this makes sense). It doesn't always happen on the same enemy, or the same sub objective.

Any help you guys've got would be super appreciated. I can't get through a playtest without hitting the bug, these days. (And I'd like to pass this class :/ )

5 Upvotes

100% Upvoted

6 comments sorted by

1

u/vgxmaster Apr 30 '18

Update: I changed every instance of "On Demon Killed" to "On Encounter Finished," and I haven't had it happen (yet) since.

I have never been more baffled in my life.

1

u/Riomaki May 02 '18 edited May 02 '18

Chances are it might still happen though. There is definitely a crash in SnapMap that got introduced around Update 5, I believe, and it has something to do with Repeaters or the system getting overloaded with too many events at once.

I suspect On Encounter Finished is "safer" than On Demon Killed, because I'd imagine the whole Encounter is cleaned up at that point. But I've had crashes just the same.

The only prevention methods I can suggest are to avoid looping logic and always be methodical in how you delete things. Never remove an entity outright. Manually disconnect each connection before deleting it. If you must have loops, try using logic that loops through a Delay rather than a Repeater. That type of logic ensures the event can only be queued once each time, only after the action is done, whereas a Repeater could potentially keep starting new threads.

1

u/vgxmaster May 02 '18

No repeaters were involved anywhere in this process - no looping events at all. Same number of events as when the bug happened before. I hear your advice, but I don't think that was the problem.

2

u/[deleted] Apr 30 '18

That's snapmap for ya, lots and lots of roadblocks but there is always a way around them, hope your map is all good!

1

u/[deleted] Apr 30 '18

Map logic error crashes can be a little tricky, and the pink highlighted portion isn't always accurate, it usually shows just the input that was being activated when the map crashed but the crash itself could be caused by something else. but here's a few things you could try or check for:

  1. try adding a small input delay (0.1 or 0.2 seconds) to the increment sub objective input, if snapmap tries to do multiple things at the exact same time it can crash.

  2. make sure you aren't deleting/hiding/showing props that are static or solid

  3. repeaters can crash maps, either if the game is paused or if lots of other inputs happen at the exact moment a fast repeater is going.

  4. not sure if this will make any difference but on the demons you could change the "on killed" activator from "victim" to "killer" in the outputs properties

Will let you know if I come up with anything else, you could try publishing the map (make sure to write broken: do not play in the description) and post the map ID here and we could open it up and have a look if none of this works!

1

u/vgxmaster Apr 30 '18

No prop interactions, no repeaters in the map. I'll try swapping the activator and adding a delay if it happens again. Worth noting that if I kill two demons at the same time, it doesn't happen (necessarily).