• Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.

[Crash] Fatal Error

Status
Not open for further replies.
Level 4
Joined
Aug 22, 2014
Messages
54
So I tested out my up to date map file and it has a fatal error upon starting the game, right after loading is done. I opened one up from last week and it worked fine. All I did was upload a bunch of icons and do some map edits- not sure what is causing the error... Here's a screenshot.

d2xU89U.jpg
 
The first step to debugging startup fatal errors is to make a backup. This part is crucial. You'll want one version in its current state, and one version for you to delete things freely to identify the error. Next:

Disable all the triggers and test the map. If it loads, then the issue is with triggers (if that is the case, then just look at all your map initialization triggers and find out which one is the culprit).

If the trigger disabling doesn't work, then delete all imports. Test the map and see if it still crashes. If it doesn't, then that means it is an import that is causing the crash.

If that doesn't work, delete all the object editor objects and do the same test.
 
Level 4
Joined
Aug 22, 2014
Messages
54
The first step to debugging startup fatal errors is to make a backup. This part is crucial. You'll want one version in its current state, and one version for you to delete things freely to identify the error. Next:

Disable all the triggers and test the map. If it loads, then the issue is with triggers (if that is the case, then just look at all your map initialization triggers and find out which one is the culprit).

If the trigger disabling doesn't work, then delete all imports. Test the map and see if it still crashes. If it doesn't, then that means it is an import that is causing the crash.

If that doesn't work, delete all the object editor objects and do the same test.

Ok, made a copy of the map, took out all the triggers, imports, and all the recent object editor data- still have the fatal error :(

I might just take the map backup from a week cut my losses... dam but this could happen again though- so, I still wanna try and fix it.
 
Status
Not open for further replies.
Top