[Development] NoggIt from now on.

[schlumpf]

Skullbot:
Filebeam - Beam up that File Scottie!

Kantheras: Yes, it corrupts the locale-enUS.mpq. Live with it until we found out why. ._.

If I would get a dollar everytime, I fix some ADT or bug, ...

[Skullbot]

If I would get a dollar everytime, I fix some ADT or bug, ...

I think we can make business =D

Seriously, this .exe need two missing .dll :
- MSVCR100.dll
- MSVCP100.dll

And those founded on Internet gave me :
"[...] _invalid_parameter_nofinfo_noreturn_ is missing in [...] MSVCR100.dll"

Do you compile with Visual Studio 10 ?

Edit : Fix found http://pcsx2.dyndns.org/vc10/vcredist_x86.exe

[schlumpf]

Yes, I did. Sorry, did not think about that. I guess, I will compile with the old one again next time.

[Skullbot]

Bug detected, analyzing ...
When saving more than once, the second save leads to crash, but don't f**k up ADT.

Possible fixes :
No result found...

Shutdown in 10 sec...

[~sInX]

Editing Brush Speed crashes noggit (not instantaniously, but within around 5 minutes, it will crash). Moreover, refreshing chunk textures fails (doesn't work - Z hotkey atc). Water doesn't load, saving doesn't work ( hasn't for me in any of the adts which i've tried it in) and the lighting is slightly unconventional - presuming that's also a bug (skybox changes without warning, contrast flickers rapidly, etc).

[Skullbot]

It doesn't crash when changing brush radius for me, even after hours of work under Noggit.
Water is NYI, and saving has just been completely re-done, so it can remains some bugs.
Flickering light problem seems to be WMO related.

About saving, it's weird that no ADT can be saved, yes it crashes after saving, but file is saved correctly for me. Maybe it'll be fixed soon.

[wowoo]

Where can I download Noggit for 3.2.2 10505?

[Naiakoa]

It doesn't crash when changing brush radius for me, even after hours of work under Noggit.
Water is NYI, and saving has just been completely re-done, so it can remains some bugs.
Flickering light problem seems to be WMO related.

About saving, it's weird that no ADT can be saved, yes it crashes after saving, but file is saved correctly for me. Maybe it'll be fixed soon.

I agree with you about the saving issues. Yes it saves correctly, however once it saves Noggit immediately crashes. In the log files it only saves that one ADT that you try to save to and that ends the log. After I restart Noggit and go to the ADT further away from the edited area Noggit loads fine but when I go from that far away ADT to load the one I edited before Noggit crashes again. Here is part of the log prior to the crash:

.\maptile.cpp:235 >   Loading tile from MPQ 33,50
.\maptile.cpp:409 > Finished Processing all but MCNK's in .\world.cpp:1278 > 0 ms
.\maptile.cpp:425 > Entire loading of World\Maps\Kalimdor\Kalimdor_33_50.adt took .\world.cpp:1278 > 4 ms
.\maptile.cpp:681 > Unloading tile 25,51
.\maptile.cpp:235 >   Loading tile from MPQ 33,51
.\maptile.cpp:409 > Finished Processing all but MCNK's in .\world.cpp:1278 > 1 ms
.\maptile.cpp:425 > Entire loading of World\Maps\Kalimdor\Kalimdor_33_51.adt took .\world.cpp:1278 > 4 ms
.\maptile.cpp:681 > Unloading tile 26,52
.\maptile.cpp:235 >   Loading tile from MPQ 33,52
.\maptile.cpp:409 > Finished Processing all but MCNK's in .\world.cpp:1278 > 0 ms
.\maptile.cpp:425 > Entire loading of World\Maps\Kalimdor\Kalimdor_33_52.adt took .\world.cpp:1278 > 4 ms
.\maptile.cpp:681 > Unloading tile 28,48
.\maptile.cpp:235 >   Loading tile from MPQ 33,53
.\maptile.cpp:409 > Finished Processing all but MCNK's in .\world.cpp:1278 > 0 ms
.\maptile.cpp:425 > Entire loading of World\Maps\Kalimdor\Kalimdor_33_53.adt took .\world.cpp:1278 > 4 ms
.\maptile.cpp:483 > Finished Loading Textures for World\Maps\Kalimdor\Kalimdor_33_50.adt
.\maptile.cpp:483 > Finished Loading Textures for World\Maps\Kalimdor\Kalimdor_33_51.adt
.\maptile.cpp:483 > Finished Loading Textures for World\Maps\Kalimdor\Kalimdor_33_52.adt
.\maptile.cpp:483 > Finished Loading Textures for World\Maps\Kalimdor\Kalimdor_33_53.adt
.\maptile.cpp:483 > Finished Loading Textures for World\Maps\Kalimdor\Kalimdor_33_49.adt
.\maptile.cpp:681 > Unloading tile 27,53
.\maptile.cpp:235 >   Loading tile from MPQ 30,48
.\maptile.cpp:409 > Finished Processing all but MCNK's in .\world.cpp:1278 > 1 ms
.\maptile.cpp:425 > Entire loading of World\Maps\Kalimdor\Kalimdor_30_48.adt took .\world.cpp:1278 > 101 ms
.\maptile.cpp:681 > Unloading tile 26,51
.\maptile.cpp:235 >   Loading tile from MPQ 31,48
.\maptile.cpp:409 > Finished Processing all but MCNK's in .\world.cpp:1278 > 1 ms
.\maptile.cpp:425 > Entire loading of World\Maps\Kalimdor\Kalimdor_31_48.adt took .\world.cpp:1278 > 33 ms
.\maptile.cpp:681 > Unloading tile 27,52
.\wmo.cpp:242 > Unloading WMO World\Wmo\Kalimdor\Buildings\Taurenhuts\Taurenchickenhut.Wmo
.\wmo.cpp:242 > Unloading WMO World\Wmo\Kalimdor\Buildings\Taurenhuts\Taurenhutd.Wmo
.\maptile.cpp:235 >   Loading tile from MPQ 32,48
.\maptile.cpp:409 > Finished Processing all but MCNK's in .\world.cpp:1278 > 1 ms
.\maptile.cpp:425 > Entire loading of World\Maps\Kalimdor\Kalimdor_32_48.adt took .\world.cpp:1278 > 9 ms
.\maptile.cpp:681 > Unloading tile 28,53
.\maptile.cpp:235 >   Loading tile from MPQ 33,48
.\maptile.cpp:409 > Finished Processing all but MCNK's in .\world.cpp:1278 > 0 ms
.\maptile.cpp:425 > Entire loading of World\Maps\Kalimdor\Kalimdor_33_48.adt took .\world.cpp:1278 > 15 ms

I might post it on the bug tracker if i remember my password lol.

[Skullbot]

Seriously, you can search a little bit, just one page before ...

Filebeam - Beam up that File Scottie!
with this .exe : Filebeam - Beam up that File Scottie!

Maybe you''l need to install this : http://pcsx2.dyndns.org/vc10/vcredist_x86.exe

Edit : Save is still a bit ****ed up, because it's probably the hardest part of the code.
Weird bugs are not rare so live with it until it was fixed

[Naiakoa]

Ah But I already have that but thanks for the links anyways I was just agreeing to your post but with more detail to the error

[akspa420]

I tried over and over again, but it seems that on 64-bit Windows 7, the damn app crashes once it approaches the 1GB working set memory mark. I've got about 9GB free ram (12GB total) when testing, so that shouldn't be an issue.

Perhaps compiling noggit as a native 64-bit binary would decrease the possibility of a memory-leak-induced crash for those of us on systems with tons of ram(?).

[Namiriu]

How to use the "Holes" command please ?

[T@rget]

How to use the "Holes" command please ?

Ctrl + Click to add a hole, Shift + Click to remove it, how do I know? I read the topic :wave:

[jeremy7271]

I can't use the links... they re-direct me to different sites.... HALP!!!!

[~sInX]

Mhm, editing brush 'SPEED' (not radius) crashes after around 1 - 2 minutes. Either that or NoggIt is compulsively crashing without provocation.