Client crashs

[Magnus]

Ok, after hopefully fixing this problem .....
viewtopic.php?f=12&t=7890  .....

... I have a new one.

1. I start a new Noggit (3.161) project
2. I put 2 objects in Northshire Valley
3. Make MPQ and test it in client
4. Works there
5. Make .tele stormwind
6. Walk out of Stormwind
7. Client crash

Snip:

Code: [Select]

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal Exception
Program: E:World of WarcraftWow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007B31F8
Seems to be a hard work with Noggit.

[Ascathos]

Oh look. A sticky.

viewtopic.php?f=12&t=2971


Also.
Noggit (3.161) project

No. Assuming I am still up to date with the version hierachy and this is the old one I remember.  Update.

[Magnus]

Hurray a sticky !  
But doesn't helped me really.

But I downloaded a newer version Noggit 3.166.

Create a new project as I wrote before.

No client crash anymore, but start flickering again as I described here: viewtopic.php?f=12&t=7890

And I didn't saved twice.

 

[Magnus]

BUMP

[Amaroth]

WoW Error - as Ascathos wrote, sticky is here. Ground effects-caused error, just make sure that all chunks on errorring ADTs have all 4 textures used and you won't meet this error again there.

Flickering - I am nearly sure you have 2 (or more) Stormwind WMOs at one place. If using 1.3, do NOT save ANYTHING twice per running of Noggit, which means, always save and restart noggit before you continue working, but thats not the only one thing you need to do to prevent this.

Also try to save the whole map at once (simply click into every ADT, so the whole map will be "edited" and thus saved). In Kingdoms/Kalimdor/Outland/Northrend its nearly impossible, thats one of the main reasons why I nearly never work there. If you really want and need to work with original and full Kingdoms, just at least try to have all ADTs with big WMOs saved at once, which means - click into every ADT on which at least a bit of Stormwind's bounding boxes are, before you save.

Follow my instructions for saving and to fix actual problem you have try to move Stormwind a litle bit. You will see, if there aren't 2 (or even more) WMOs, duplicated from the original one by noggit bug. If it is so, just delete all of them and leave only 1 there. I have a feeling, that you were misled that just saving already edited and messed up map in right noggit version or just never double-saving will solve flickering problem - it won't, you need to delete tthose duplicates (and that my friend really won't be possible unless you edit all ADTs hit my Stomrwind bounding boxes at once).

[Milly]

Wait, you're saying all you gotta do is use all 4 textures to remedy the ground effect doodads bug? I gave up an entire project because of that bug...

[Amaroth]

viewtopic.php?f=12&t=2971
3rd error in main post

[Ascathos]

Wait, you're saying all you gotta do is use all 4 textures to remedy the ground effect doodads bug? I gave up an entire project because of that bug...

Why does no one bother looking into a sticky topic if it's one of the most used areas on this forum ? I don't get it

[kojak488]

Someone already told you to use the fileinfo and loadinfo tools on the ADTs to find the duplicate and remove it.  This thread is unnecessary.

[Magnus]

Ok, today I had a little bit time to work with Noggit again.

Checked this issue with Stormwind wmo inside Noggit. I can delete Stormwind for about 8-9 times till it disappears from the screen. So it's several times inside. This in a new project. After I delete it and save and restart Noggit it's again several times inside.

Don't know why and have no idea how to fix this.

I gave up this project and tried a new one in Tanaris, so empty project folder.

Made this in Tanaris:
- Select a palm tree
- Ctrl-C
- Ctrl-V
- Ctrl-V
- Ctrl-V
- Ctrl-S
- MPQ
Result: Wow crashs immediately

So I can choose between flickers (Stormwind) or crashes (Tanaris).

So unfortuntely for me that's the end for working with Noggit. Will try to realize my world with server side objects even it slows down the server.

However if somebody has any ideas I will try that.

[Amaroth]

I don't know which crash you get when working in Tanaris, However, if it is the same on (0023:007B31F8) I already answered you. Read my post and start to do as I wrote there. I am nearly sure that you won't get more crashes or object duplications, just try to follow my (all!!!) instructions. I think I made myself rather clear, but feel free to ask if you didn't understand something.

[Magnus]

I read you post and tried all the things.

Stormwind:
- Use Noggit 3.166
- The save bug I already know and never do it. I even use Ctrl-S instead the mouse to prevent double clicks.
- For every try I empty the project folder. So, no old or previous edited files.
- Thanks to your post I discovered the multiple spawns of Stormwind. However that's every time starting a totally new project. I delete SW as much as I can, save, close Noggit, reopen it, again multiple spawns. Will give a try today once more.

Tanaris:
- The crash error is indeed 0023:007B31F8.
- I made what I have written: Select a palm tree, Ctrl-C, Ctrl-V, Ctrl-V, Ctrl-V, Ctrl-S
- After a save I close Noggit completely.
- Today I tried additionally to save more adt's around my edited area.

That's what I'm doing. Don't know what else I can do.


However today I started in Tanaris the same project with Noggit 1.2. Works atm without problems. Except I lost the sea (water) layer. But as far as I know that's not a bug it lacks of support in Noggit and must added manually. Don't know how yet, but will check that in forum posts. (Links appreciated   )

[Simping]

However today I started in Tanaris the same project with Noggit 1.2. Works atm without problems. Except I lost the sea (water) layer. But as far as I know that's not a bug it lacks of support in Noggit and must added manually. Don't know how yet, but will check that in forum posts. (Links appreciated   )

I use this tool when adding water to my ADT's:
viewtopic.php?f=59&t=554

[Amaroth]

Also try to save the whole map at once (simply click into every ADT, so the whole map will be "edited" and thus saved). In Kingdoms/Kalimdor/Outland/Northrend its nearly impossible, thats one of the main reasons why I nearly never work there. If you really want and need to work with original and full Kingdoms, just at least try to have all ADTs with big WMOs saved at once, which means - click into every ADT on which at least a bit of Stormwind's bounding boxes are, before you save.

This was important. Saving the whole map at once should prevent duplicating objects, or at least saving all ADTs which can posssibly have any "reason" to have specific object (for you SW WMO) saved in them. Problem is that SW WMO is huge, Azeroth map as well, which means that loading the whole map and saving it at once is quite impossible. You can, however, save all ADTs where SW is and always when you will want to do anything in any of those ADTs, you must save ALL ADTs, NEVER only a few of them. I marked 16 ADTs which contain at least a bit of SW. Those around them were saved together with those 16 ones (SDL 1.3s way how to prevent such bugs, sadly useless for such huge objects).

So, whenever you will edit anything in all these 36 ADTs you can see saved here, you need to also edit all 16 red marked ADTs (in SDL 1.3) to not have SW duplicated during saving of your work. I tested it - worked for me, SW didn't duplicated when all those 16 red marked ADTs were edited and thus they and ADTs around were all saved at once.

Screen: