View Full Version : Problem With Testing
BlackKnightTGS
07-03-2011, 04:55 PM
Okay, so I was making a map (normal World Editor), and it was running fine yesterday. I pressed "Test Map" today and I got an error :S
http://www.hiveworkshop.com/forums/members/174393-albums4876-picture48327.jpg
^this is the error I get.
What's wrong?
Dr Super Good
07-03-2011, 11:07 PM
^this is the error I get.
The subject referenced by "this" appears to be missing.
Errors with WE are usually caused by eithor a JASS scripting error, eg making a syntax error, or trying to use vJASS abilities or systems without using JASShelper to precompile it to normal jass (done usualy JNGP usually).
BlackKnightTGS
07-04-2011, 02:24 AM
Missing? Well, this (http://www.hiveworkshop.com/forums/members/174393-albums4876-picture48327.jpg) is the error that I get. (hope it can be seen now)
And well, I made an ability trigger (wasn't JASS or vJASS, GUI), but even when I deleted it I still get that message when trying to test.
Dr Super Good
07-04-2011, 04:15 AM
The image of the error appears to be curropt for me (does not load).
Is it a syntax error or some other kind of error?
BlackKnightTGS
07-04-2011, 02:50 PM
"This application has encountered a critical error:
FATAL ERROR!:
Program: e:\games\warcraft iii\War3.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:150348BC
The instruction at '0x150348BC' referenced memory at '0x00000000'
The memory could not be 'read'.
Press OK to terminate the application."
I tried exporting and importing its data to another map (without the specific spell trigger), it works well on it...
Dr Super Good
07-04-2011, 03:20 PM
This sort of error is caused by the game loading invalid data. It could be terrain, objects or even gamplay constants / gameplay interface settings. If a custom load screen is used, the image may even be curropt. For that mater, any import being curropt has been known to do such things. Badly written triggers can cause this sort of error as well such as initializing a global quest to a quest object.
Firstly try removing all imports from the map. Then try rolling back each settings 1 by 1 until you basically get a blank unedited map that is playable.
The key to not losing the map's content is to save a backup of it in a non working state. Then break it piece by piece until it is working (and you identify what was causing the error). Then you can go back to your broken backup copy of the map and only remove or fix the piece that is broken so all other content is not lost.
BlackKnightTGS
07-05-2011, 02:54 AM
Alright, will do. Thanks for the help!
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.
Search Engine Optimization by
vBSEO 3.5.1 PL2