Modcraft - The community dedicated to quality WoW modding!
Content creation => Level Design => Topic started by: Allifeur on June 06, 2014, 09:42:45 pm
-
Hello, my question might look weird at first, but let me explain :
I have a weird bug on two of my adts. There are a some M2 that make the game crash if they get into the player's visual field. Those M2 have no distinctive traits on Noggit, which means the only way to know which ones are bugged is by testing ingame and making some guess.
(http://img15.hostingpics.net/pics/932831BugExpliqu.jpg)
If I copy this bugged M2 and delet the original, it doesn't bug anymore. Though the bug switchs to another M2 with no obvious reason, and I can't solve it.
(http://img15.hostingpics.net/pics/621362BugExpliqu2.jpg)
I imagine that the problem is related to some IDs, but I don't really have so many clues about where it will appear next; and no idea why it appeared in the first place.
So that's why I would like to ask if you know something that can reload every single M2 of the map in order to destroy definitely the bug; or if you have a better idea.
I already tried to solve my problem with cryect tools but it didn't worked.
-
I have the same problem on one of my maps my rabbit
Can't figure it out yet...but the problem is pretty mutch the same
If I manage to fix it I will contact you, I expect you to do the same
-
Loadinfo fileinfo
Cut out all m2s. Then add the first half again. Test ingame. If crash cut from the rest again the half. If not do it with the other half.
So you get every step clother to the problem m2.
-
Loadinfo fileinfo
Cut out all m2s. Then add the first half again. Test ingame. If crash cut from the rest again the half. If not do it with the other half.
So you get every step clother to the problem m2.
The thing is that there are several bugged M2s, and that deleting one is useless since the bug switchs on another M2.
-
Then kill all m2s.
Test adt ingame.
Add m2 list
Test ingame
If error appears delete all amd add them one by one.
Kf you have full list in start with spawns. Doing the same.
-
Are the crashing M2s custom or copied from post-3.3.5 clients? If such M2s are used, try having a testing area for them, it'll be some work, but just create some ADTs to test them ingame.
What's the error WoW gives?
I personally haven't had the issue with M2s yet, I did have issues with WMOs + 3.3.5->4.0.6 converted ADTs.
-
There are some custom and post-3.3.5a imported M2s, nevertheless those do not seem to be related to the WoW errors : There are several exemplaries of them on the ADT that are working perfectly well.
The error is :
This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal Exception
Program: C:UsersMarcDesktopWorld of Warcraft - Copie (2)Shadow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007B31F8
The instruction at "0x007B31F8" referenced memory at "0x00000010".
The memory could not be "read".
-
viewtopic.php?f=12&t=2971 (http://modcraft.io/viewtopic.php?f=12&t=2971" onclick="window.open(this.href);return false;)
(http://4.bp.blogspot.com/-44GZwoRG_mE/UTOoov9-kHI/AAAAAAAAABA/u74ABm-DFhM/s1600/double_facepalm.jpg)
Felt like it
-
I don't really understand : I didn't put any grounds effects at all yet, and the bug is linked to M2s. Moreover all the chunks have 4 textures. So I hardly see why I get this error.
Edit : Oh, there is a not-bugged chunk that has a shollazar texture for no reason. I'll try to change it, maybe the problem is related to it. Though it's weird.
Edit² : Ok. Changing it solved the whole problem. There were some weird corruption there that I still don't understand. The bugged M2s were only a consequence of it.
I give you my thanks for making me look at textures. I feel kind of ashamed now.
-
I don't really understand : I didn't put any grounds effects at all yet, and the bug is linked to M2s. Moreover all the chunks have 4 textures. So I hardly see why I get this error.
Edit : Oh, there is a not-bugged chunk that has a shollazar texture for no reason. I'll try to change it, maybe the problem is related to it. Though it's weird.
Edit² : Ok. Changing it solved the whole problem. There were some weird corruption there that I still don't understand. The bugged M2s were only a consequence of it.
I give you my thanks for making me look at textures. I feel kind of ashamed now.
If error #132 occurs, check the thread. Take it as opportunity for the future.