BETA V 120 B 20 - changeset 174 (4d0574ae3ae1)

[gorq]

ok thx steff it works now.  Have u changed the blur key too? I cannot use it :S

- Texturing is really bugged or changed..i cannot paint some textures with b20 but i can with b19. Maybe some stuff from the layers opacity? I have painted with full opacity.

[Instantfreakmod]

when u spawn and when ur flying it like flys u down fast and very far down...

[Skullbot]

Found some minors issues :

- When you right-drag to zoom in 2D View, it also moves the camea in 3D View (then when you switch back to 3D view, you'll most likely look to the sky)
- Moving an UI Item in 2D View also moves the view.
- In the "File" Item tooltip, the text is a bit too long and get out of the button.
- Experienced an Appcrash when texturing an area with 100-sized brush on untextured chunks, dunno if it come from me or not.

Special chars replacement works very well, finally can read zone name correctly ;p
Other issues I've found have already been reported =)

I'll try to build some little things to see if that works well IG.

[Diantonix]

Can not leave empty boxes in 2D mode.

[ToyokaX]

So I now have the pleasure to test out the 120 Beta, and I have a few bugs to report! Since I did not see a bugs topic in this sub-forum, I have made this topic exactly for that reason. So here we go:

I encountered this glitch shortly after downloading Noggit (and playing around with it), it appears when "Lines" are enabled.




But of course, it disappears when "Lines" is disabled




A strange glitch occurs when I try to texture in a certain way. It happens when I try to overlay a texture onto a texture that has, in turn, overlapped it (ie applying layer 1 texture on layer 2 texture that is over layer 1 texture). This might not be the problem, but there is a solution; simply wipe all the textures in the chunk and reapply the texture in the correct order. Fortunately for me, the area that had this problem didn't require much re-texturing.



More to come if I can find any

[ringtail2390]

I found a bug.. when you go into noggit you can move and modify .m2s normally however when you save you can no longer move the .m2s (but you can move .wmos)

[Steff]

Please use the bugtraker. Take a look if the bug is in and add it if not.

[Zim4ik]

Cool. Does i need taliis to resave adt for m2 models appering?

[Steff]

If you had read the release notest in the other revs......
You should do this and test all functions listed there.

No you don not need to save in taliis.

[Zim4ik]

Yay!)
I`ve got one idea. To make menu in which will be shown all models)

[Steff]

Hwill you display all models in a menu
We will implement a model browser later but there are many other problems we have to solve before.

[lordshark]

Yes, the Render-Bug on W7 x64. My Noggit crashes every time, so i cant test it.

[Steff]

What do you meen with crashs every time. What meens every time. On startup or....?

I develop noggit on Win7 X64 and on my testmap everything works fine. Noggit seems to have problems with special models (m2) so if you move to some parts of the wow world it crash on my pc.
But on other reagions i can move without problems.

[lordshark]

Its the Rendering-bug. Its crash after Loading the map, when it is rendering the objects i think.


Pastebin Code
http://pastebin.com/nQJxdE4g

[schlumpf]

"The rendering bug". Wat?
Also: Stephan, I told you. Stackwalker is useless as long as you don't give them debugging symbols / the PDB. Just completely useless. As useless as "the rendering bug".