Modcraft - The community dedicated to quality WoW modding!
Featured => Noggit => Topic started by: Gumby Gamer on June 13, 2015, 05:13:01 pm
-
https://www.youtube.com/watch?v=UmTOQ_dL9tk (https://www.youtube.com/watch?v=UmTOQ_dL9tk" onclick="window.open(this.href);return false;)
Please give feedback <3
Fixed* Sorry put the wrong link -_-
-
You linked to a channel, not a video.
-
You should probably at least look in that log file. Not likely to give you more help, though.
-
Use latest v0.22 version of noggit 1.4
-
Who began that versioning?! Also, where do you get that? And what source revision is it equivalent to?
-
It has always been there since we released SDL 1.4 beta. As it is a beta release, it obviously has some builds that were available for downloading from time to time. The last one released to public was 3.0.22. So, the file is called noggit_3.0.22.exe, but this guy is obviously using v14 or v15 version which used to have the black ground bug. The source on the official repository is up to Noggit SDL 1.3 which we have used as a base for our changes. The source on our testing repostiory which is linked in the thread complements SDL 1.4 v22 which is the last and the most stable version among other 1.4 builds. Clear enough?
-
So Im good friends with Phillipthenoobmodder, hes fixing the crashing issue for me, its a texture thats on my map that is "nulled" Texture, Hes going to fix that. But does anyone know why the textures when i go into the wow client show as black? Do I have to put them in the patch or somthing? Also still crashes on 3.0.22.
-
Use clean shader button in assist menu to remove the black issue. Crashes are caused by groundeffects data if you edit blizzard's adts. Make sure every chunk of your ADT has 4 textures in it. It will stop crashing them. It is Hanfer's bug from SDL 1.3.
-
I'm not sure what's causing the hiccup but the Crash is from the MTEX chunk starting with a 0x00 null byte after the chunk size value:
(http://puu.sh/intlP.png)
(http://puu.sh/intjq.png)
If I actually put a string there or remove the 00 byte, then resize the MCIN and all other offsets, the ADT works fine in Noggit, I have no idea what is causing the hiccup for it to have the 00 byte on it to begin with.
I am not a Noggit user so what I typed up may be meaningless but I figured I'd put in my two cents atleast.
-
Those crashes can be easily fixed inside Noggit as I already said.
-
Those crashes can be easily fixed inside Noggit as I already said.
(http://i.imgur.com/6RAALgM.png)
And as I'm still confused, how is that even possible if the ADT crashes noggit when it tries to load That 16x16 tile? Please define that part because I'm still very confused, there's no way to use any options in noggit if it crashes upon load up of the ADT.
It's only 2 ADT's that have the MTEX issue, all the others around it are fine and don't cause Noggit to close out. The moment I try to add either the Original 28_27 or 27_27 into the mix, it dies. So again, how would one go about using a Noggit function if putting the ADT into the load up causes it to crash/close?
-
Oh, I thougt those were client crashes. No idea, never had any crashes in Noggit.
-
Could I possibly try deleting out those ADT's and put them back in? is that a thing.