Modcraft - The community dedicated to quality WoW modding!
Featured => Noggit => Topic started by: Petisoo on February 07, 2015, 07:10:08 am
-
Well, it is simple: Every time that I'm editing a Blizzard map, I get wmos and m2s duplicated, like this one:
[attachment=0:8n19lq2p]Sin título.jpg[/attachment:8n19lq2p]
My question is: The only way that I've to solve this problem is saving both adts (image)? Is there other way? 'Cause I'm getting this error in EVERY edge of edited adts and I can't save all of them.
-
Get the newest Noggit. Find the pack in the tread here and then take the latest executable from here: https://drive.google.com/folderview?id= ... aring#list (https://drive.google.com/folderview?id=0B-6Vaewxxz9aMVlyTkpuOFZzd3c&usp=sharing#list" onclick="window.open(this.href);return false;)
There will be a button to fix duplicatilon in the latest version.
-
When will it be ready? I mean, the latest. Because I've founded lot of duplication and I'm unmotivated.
-
Get the latest executable and go to assist menu -> Remove duplication.
-
I've already done that, but take a look to the before-after:
BEFORE:
[attachment=0:3i5hi778]image1fix.jpg[/attachment:3i5hi778]
AFTER:
[attachment=1:3i5hi778]image2.jpg[/attachment:3i5hi778]
This is possible? My 1 ADT "map" will be 20+ ADTs after the remove tool.
-
Yes. That makes technical fully sence.
-
Damn... Is just one adt, but... after the toll i've 20... Is not a good thing...
P.S: 20 with 0x007B31F8 read 0x00000010 (viewtopic.php?f=48&t=8893&p=43916#p43916 (http://modcraft.io/viewtopic.php?f=48&t=8893&p=43916#p43916" onclick="window.open(this.href);return false;))
-
Just delete those unwanted ADTs from your map folder and/or add only that 1 to your patch. You will have only 1 ADT changed, it will be working without errors and duplications and all ADTs around will be kept blizzlike, so no problems to worry about with them.
-
If you habe a bigger wmo placed thatnspawns over more adts. And it is not included in all. The wmo is simple missing if you enter the adt where it is nkt added. Beside this amaroth is right.
-
Yes I've done that, but in every corner of the ADT there are wmos and m2s duplicated. Like trees or rocks, you know... the usual things that you find in the woods.
-
Which noggit version do you use?
-
Last one: 1.4 with noggit_3.0.22.exe
If u want a picture about the problem, let me know. But is quite simple, 'cause is just a WMOs and M2s duplication in the division between 2/3/4 adts. For example: There is a tree in the green line between my edited ADT and the Blizzlike that i don't want, well... that tree result in a duplication.
Edit: Picture related: download/file.php?id=2514 (http://modcraft.io/download/file.php?id=2514" onclick="window.open(this.href);return false;) (Is an old picture, there i was using 1.3, but is the same problem so...)
-
Well... I've the solution for this duplication problem.
I can say that is solved by myself, if someone wants to know how to do it, send me a PM.
-
How did you guys solved the problems of wmo duplication in noggit, I still face the same using Noggit 14
Please help me.
-
Imo, a nice and clean way is still fileinfo (http://modcraft.io/viewtopic.php?f=59&t=816).
-
Go and clean 50 adts with a few hundred of duplicates manually using loadinfo. I would enjoy watching the process. Noggit cleans duplicates for each adt in one second. Fileinfo thing is useful for only severe cases from early 1.3 when you can't load the map in Noggit.
-
Go and clean 50 adts with a few hundred of duplicates manually using loadinfo. I would enjoy watching the process. Noggit cleans duplicates for each adt in one second. Fileinfo thing is useful for only severe cases from early 1.3 when you can't load the map in Noggit.
Interesting that you say that, I am not doing adts anymore. I never said that noggit is a bad thing, either. Quite the opposite.
Also was refering to the question asked before mine as additional point to the entire thread.
-
Imo, a nice and clean way is still fileinfo (http://modcraft.io/viewtopic.php?f=59&t=816).
Thank you for quick reply, I have downloaded fileinfo.rar which contains
1. fileinfo.cpp Source file for clean build.
2. fileinfo.exe executible with no information how to use it, and
3. fileinfo.o ? unknown filetype
My humble request to you is that if you shed some light of information on how to use this tool , It will be helpful for noobs like be.
Thank you again for your kind heart once again.
-
Imo, a nice and clean way is still fileinfo (http://modcraft.io/viewtopic.php?f=59&t=816).
Thank you for quick reply, I have downloaded fileinfo.rar which contains
1. fileinfo.cpp Source file for clean build.
2. fileinfo.exe executible with no information how to use it, and
3. fileinfo.o ? unknown filetype
My humble request to you is that if you shed some light of information on how to use this tool , It will be helpful for noobs like be.
Thank you again for your kind heart once again.
fileinfo consists commonly out of these files:
cygwin1.dll (THe library the creator gathered and used)
FileInfo.exe
Loadinfo.exe
Maybe loadinfo.exe.stackdump.
You pull an adt into fileinfo and a txt file is extracted. You can edit that textfile.
Now, you pull the adt into fileinfo and it's original content is overwritten by the content of the txtfile.
The txt consists of several pieces of information that you should easily understand, because it's also declared in the wiki.
I personally prefer working with such a textfile. However, as was pointed out, noggit is far faster to remove duplicate models for many adts. But fileinfo is still a powerful tool.
-
Imo, a nice and clean way is still fileinfo (http://modcraft.io/viewtopic.php?f=59&t=816).
Thank you for quick reply, I have downloaded fileinfo.rar which contains
1. fileinfo.cpp Source file for clean build.
2. fileinfo.exe executible with no information how to use it, and
3. fileinfo.o ? unknown filetype
My humble request to you is that if you shed some light of information on how to use this tool , It will be helpful for noobs like be.
Thank you again for your kind heart once again.
fileinfo consists commonly out of these files:
cygwin1.dll (THe library the creator gathered and used)
FileInfo.exe
Loadinfo.exe
Maybe loadinfo.exe.stackdump.
You pull an adt into fileinfo and a txt file is extracted. You can edit that textfile.
Now, you pull the adt into fileinfo and it's original content is overwritten by the content of the txtfile.
The txt consists of several pieces of information that you should easily understand, because it's also declared in the wiki.
I personally prefer working with such a textfile. However, as was pointed out, noggit is far faster to remove duplicate models for many adts. But fileinfo is still a powerful tool.
Thank you Buddy Thats helpful.
+REP