Forum > Miscellaneous

ERROR #132 - An actual way to fix it. (Build 12340)

<< < (2/8) > >>

schlumpf:
Seems to be related to WDT. Try redoing that. (At least, there is CBarrier code nearby.)

Ayos:
So, i recreated the whole map again with a different adt template from this site and still crashing, but this time from this:

ERROR #132 (0x85100084) Fatal Exception
Program:   D:JátékokTauri WoWWow.exe
Exception:   0xC0000005 (ACCESS_VIOLATION) at 0023:007B4D14

The instruction at "0x007B4D14" referenced memory at "0x00000071".
The memory could not be "read".

I hope this is not related to the fact that i use a full 64x64 map... this size is necessary for my project.
Any idea?

schlumpf:
That's pretty close to the old values, thus in the same function, thus most likely in the same filetype. Did you try creating the files step by step so that you see, when it starts crashing? (i.e. create the wdt + 1 adt first. See if it crashes. Expand the WDT, see if it crashes, ..)

MR. Farrare:
when i get to the end of my map i get only at the end and up in my map is ok only  at the end maybe because my map is too big 64 64 and ye i used add water on the last off my map and i picked ocean plz help and no wmo there all deleted and if there maybe and wmo then its unseen wmo plz tell me how to find it and select it and delete it srry for my english im trying to get better
ERROR #132 (0x85100084) Fatal Exception
Program:   I:wow woltk repackseus wowWorld of Warcraft 3.3.5a (no install)wow.exe
Exception:   0xC0000005 (ACCESS_VIOLATION) at 0023:007B4D61

The instruction at "0x007B4D61" referenced memory at "0x00000071".
The memory could not be "read".

Ayos:
My problem was almost the same as yours. The client always crashed when i used my 64x64 map, but when i made a 63x63 version (still dont know why), the crashes disappaered. So just try to cut the outter lines of your map.

Navigation

[0] Message Index

[#] Next page

[*] Previous page