Noggit Crashes Wow (in-game)

[Drendor]

Basically, I just enter into a blizzard map through Noggit 1.2/1.3/1.4 (The version is not the problem or the solution), let's say Kalimdor, and add a M2, or .wmo or modify terrain, ground, etc. I save it, create the MPQ file and run it with the WoW Client. When I go to the place I modified, it instantly crashes my WoW client with this error:

  ERROR #132 (0x85100084) Fatal Exception
Program:   C:WoWModdingClient335aTestElseworld of Warcraft.exe
Exception:   0xC0000005 (ACCESS_VIOLATION) at 0023:007B31F8

The instruction at "0x007B31F8" referenced memory at "0x00000010".
The memory could not be "read".

I'm sure you know enough about this famous error, but the solution I found every time in the forum does NOT work for me. As you can read, with every tool I use in noggit, the blizzard map crashes in-game, even if I don't modify terrain or texture. I do not see any logic on what's happening to me. I'm also "new" in noggit, I'm sure I know more less than you guys, but I've already created a continent, and a full map with 8 ADT's and Noggit versión 1.3 never resulted on a problem to me. I recently read that version is corrupted as hell, so I changed it to 1.4, any improvement? no one. Help, please, that's all I ask for.

[Petisoo]

viewtopic.php?f=12&t=2971

/close

[Drendor]

What did I just tell you? THAT IS NOT A SOLUTION, I've already prove it. It doesn't make sense that for every single modification with noggit (any version) , even if I do not touch the TEXTURES and GROUND, the wow crashes because of that modification. I tried it, I put 4 textures in every chunk of the adt I modified with any tool.

[Skarn]

viewtopic.php?f=48&t=9113&p=45948#p45948 Here you go.

[PhilipTNG]

@Drendor, do you think maybe you can upload your adt files that is crashing?  I'm not smart enough to try to use noggit to try to re-create your error on my end. if is no problem for you, can please upload so I can look at it?  I am very curious

http://modcraft.io/viewtopic.php?f=48&t=9113&p=45948#p45948 Here you go.

So basicaly just remove all other adt's that surround the adt(s) he modified? that's not too difficult to do then, that's a simple solution if it works out for him

[Drendor]

Ok I will upload them, but it's not a great deal. Like I said before, I'm not doing anything weird, I'm just opening a map with noggit, putting some high to a ground and saving it (Or putting a m2 and saving it).

Thanks Skarn! That's the explanation I wanted , that is exactly what happens to me. I'm gonna do it

[Amaroth]

Petisoo gave you EXACTLY the same. You were just too lazy to look for solution he gave you in that sticky. Well, it lacks information that you "should" delete edited ADTs which you didn't want to get edited, but that should be pretty obvious, especially when those ADTs around those you wanted to get edited start to crash. Just delete them from custom patch of yours and call it a day.

[Basto&co]

Can you send the hole report of the WoW-error? Cause there are pop up TWO (!) windows even WoW errors and that with more information says sometimes the exactly problem.

And a question; Did you use a modded/hexed wow.exe?

Greets,
B&C