[Development] NoggIt from now on.

[Herbalism]

Hey I need some help with noggit :|

http://www.mmowned.com/forums/world-...wont-work.html

[mononavideño]

Hi, i installed noggit and run it, but it closes almost immediately when i start the program, also, it corrupts the mpq files inside EnUS folder changing the data and preventing the game from starting again.
I have to replace the corrupted mpqs.
Im using a 3.3.3a version but i have the same problem with a 3.0.1 version. any ideas why this happen?

[Reflection]

Hi, i installed noggit and run it, but it closes almost immediately when i start the program, also, it corrupts the mpq files inside EnUS folder changing the data and preventing the game from starting again.
I have to replace the corrupted mpqs.
Im using a 3.3.3a version but i have the same problem with a 3.0.1 version. any ideas why this happen?

Post the log.

[NerieX]

NoggIt = Worlds Best World Modifying Tool

[newtech]

Could anyone please upload the newest version of Noggit for WoTLK please? I dont know if this helps, but for wow's version 3.3.5 :P

[mononavideño]

Post the log.

.\wowmapview.cpp:154 > Nogg-It $Rev: 104 $
.\wowmapview.cpp:264 > Game path: C:\Archivos de programa\World of Warcraft\Data\
.\wowmapview.cpp:266 > Project path: C:\Archivos de programa\World of Warcraft\
.\wowmapview.cpp:304 > Locale: enUS
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\common.MPQ
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\common-2.MPQ
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\expansion.MPQ
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\lichking.MPQ
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\patch.MPQ
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\patch-2.MPQ
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\patch-3.MPQ
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\patch-a.MPQ
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\patch-b.MPQ
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\patch-d.MPQ
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\enUS\locale-enUS.MPQ
.\mpq_libmpq.cpp:29 > Error opening archive C:\Archivos de programa\World of Warcraft\Data\enUS\locale-enUS.MPQ
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\enUS\expansion-locale-enUS.MPQ
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\enUS\lichking-locale-enUS.MPQ
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\enUS\patch-enUS.MPQ
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\enUS\patch-enUS-2.MPQ
.\mpq_libmpq.cpp:27 > Opening C:\Archivos de programa\World of Warcraft\Data\enUS\patch-enUS-3.MPQ
.\wowmapview.cpp:362 > main: mpqs: 611 ms
.\wowmapview.cpp:398 > main: directory: 1154 ms
.\dbcfile.cpp:13 > Opening DBC DBFilesClient\AreaTable.dbc
.\dbcfile.cpp:13 > Opening DBC DBFilesClient\Map.dbc
.\dbcfile.cpp:13 > Opening DBC DBFilesClient\LoadingScreens.dbc
.\dbcfile.cpp:13 > Opening DBC DBFilesClient\Light.dbc
.\dbcfile.cpp:13 > Opening DBC DBFilesClient\LightParams.dbc
.\dbcfile.cpp:13 > Opening DBC DBFilesClient\LightSkybox.dbc
.\dbcfile.cpp:13 > Opening DBC DBFilesClient\LightIntBand.dbc
.\dbcfile.cpp:13 > Opening DBC DBFilesClient\LightFloatBand.dbc
.\dbcfile.cpp:13 > Opening DBC DBFilesClient\GroundEffectDoodad.dbc
.\dbcfile.cpp:13 > Opening DBC DBFilesClient\GroundEffectTexture.dbc
.\dbcfile.cpp:13 > Opening DBC DBFilesClient\LiquidType.dbc
.\mpq_libmpq.cpp:125 > Unable to find file fonts\MORPHEUS.TTF! Check MPQs and the file that has been requesting this!
.\FreeType.cpp:232 > ERROR: FT_New_Face failed (there is probably a problem with your font file)

That's the log, it seems to be simmilar to other log i saw in this post but that person didn't mention anything about corrupted mpq files.

[Reflection]

Isn't the last lines obvious? Do you have the fonts in your directory as Noggit can't find them?

[mononavideño]

Isn't the last lines obvious? Do you have the fonts in your directory as Noggit can't find them?

How does that explain the mpq data corruption? i would like to know to avoid reintalling the game in order to fix it.

[newtech]

How does that explain the mpq data corruption? i would like to know to avoid reintalling the game in order to fix it.

God... This has nothing to do with your MPQ's. The error is caused, because your Noggit is missing a file named MORPHEUS.TTF Which means, download an earlier version of noggit and get it from there, or find it some other way. Now, I know your gonna say "can you give me a link please?" No. Go google it. It cant be that hard -.-

[mononavideño]

God... This has nothing to do with your MPQ's. The error is caused, because your Noggit is missing a file named MORPHEUS.TTF Which means, download an earlier version of noggit and get it from there, or find it some other way. Now, I know your gonna say "can you give me a link please?" No. Go google it. It cant be that hard -.-

Look buddy, I wasn't going to ask you any link so spare me that.
Gods, people here are so Unpolite. I know all of you may be tired of answering dumb questions but if you are tired of that just don't do it.

[Tigurius]

As there isn't any progress in development... here is the broken source code: File-Upload.net - noggit-sourcecode.zip

If someone wants to fix it... have fun: http://imagr.eu/up/4b92559ee7ff2_Noggitfail2.jpg

[akspa420]

Thanks for releasing the bugged source code. I don't know much about c++, but I'll take a stab at it - first things first, I'm updating all the libs to the latest versions, and solving basic bits like that before attempting to figure out what the hell happened to the program (yes, not conventional, but hey, I'm learning something ). I have high hopes that someone else will take a stab at it, someone that actually knows wtf they're doing, anyway :P

[schlumpf]

Thanks for releasing the bugged source code. I don't know much about c++, but I'll take a stab at it - first things first, I'm updating all the libs to the latest versions, and solving basic bits like that before attempting to figure out what the hell happened to the program (yes, not conventional, but hey, I'm learning something ). I have high hopes that someone else will take a stab at it, someone that actually knows wtf they're doing, anyway :P

The libs should be up to date. I updated them recently.
When learning C++, you may not want to start with something like this.

[newtech]

The libs should be up to date. I updated them recently.
When learning C++, you may not want to start with something like this.

Meh, give him a go. Who knows, he might be our savior? xD In case he isnt gonna fix it, (which well... Isnt the biggest chance he will) would someone who knows C++ please give it a go? I know a lot of people would be very happy with you!

Thanks
Newtech
Keta

[Cromon]

I had a look on it, but it was kinda shocking. Nearly all the models had no textures, there was no terrain at all showing up, WMO were just a colored block of vertices without textures and it crashed about once every 2 minutes. I gave the models and WMO their textures back and terrain went back to the right place but was only displayed as fog and its not really easy to go through the source-code to find the error (as i also don't really like OpenGL). And of course it still crashes on nearly every action. So i gave up to repair it

/Edit:
And the coding style is not really good. A big mixture of C and C++ (which is commonly considered as one of the worst and most dangerous combinations) everywhere. The code is very unstable as there are only very few validation checks and no exceptions are being caught. In about an hour i also found about 4 places that looked like that:

void foo()
{
      void* pMemory = malloc(someLargeAmountOfMemory);
      doSomeThingWithMemory(pMemory);
}

You see: No free (why even use malloc -> free? We have new -> delete[] now...) at all. Also known as memory leak. The Visual Studio Ultimate Profiler gets crazy analyzing the code