Forum > Noggit

My Fix Idea for Crashes that come from Editing Blizz ADTs

(1/3) > >>

PhilipTNG:
Basically just about anyone who's made an edit on a blizzard ADT with Noggit 1.3 or 1.4 has noticed the eventual crash that happens when you do edits to a blizzard map adt. So I spent half my day changing stuff around until I got around the crash and here's what I came up with.

The crash can happen for multiple reasons, this is a hacky fix idea for one of the crashes that I ran into, it may not work for other people with crashes caused by something else. Also this isn't a recommended fix since I'm pretty sure it could lead to something bad in the long run XD.

[media:2ubkzoww]https://www.youtube.com/watch?v=vdgxYJJLGS8[/media:2ubkzoww]

I'm not giving any type of script out because I have no idea how safe this is and last thing I want is a whole lot of people barking up my inbox filling it with, "You Broke My MAP!!!! WAHHH!!!!"

Skarn:
Haha, you can do it much easier actually even without tinkering with .adt data. As is said for multiple times, the problem is really simple. Blizzard WoWEdit does not really care about the order of textures on adt chunks. So, sometimes there may be 2 or 3 textures on a chunk, and Noggit is not really able to handle groundeffect saving on these adts. So, the best solution is to change Noggit's code. Though, there is a hackfix too. Just pick up a huge brush and paint some random textures with 0 opacity on your change Blizzard adts. Here is another problem. The more adts you fix, the more adts Noggit corrupts around. So, you just fix adts you really need and remove all extra saved ones. That's all.

PhilipTNG:

--- Quote from: "Skarn" ---Just pick up a huge brush and paint some random textures with 0 opacity on your change Blizzard adts.
--- End quote ---
I tried that painting idea you posted in another thread, I still ended with the error on the ADT that I errored on in the video. :(

schlumpf:
I was interested in your idea until I was forced to watch a three minute video. Guess I'll never know the idea.

PhilipTNG:

--- Quote from: "schlumpf" ---I was interested in your idea until I was forced to watch a three minute video. Guess I'll never know the idea.
--- End quote ---
it's just zero'ing out the 16 bytes(32x2bit values) at the 0x40 of the MCNK Header, the 16 bytes after the Hole area.  Hacky but avoided the crash that came from editing the file.  Doing so also fixed a buddy's previously un-usable adt files as well which consisted of some 120 adts.

It's probably just something to do with the MCLY but I didn't look too much into it. maybe later I will.

Navigation

[0] Message Index

[#] Next page