HomeUser Control Panel (unavailable in archive)ForumsTutorialsArt GalleryResourcesMaps

what does this mean? please help!

06-16-2003, 02:12 PM#1
Stormwraith
im making a map, and when i go to test it it loads fine and says 'push any button to continue' and i do. it then exits the game and brings up a fatal error screen. the screen says this:

------------------------------------------------------------------------------------
War3

This application has encountered a critical error:
Fatal Error!

Program: C:\Warcraft III\War3.exe
Exception: 0x0000005 [access_violation] at 0167:6F27A03D

The instruction at '0X6f27A03D' referenced memory at '0X0850FC20'

The memory could not be 'written'.
Press OK to terminate this application.
-----------------------------------------------------------------------------------

thats what the error screen said, this map obviously is important to me, otherwise i wouldnt put so much effort into finding how to fix it. i'm pretty sure that the problem isnt with warcraft because i've tested 2 other maps and neither of them have had problems. attached is the error log. hopefuly some one can help me out. thanks for any help
06-16-2003, 04:29 PM#2
Neo_Genesis
I actualy had this problem not too long ago.

For me it was any map I tried to run with TFT that I had made in the orgional WE for WC3.

The fatal error I kept getting was cuased by the units Path Map being blank. I dont think WC3 likes that field to be blank. If you have a unit that has a blank Path Map change it to 4x4 solid and that should fix your problem.

Hope that helps

Neo_Genesis
06-16-2003, 04:49 PM#3
Stormwraith
i deleted every custom unit, and reset it to default. didn't help either. i was messing around with it, and i made it so cinematic mode turned on at map initiation, waited 2 seconds and then turned off. the map loaded and worked fine for those 2 seconds. as soon as cinematic move turned off, the game crashed. i appreciate the help tho, ill keep trying.
06-16-2003, 09:36 PM#4
Ari
It sounds like it could be a trigger issue. Ask the question "what happens imediately after cinematic mode turns off?" In the past, I've had crashes like this when I had a trigger refer to a variable that hadn't been assigned a value. Certain infinite loops I did also crashed like that.