BETA V 120 B 19 - changeset 91 (bafa324c29de)

[Steff]

Next version.

http://www.file-upload.net/download-3152685/Noggit3_v120_B19.zip.html

Changes since B17:

- Insert the Map Window from the start menu also inside the 3D view. Open up with M. Replace the old Map.
- New implementation of saving. Now every change on an ADT marks this as changed. If you save now every changed ADT will get saved (CTRL + S) The old Save function is also in. You can find it over the menu or with SHIFT + CRTL + S.
- All changed ADT are marked with a white border in the Map Window.
- Fix a problem with WMO import from ModelViewer ( but found out that WMOs with doodads inside make problems, work on it)
- Add StackWalker to the logfile. So if noggit crash we have some more infos to find out why.

Please test the new save method. Open up the map window (M) and make changes on ADTs.
Every change MUST add the white border to the ADT in the map window that it get saved!
Ground edit. hole, Rotate of models, scalingmovement, texturing .... everything!

[gorq]

Ok i have noticed a bug in 2d texturing. It seems to appear a black bar on the map. It moves when i move camera or make zoom in/out.





New saving method is working really nice ^^ White lines appear on modified ADT and disappear when you save them! ^^



3d texturing is a bit fucked near adt border. I'm sorry i cannot explain it better. I mean when u paint over an adt, the next adt is not painted. And another problem..if u paint near adt border it seems to paint a pair of meters away of the border too

Import human scale and cube OK
Import from txt OK
WMO manipulation and saving OK
Doodad manipulation and saving OK
Holes OK

F7 is still rendering fake water on Z=0

[Steff]

In this version it is importend that ALL adt modifications change the status of the ADT so it gets saved. So try all modifikations you know and see if the with swaure appears. If not i have to fix this tool to cahnge the status too. Thanks for you testing.

[gorq]

well as i have tried adt status is modified when:

texturing
modifying landscape shape
moving objects

 (have to try if it saves when only importing)

dp: oh, IMPORTANT hehe lol

[Steff]

I tryed the 3D painting over ADT borders now some times. And it works. Notice that the other adt must be drawwable Must have free Texture slots. if all 4 sloats are full you cant paint on it.
I will try to implement an auto Texture slot freeing routine in nne of the next versions. So if a texture is not used noggit should kill it so you can paint.

The problem with painting away from your position is a known 3D selection problem and do not only appear in 3D painting. But there you notice it the most.

[gorq]

Oh yes i know.There are 4 textures in a chunk and i know how to free all of them (delete) . This adts are new and they only have one texture. I think my problem is because i have been painting too far from the ground and maybe it is the bug u have said. I will try it another time.

I have to try importing from modelviewer log too ^^

Do u know anything bout my 2d texturing problem? The most zoom i do the most worst i see it. lol

oh and, there is something bout doodad collision? (wmo collision is working nice ^^)

[Tigurius]

Happens in Northrend, most likely everywhere when the Data was previous as 4096 stored after saving.

[gorq]

I'm sorry i have discovered that my "black bars" problem was because of a bugged release from ContinentCreator (oups!) Now my 2D texturing is 100% working for me. Apologyze me

[Steff]

Nice to here that not every problem comes from noggit

[SirFranc]

Tanks a lot i'm going to test it right now

BTW i always found a bug (and usually other people didnt') when resetting chunks of textures the ADT got always corrupted with no way to repair it : /

[SirFranc]

Everything works fine except the modelviewer things, nothing happens selecting them.
I found massive lag when moving a lot round the terrain but i guess is better than before since i expected no crash, stability is dramatically in creased!
The new brushes work as intended too, good job!

EDIT: i found many problems selecting objects properly. As well some objects are impossible to select (like the bird doodad... now that keeps flying you don't know where to click to select it) and usually the object i click on doesn't get selected, while the terraining tool seem more reliable

EDIT2: random crash, sadly i forgot to save the log, next time that happens i'll post the log crashdump.

[Steff]

Do you meen you cant import models from medelviewer or you cant select them after import.
I had the selection problem also. Just leave noggit and start again, then this models should also get selectable. Hase something to do with insert. I will test this.

Noggit loads now all adts and dont unload them. So if you work some time your ram will get full if you work on a wider area. We will implement an unloading routine later. This will also lead to crash if your ram is full.

The bird is realy not easy to get
We could make  select the bird contest.
But it is possible, i have also some on my last map and it took some time to get them
I think abbout the idea to insert a mode, all models ( or just some we know that they make problems to select) get replaced with boxes to get them easier.

[SirFranc]

Do you meen you cant import models from medelviewer or you cant select them after import.
I had the selection problem also. Just leave noggit and start again, then this models should also get selectable. Hase something to do with insert. I will test this.

Noggit loads now all adts and dont unload them. So if you work some time your ram will get full if you work on a wider area. We will implement an unloading routine later. This will also lead to crash if your ram is full.

The bird is realy not easy to get
We could make  select the bird contest.
But it is possible, i have also some on my last map and it took some time to get them
I think abbout the idea to insert a mode, all models ( or just some we know that they make problems to select) get replaced with boxes to get them easier.

Suggestion, may look stupid:
Add those visualize options:
-Show all bounding boxes (the ones that appear when you select) for M2
-Show all bounding boxes for Wmo
-Show spawn points (showing a cube where the spawn point of the object is like Wc3 editor "Use click helper", this would help not only for objects like the bird, but as well to place particle models into the game (for example seeing where the fire particle i'm adding spawns, not necessarily seeing particles but knowing WHERE it spawns)

This would help a lot.
Also noticed a weird bug on MonasteryInstances map, when looking around the wmo pieces appeared and disappeared quite randomly.

Yes, something to unload memory would be useful, i usually find myself working with 10 adts at time ^^'

About model viewer import tool: how does exactly work? because when i click on it nothing happens at all

[Steff]

You must set the path in the noggit.config file.
Import file to the path where the log.txt of the modelviewer is located.
You find it inside the usrSettings folder in the modelViewer directory.
But this onyl works good for m2s. Bacaus i just import the last file loaded and if you load a wmo and this one hase doodads inside modelviewer loadd them after the wmo. So you get the last doodad but not the wmo.

[SirFranc]

I managed to get the piece of code from random crash that usually occurs

[spoiler:utx628qy]

Code: [Select]

(..srcStackWalker.cpp:1221): Stacktrace:ERROR: SymGetSymFromAddr64, GetLastError: 487 (Address: 00A0DEEC)
(..srcStackWalker.cpp:1221): Stacktrace:ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00A0DEEC)
(..srcStackWalker.cpp:1221): Stacktrace:00A0DEEC (noggit): (filename not available): (function-name not available)
(..srcStackWalker.cpp:1221): Stacktrace:ERROR: SymGetSymFromAddr64, GetLastError: 487 (Address: 009F9724)
(..srcStackWalker.cpp:1221): Stacktrace:ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 009F9724)
(..srcStackWalker.cpp:1221): Stacktrace:009F9724 (noggit): (filename not available): (function-name not available)
(..srcStackWalker.cpp:1221): Stacktrace:ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 6F81B907)
(..srcStackWalker.cpp:1221): Stacktrace:6F81B907 (MSVCR100): (filename not available): XcptFilter
(..srcStackWalker.cpp:1221): Stacktrace:ERROR: SymGetSymFromAddr64, GetLastError: 487 (Address: 00A2D7E6)
(..srcStackWalker.cpp:1221): Stacktrace:ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00A2D7E6)
(..srcStackWalker.cpp:1221): Stacktrace:00A2D7E6 (noggit): (filename not available): (function-name not available)
(..srcStackWalker.cpp:1221): Stacktrace:ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 76443677)
(..srcStackWalker.cpp:1221): Stacktrace:76443677 (kernel32): (filename not available): BaseThreadInitThunk
(..srcStackWalker.cpp:1221): Stacktrace:ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 779D9D72)
(..srcStackWalker.cpp:1221): Stacktrace:779D9D72 (ntdll): (filename not available): RtlInitializeExceptionChain
(..srcStackWalker.cpp:1221): Stacktrace:ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 779D9D45)
(..srcStackWalker.cpp:1221): Stacktrace:779D9D45 (ntdll): (filename not available): RtlInitializeExceptionChain
[/spoiler:utx628qy]