Noggit bugs

[Steff]

You mean you change only one adt and noggit save more..  That is normal and needed. Models on boarders are located on 2 till 4 adts.  So you need always one row adts saved plus around yoir edit to proof that all is clean.

[slyceR]

• Dont delete Groundtextures

[Steff]

?  better description please.

[slyceR]

?  better description please.

Its a Windows 10 Bug only

Windows 10 Bugs in Noggit

• Texture deleting didn't work
• Water edit didn't work
..coming more

[Skarn]

Those bugs cannot appear because of Windows 10. It is impossible.

[Reynaud]

Hello!

I'm a worldbuilder from the "Schattenhain-Project" (Luzifix) and have a problem in Noggit. Accidentially I imported a raindbow model from the modelviewer into Noggit. (sholazar_rainbow.m2) I can't see it in noggit, its invisible and not clickable, so I can't delete it. At ingame test, there is a rainbow now. Is there a way to delete this item in Noggit without resetting all m2 models at the .ADT? Would be awesome, if there's a solution because the backup from this ADT is one week old.

Thanks for replies!

[Ascathos]

Hello!

I'm a worldbuilder from the "Schattenhain-Project" (Luzifix) and have a problem in Noggit. Accidentially I imported a raindbow model from the modelviewer into Noggit. (sholazar_rainbow.m2) I can't see it in noggit, its invisible and not clickable, so I can't delete it. At ingame test, there is a rainbow now. Is there a way to delete this item in Noggit without resetting all m2 models at the .ADT? Would be awesome, if there's a solution because the backup from this ADT is one week old.

Thanks for replies!

Fileinfo. Wondering why luzifix didn't think about that.

That aside, wondering why it's not clickable.

[x13lackcatxlllx]

Hey there, my Noggit is crashing whenever I'm near Alterac, yet isn't crashing for the others I work with.
The only error I'm seeing is -
9339 - (Video.cpp:280): [Error] OpenGL: (at Model::draw:: after the draw list): GL_INVALID_VALUE
Here's my entire crash log.
http://pastebin.com/dp4TicN0
Could anyone please provide some insight on what is causing the crashing or any tips? I'd really appreciate it.
Thank you.

[Adspartan]

Hello!

I'm a worldbuilder from the "Schattenhain-Project" (Luzifix) and have a problem in Noggit. Accidentially I imported a raindbow model from the modelviewer into Noggit. (sholazar_rainbow.m2) I can't see it in noggit, its invisible and not clickable, so I can't delete it. At ingame test, there is a rainbow now. Is there a way to delete this item in Noggit without resetting all m2 models at the .ADT? Would be awesome, if there's a solution because the backup from this ADT is one week old.

Thanks for replies!

Noggit only render the rainbow on one side, try to set the time to the night it will be easier to spot it and circle around the position of the object, when you see it you can select it.


On a side note, I don't think this has been repported but swapping textures doesn't mark adt as edited (only when swapping the whole adt).

[Vortalex]

A map that has been only slightly altered by the newest version of Noggit causes my game to crash after making only a few brief movements.

I think it is related to the water not saving, because the water didn't appear in Noggit when I reopened the recently edited map.

[Amaroth]

That depends on Noggit version, SDL 1.3 and especially 1.4 do save water. Post crash log (can be found in Errors in WoW folder). Were you editing blizzlike maps? Is your exception looking like this?:

Code: [Select]

ERROR #132 (0x85100084) Fatal Exception
Program: C:FilesWorld of Warcraft 3.3.5aWow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007B31F8
If it does, its long know problem and solution can be found here (3rd crash in main post, solution may be found there even if this crash I posted is not your case).:
http://modcraft.io/viewtopic.php?f=12&t=2971

[Vortalex]

That depends on Noggit version, SDL 1.3 and especially 1.4 do save water. Post crash log (can be found in Errors in WoW folder). Were you editing blizzlike maps? Is your exception looking like this?:

Code: [Select]

ERROR #132 (0x85100084) Fatal Exception
Program: C:FilesWorld of Warcraft 3.3.5aWow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007B31F8
If it does, its long know problem and solution can be found here (3rd crash in main post, solution may be found there even if this crash I posted is not your case).:
http://modcraft.io/viewtopic.php?f=12&t=2971

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal Exception
Program:   D:Camerons PlaygroundArena-tournament.com 3.3.5 qqqqWow.exe
Exception:   0xC0000005 (ACCESS_VIOLATION) at 0023:007B31F8

The instruction at "0x007B31F8" referenced memory at "0x00000010".
The memory could not be "read".

[Amaroth]

You didn't have to post whole log, just top of it . Its exactly like I said. Follow quoted Ascathos' advice in main post in topic I linked above - keep all chunks in all edited ADTs filled with 4 different textures used, otherwise those ADTs crash after being saved in Noggit (if they have ground effects on, and nearly all blizzlike ADTs have ground effects).

[Vortalex]

You didn't have to post whole log, just top of it . Its exactly like I said. Follow quoted Ascathos' advice in main post in topic I linked above - keep all chunks in all edited ADTs filled with 4 different textures used, otherwise those ADTs crash after being saved in Noggit (if they have ground effects on, and nearly all blizzlike ADTs have ground effects).

Well here's the thing. I opened an existing WoW map, and the only change I made to it was that I added an AreaID Paint onto 3 chunks, then I saved. The crash occurs anyway.

The other thing too, is that this problem DOES NOT occur when I use the old version of Noggit.

[Amaroth]

You really can trust me with this. It doesn't matter what you do on ADT, wheter you remake all texturation and modelling or just one-click on one model. What matters is that you save it in Noggit. Older version also doesn't help, for one reason, new version saves ADTs you edited and also all ADTs around it. Which means that what happened to you is that you have edited ADT without ground effects, saved it and:

- newer version - saved ADTs around and at least one of them had ground effects while not having all chunks completely filled and thus started crashing in game.

- older version - didn't save ADTs around and it worked for now fine. But only because you were very lucky, try to also edit those 8 ADTs around the one you have edited and there you go - you will get crash again.