roaaaarrrr
New Member
- Reaction score
- 33
I have seen about a post a day about game crashes, and nobody seems to know how to utilize the crash logs to help themselves. So I figured I would write a quick tutorial. I don't know everything about them, but if you are just trying to figure out what ability/item/unit is causing the crash, this almost always works. So here we go....
_________________________________________________________________
When your game crashes, there will be two files saved automatically by Warcraft. These will be in your default Warcraft directory under the Error folder. (C:\Program Files\Warcraft III\Errors). One file will be saved with a .txt extension, and the other will be saved with a .dmp extension. Focus on the .txt file. Each file will have the date and time as the name, so open the most recent file.
When you open the file there will be a ton of info, but you can ignore most of it. What you should focus on is the last section - "Memory Dump". It will look something like this
When you first look at it, it looks like a complete mess. But focus on the last column on the right. There is one sequence of numbers and letters that continue to repeat itself. This is the rawcode of whatever caused the crash. Sometimes WC will invert this code, and sometimes it will be in the correct order. In this example, you see over and over the string "660A" and "A066". So this is the info you were looking for from the crash.
Now that you have that rawcode, you can identify what is causing the crash. If you don't know how to check a rawcode, go into the editor and press "ctrl+d". Then press "ctrl+f" to search.
Obviously this guide won't solve every crash, but this little strategy has helped me fix innumerable problems while making maps, so I thought I would pass it on.
_________________________________________________________________
When your game crashes, there will be two files saved automatically by Warcraft. These will be in your default Warcraft directory under the Error folder. (C:\Program Files\Warcraft III\Errors). One file will be saved with a .txt extension, and the other will be saved with a .dmp extension. Focus on the .txt file. Each file will have the date and time as the name, so open the most recent file.
When you open the file there will be a ton of info, but you can ignore most of it. What you should focus on is the last section - "Memory Dump". It will look something like this
When you first look at it, it looks like a complete mess. But focus on the last column on the right. There is one sequence of numbers and letters that continue to repeat itself. This is the rawcode of whatever caused the crash. Sometimes WC will invert this code, and sometimes it will be in the correct order. In this example, you see over and over the string "660A" and "A066". So this is the info you were looking for from the crash.
Now that you have that rawcode, you can identify what is causing the crash. If you don't know how to check a rawcode, go into the editor and press "ctrl+d". Then press "ctrl+f" to search.
- If your rawcode started with an 'A' it will be in the ability editor.
- If your rawcode started with a 'h', 'o', 'u', 'e', or 'n', it is a unit (Human, Orc, Undead, Night Elf, or Neutral - respectively)
- If your rawcode starts with a 'B' it is a Buff.
- If your rawcode starts with an 'R' it is an Upgrade.
Obviously this guide won't solve every crash, but this little strategy has helped me fix innumerable problems while making maps, so I thought I would pass it on.
