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.
Imo, a nice and clean way is still fileinfo.
Quote from: "Ascathos"Imo, a nice and clean way is still fileinfo.Thank you for quick reply, I have downloaded fileinfo.rar which contains1. fileinfo.cpp Source file for clean build.2. fileinfo.exe executible with no information how to use it, and3. fileinfo.o ? unknown filetypeMy 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.
Quote from: "fadnis"Quote from: "Ascathos"Imo, a nice and clean way is still fileinfo.Thank you for quick reply, I have downloaded fileinfo.rar which contains1. fileinfo.cpp Source file for clean build.2. fileinfo.exe executible with no information how to use it, and3. fileinfo.o ? unknown filetypeMy 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.exeMaybe 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.