Modcraft - The community dedicated to quality WoW modding!
Featured => Noggit => Topic started by: Ascathos on June 05, 2012, 04:48:01 pm
-
ERROR #132 (0x85100084) Fatal Exception
Program: D:GamesworldofwarcraftWow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007B31F8
The instruction at "0x007B31F8" referenced memory at "0x00000010".
The memory could not be "read".
I try to understand this error, for the simple reason that it comes with many ADT no matter if I fixed it's doodads with the fixer, removed it's doodads with the doodad changer or leave it as it is.
To see if this is the case, I tried the following:
I used the "raw" ADT:
->
ERROR #132 (0x85100084) Fatal Exception
Program: D:GamesworldofwarcraftWow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007B31F8
The instruction at "0x007B31F8" referenced memory at "0x00000010".
The memory could not be "read".
Fixing the ADT with the "Doodad Fix" on here:
->
ERROR #132 (0x85100084) Fatal Exception
Program: D:GamesworldofwarcraftWow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007B31F8
The instruction at "0x007B31F8" referenced memory at "0x00000010".
The memory could not be "read".
Removing all Doodads from the ADT without Fix:
->
ERROR #132 (0x85100084) Fatal Exception
Program: D:GamesworldofwarcraftWow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007B31F8
The instruction at "0x007B31F8" referenced memory at "0x00000010".
The memory could not be "read".
ADT with all Doodads removed with the "doodad adder" and with the fix applied.
->
ERROR #132 (0x85100084) Fatal Exception
Program: D:GamesworldofwarcraftWow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007B31F8
The instruction at "0x007B31F8" referenced memory at "0x00000010".
The memory could not be "read".
So basically, it can not be related to the doodads - it's always related to something else - can it ? Unfortunately, and that is simply my initial issue - this error is somehow "always" appearing. From previous edits, I know that the exact same error is applying to ADTs which do not have the doodad fix ran yet - after I am running it though, they work completely fine.
So, my question would be - what is it ?
It says that it can not access an area or a part from the ADT, which leads to a corrupted, missing or broken part, but how can it show such an error if the exact same error applies to "somehow working" ADTs after doodad changes ?
Additional: I use the Wow.exe with the md5 change, which doesn't require a new MPQ but loads from the immediate world folder.
I have no Custom MPQ or additional custom changes applied, so I am solely trying to run the "ADT" changes.
Same applies for the times I edited with Noggit; I use the newest SDL version.
Noggit is applied to a clean 3.3.5a version with the reggedit always pointing to the folder (checked it several times). No config file is ran.
-
ERROR #132 (0x85100084) Fatal Exception
Program: D:GamesworldofwarcraftWow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007B31F8
Does not matter.
The memory could not be "read".
Does not matter.
Fixing the ADT with the "Doodad Fix" on here:
Does not matter.
Removing all Doodads from the ADT without Fix:
Does not matter.
ADT with all Doodads removed with the "doodad adder" and with the fix applied.
Does not matter.
can it ?
Sure.
It says that it can not access an area or a part from the ADT
It does not.
Additional: I use the Wow.exe with the md5 change, which doesn't require a new MPQ but loads from the immediate world folder.
Does not matter.
Noggit is applied to a clean 3.3.5a version with the reggedit always pointing to the folder (checked it several times). No config file is ran.
Does not matter.
The instruction at "0x007B31F8" referenced memory at "0x00000010".
Matters. The only thing one can tell you, is that somewhere in the file, there is a pointer that should be set but is not. This might be anything, maybe MHDR or MCIN or MCNK, anything which has pointers or offsets.
The only way to find this out is investigating the ADT file in detail manually or finding out what "0x007B31F8" does.
-
This issue is caused by the ADT referencing a detail doodad ID that is not given in the DBC, either by saving incorrectly or not editing the DBC correctly.
This can be fixed by adding an entry to the DBC for all IDs or by removing the id from the ADT.
-
... I apologize for being so persistent and I feel kinda bad about it. My logic got me to the point that I either have to edit each detailtextureid (I use the 010 editor templates) or I just have to edit the ofsMTEX. However, it seems kind of illogical to do the last one, so I'm at a stuck point that I might have to edit each texture ID. Am I guessing right ? I apologize for my missing experience.
-
Do you use something else on the ADTs then noggit to get this error?
I creat the ADTs with taliis and then use ONLY noggit and the allwaterWotlK CMD. And i never had any crashing adt. And I do much work on them and save hunded of times.
-
Non. I just start editing a new area with Noggit. This time, it was Brill in Tirisfal Glade. Just one sole ADT containing the whole town - I cleaned it from all the things I don't want, added my m2's and wmos on it, changed the textures (STRG+Shift + Left Click on each Chunk and placed the texture new accordingly on it) and save it (of course, saves are also inbetween :roll: ). Trying to load the ADT up results to that error at times. My friend who also works with Noggit always has the issue, which is why I'm trying to get a hold of how to fix it.
Also, considering that -1 is not an hex value, do I have to reduce the IDs by one or set it to 0 ? :3 I am not really knowledgable on the matter and I might've been doing it wrong until now.
I can upload it later if you want me to.
-
-1 equals 0xffffffff
-
The problem could be taht you edit exiting stuff. I always build new adts.
-
The problem could be taht you edit exiting stuff. I always build new adts.
That might be, but the main issue with building new adts is the implementation into existing structure. Especially considering if changes move over to multiply ADTs it gets pretty dirty in the implementation.
@schlumpf Alright, I'll give it a try again as soon as I have the ability to.
-
Ähm... for me is using noggit to build my own and new stuff and not use existing structures ;)
-
Ähm... for me is using noggit to build my own and new stuff and not use existing structures ;)
That may be true and I (for my part) do accept that Noggit is not "perfect" for every purpose, but that's why I search for solutions and consult way more experienced users for a possible solution. If it works, I'm grateful - if not, I have to look another way :)
-
Give me the map and adt cords and what you did there. I will try it also:)
-
I am editing the Azeroth_31_27.adt and I basically edited every chunk (removed the textures and re-placed them) , placed some details like WMOs and M2s, etc..
After saving, it resulted in that.
-
I can confirm a similar issue with another ADT edit;
Azeroth_31_28 and Azeroth_31_29
I did the same things, but it is still not working. The same error as above. I assume that Noggit is not properly saving these changes to the doodad things. Unfortunately, changing all the effectDetailsID doesn't seem to work either; or I did something wrong.
-
I have tested it and you areright. If i make changes there ADT dont work inside wow.
Now we must find what fchange it is :)
-
The problem are the texture stuff. If I Replace all textures with only ground layer the adt crash. Models work fine Also ground editing.
The thing here is. Why do I have to do such tests and not the guy(s) with the problem?
(http://imagr.eu/up/4fd05341ec45f3_WoWScrnShot_060712_090633.jpg)
http://imagr.eu/up/4fd05341ec45f3_WoWSc ... 090633.jpg (http://imagr.eu/up/4fd05341ec45f3_WoWScrnShot_060712_090633.jpg" onclick="window.open(this.href);return false;)
-
Texturing also work Only the last layer get wired chunklines on it.
(http://imagr.eu/up/4fd05434dc1388_WoWScrnShot_060712_091135.jpg)
http://imagr.eu/up/4fd05434dc1388_WoWSc ... 091135.jpg (http://imagr.eu/up/4fd05434dc1388_WoWScrnShot_060712_091135.jpg" onclick="window.open(this.href);return false;)
-
To start it all off, thanks Steff for the tests. I was not sure what to look for and the mistake didn't really show itself again, so I had nothing consequent to show. However, now it repeats in a weird way - maybe it helps, maybe not.
Following the more common suggestion of doing things, save old ones, Test and THEN continue, I found a new way this error is approaching;
Now, I've again been editing a Blizzard area. Textures have mostly been kept as they are. I only changed height of some parts, etc.
However, after doing some smaller changes, I became unable to go near the area with the same area. Now, from former experiences, I know that fixing doodads or removing doodads (each with the tool) might fix it, so I did - it fixed the issue. Now, the weird part begins. I go from one end of the ADT to another through the whole area and have no problems at all. However, going back along the way shows the same doodad error like before.
Make it short:
- Edited an area (Azeroth_39_34.adt - forbidden sea near Jintha'Alor)
- Added various models which worked, changed landscape, etc. - worked
- Changed some textures on the map - doesn't work.
- Fixing the doodads - works, however...
-- Moving through the adt, but coming to roughly "half" the area, it gives the same wowerror I had until now.
Also, from early tests, changing the detailID didn't have an effect - might have done it wrong, but I did change every detailID value in every chunk to -1.
EDIT:
Do you want me to apply a Bug to the tracker ?
-
If you report it, add a file before and after while changing exactly _one_ thing in between and clearly describing that thing.
-
Any progress on this error? I have the same/a similiar |:
-
Any progress on this error?
See my reply a few weeks ago.
This issue is caused by the ADT referencing a detail doodad ID that is not given in the DBC, either by saving incorrectly or not editing the DBC correctly.
This can be fixed by adding an entry to the DBC for all IDs or by removing the id from the ADT.
There is no error on noggit's side.
I have the same/a similiar |:
As this "investigation" is on some generic SIGSEGV, most likely your "similar" error is not similar at all and might be anything imaginable. Without saying how it is similar, you might as well just fart on a ladybug.
-
Sorry, o only saw the first page, didn't recognize that there is a second page..But I'll go throught it later on..