[Development] NoggIt from now on.

[T@rget]

I've got a Hackintosh I can help testing that release

[BYSCUIT]

Cant wait til the mac release.

[~sInX]

ok so im using noggit to alter the terrain of a particular adt for an edit which im planning on releasing. around 1 hour 30 mins later noggit crashes and the adt is currupt, therefore my last hour and 30 mins of work is fcked over.

why release software if it doesnt work? which it blatantly doesn't.
sry if im coming across rather judgemental/confrontational; im extremely fcked off. i appreciate the effort you guys are inputting to make this a succesfull tool, moreover i love the new functions but seriously, i was kinda hoping it wouldnt fck up solely using 1 adt, texturing and terrain altering. noggit 1.12 worked much more conveniently thn this ffs.

[Ravenheart]

If you really want to use this version of noggit to build something, i recommend you to back-up your work before every save of an adt

[schlumpf]

Ehem .. This thread is named "Development". It states "alpha" and "beta" everywhere. We search people to test it for us. Does that really sound like a "its stable, use it!" to you? We try to release only the most stable versions, but yes, there still are enough bugs. Another question is, why you even use a development version and don't save every ten minutes. These versions ALWAYS are subject to crash soon.

It IS your own fault, if you want to use this in a productive environment. Its clearly stated not to be intended for it. As we say, its a development and people should help us finding bugs etc. If you are not interested in doing that, go and **** yourself. Instead of flaming here (didn't we already have something like that? ..), just shut up or try to help us finding the bug and eliminating it. Your ****ed up ADT could help. What you have been doing in the last seconds may help. Your log may help. Flaming us for your own stupidity does not.

Thanks.

Actually, with the kind of feedback we currently get (almost always negative, if any), I really think about going on with this project. Have fun with YiasEdit. Oh, wait its not out. That's the difference. We let YOU test it so you can give us feedback at any time. Cromon waits till its done and releases it then.

[Toyoka]

Don't let anyone put you down, schlumpf. You and your team are doing a great job and the community is very lucky to have a team like you here (one that releases revisions, regardless how buggy they are). There are other competitors creating world editors as well but they all have their flukes and flaws. Mistakes are mistakes, everyone makes them. But that doesn't mean there has to be blame going around! Even if other world editor creators don't want to work together, or people are giving you bad feedback, it doesn't mean the end of the world

I personally use all the tools I can get my hands on. They all have their benefits and so they should all deserve equal appraisal in my opinion

[tnguyenxxxx628]

ty +Rep - filler

[steff]

In the moment we try to cut out all platform depended stuff and update to the newest Versions of al other dependencies. Further we start to test around with QT as new QUI Framework. So it will take some time to get it all clean and release a new version.

But we have to do this to get some trash out of the code. There are so many unused and dirty things to cut out

And please !!! If you find a Bug search our bugtraker if it is already listed there and if not insert it. Wit screens and log links and as many informations you have for us. Also you can leave comments in still opened bugs.

[Toyoka]

http://87.118.108.82/bugtraker/index...index&switch=1 For those of you having trouble finding the bug tracker

[Cromon]

Just to mention some points:
1. Normals are not stored correctly, therefore no lighting
2. A lot of sizes are messed up
3. Changing anything on a doodad completly messes up all of the MCRF (See this from my ADT-analyzer for Kalimdor_39_33.adt (Valley of trials) pastebin - collaborative debugging tool)
4. Often editing the terrain isnt resulting at the point where the mouse is

[steff]

We know all this problems and there are tickets for them in the bugtraker

[Cromon]

And basically why dont you sorta fix'em or take them out? There is no chance that the adt will ever work they way you save it. So why do you even give the possibility to save?

At least 3 of the points mentioned are work of bout ~5 minutes (normals, sizes and MCRF) and they will result in a (nearly) working ADT.

[*Alexz*]

Everytime i go to load noggit it crashes right at the start
Logs:

.\wowmapview.cpp:154 > Nogg-It $Rev: 104 $
.\wowmapview.cpp:264 > Game path: C:\Users\Alex\Desktop\Games\World of Warcraft\Data\
.\wowmapview.cpp:266 > Project path: C:\Users\Alex\Desktop\Games\World of Warcraft\
.\wowmapview.cpp:304 > Locale: enUS
.\wowmapview.cpp:362 > main: mpqs: 58 ms
.\wowmapview.cpp:398 > main: directory: 0 ms
.\dbcfile.cpp:13 > Opening DBC DBFilesClient\AreaTable.dbc
.\mpq_libmpq.cpp:125 > Unable to find file DBFilesClient\AreaTable.dbc! Check MPQs and the file that has been requesting this!
.\dbcfile.cpp:13 > Opening DBC DBFilesClient\Map.dbc
.\mpq_libmpq.cpp:125 > Unable to find file DBFilesClient\Map.dbc! Check MPQs and the file that has been requesting this!

[Cromon]

Well, open your locale-enUS.MPQ and look if there is really no AreaTable.dbc. Basically i would say that the MPQ could not be opened at all, i dunno if noggit gives a debug-message if MPQ could not be opened.

[Dark_Spyro_003]

Or just read the thread and do as it says: Unpack the patch-enUS.MPQ because noggit has problems with it for some unknown reason.
nogg-it: FAQ