Anim8or Community

The current development release is v1.01.1318, January 25, 2018: http://www.anim8or.com/download/preview/files/animcl1318.zip


.............

Previous v1.01.xxxx releases:

Major changes for build 1317 dated January 14, 2018:
Fix #101-017: Issues with Groups and Layers.
   Use group's layer instead of each component's layer when displaying or selecting a group.
   Use the group number of the components in a group when creating a group.
   For multiple group numbers, use any one of them.
Fix #101-018: Reading a .an8 file with a script-based parameteric shape in a group crashes.
Fix #101-019: Script controllers for scene morph targets with aren't saved in .an8 file.
IK effector: Change to not move location of effector unless the user have specifically moved it
(i.e. not when it was moved because it couldn't be reached when the whole figure was moved).
Connected Face Extrusion: Expand cases when new faces are kept parallel to original faces.
Inset Tool: Change to inset edges parallel and equal distance to original edges. Previous behavior (that moved edges relative to the length of each individual edge) is available using the Shift key.
Scene Editor: Add menu command Edit->Bones->KeySelectedControllers.
Fix #101-020: Object Editor: Copy/Pasting a Group with a sub Group doesn't work correctly.


............

I don't know how I missed the 1317 release  , but that's superb Steve. Can the exact same behavior be implemented for the Bevel tool also ?

As ENSONIQ5 said : those boxes in menu have no affect on ART, only on Scanline . Try what slex suggested for Scanline .
There are some issues there like for ever. Not only in Scene ( render ) mode. Step by step Steve will fix them all we hope.

Great video. Well done . Happy New Year !!!

Layers, as I finaly figured out, are very usefull. We just should clear it up a little bit.
First: Steve, it seems that the "0" layer has kind of a "higher priority" by default, always. When you hide that layer, in the material bar, the matterials ( visuals , spheres ) don't show, you can see the names only ( pic.1 ).
Also there's something with the primitive (the Mesh Primitive - see "a mesh" - is fine) created on an empty layer set as default, different than "0". The "0" layer pops up, although other was set as default. When you double click on the primitive and then close ( only by "Ok" ) the parameter window the "0" layer turn off and the ( say ) "1" gets active with the underline under it ( the same result can be achieved by simply converting the primitive into a mesh )( pic.2). Note: when creating two or more primitives without changing the settings, first gets active the " 0 " layer ( first primitive ) and then as an addition the default ( if different than " 0 " ).

Now, very important, about grouping- ungrouping. Ofcourse very important others opinion, how they generaly go around with it.

1)When grouping items of the same layer, it's obvious the group should stay in that same layer  (period) Ungrouping items, that originaly were located on the same layer, should be relocated on that " old" layer and not transfered automaticaly to the "default" layer
2) About grouping items from different layers: first I thought it would be good to prohibit that possibility and to mention, by a pop up window ( So'd just you know window  ), that items can be grouped only when they belong to the same layer and they must be manualy transfered to the same layer before you can group them. Then, ofcourse I understood that it would be stupid, because you loose the ability to group at once a lot ( million ? ) of items without the need to manualy ( !!! ) edit their settings !!! So, grouping items, that originaly belong to different layers should locate the newly created group into the default layer.
And here I bring up again the suggestion, if it is at all possible, to set the " default " layer via the Midle Mouse Button on the tool bar directly. You just click ( MMB ) on the layer you are currrently working in ( better maybe "working layer " - as a replacement to that " default"  ), that layer gets the underline and everything you group will be transfered to that " working" layer. It's the way actually things work now, just you have to go all the time through the Options menu, wich is not practical. Currently, when ungrouping items that originaly were located in different layers, each item returns to its original layer and that's the correct way, nothing should be changed, because when editting often you need to group things just for a sec or two and then relocate everything back. The only thing is that grouping items from different layers, as you mentioned, hidding the layer (of the item originaly ) hides the item inside the group. That should not happen. The visibility of the group should relay only on the layer that the group belongs. Anim8or should " seek " for the group layer's visibility only and only when items will be ungrouped they can be affected by their original layers.

As I remember, cooldude asked a question about your work . Repeating him actually : are there your games, for which you make all those characters, anywhere around ?

Nice. A wireframe screenshot would be interesting.

Where is the fast AA render option?

AA settings, left lower corner . I think it's "on" by default ??

Thanks a lot for the advice guys. I do render from 0, it was just an example. Sometimes the transition between two frames is not smooth. I have tried V1.0b but it also crashes when I enter scene mode. Maybe the scenes too complex?
Thanks again

I use the latest build. It did to mee too. I think I figured out what the problem is. My project was 35 MB at the point the problem accured, but I think the size is not the problem here. When I was in the Scene mode in Wireframe shaded view, everything was Ok ( although a little bit freezy, despite computer's 8 GB RAM ). But, when I changed to the flat shaded view Anim8or crashed !!! Thankfully, the project was saved at the right point and nothing was lost. Then, although I couldn't understand what exactly happened and I did the same mistake again. From wireframe to flat shaded ->> crash !!! Only then I changed from wireframe to solid shaded view and no problem. I forget about it for a day or two and the next time it happend again, but... I almost lost the whole work !!! Suddenly I couldn't go from Object Mode to the Scene Mode at all... crash again. Maybe Anim8or remembered the shader settings ( flat shaded ) and that's why I couldn't get into Scene Mode . I oppened the project in the old good v.0.97d and it worked !!! That means the project was not corrupted. Opening a new empty scene ( new project ) was possible too, but turning to the project scene, crushed it again. Finally, I think I found the problem... it's the new shading settings - >> GLSL. Changing to the old ARB or turning them off fixes the problem

You know what ?!! I know what : I can't modeling !!!  Once I'll clear it all a little bit, I'm gonna start that modeling topic at last !!! 

As about the project : finished the first ( one n' a half ) stage. Everything planned from the start, now is finished.
- The building ( floor, walls, roof, doors )
- Basic appliances ( light switches, suko sockets, heat units, air conditioner and some other, near the doors )
- Lights (ceiling lamps)
- Windows ( with curtains )
Did some furniture, just to see if it looks as I planned . I like it so far. Though, now that's the next stage : to fill it ( appartment ) with all the stuff ( furniture, decorative items e.t.c. )

All the modeling is kind of messy, although I'm trying to keep it as simple as I can, but without a general lack of accuracy ( modeling accuracy is not my goal, since, even if it would be, I would not be able to handle it anyway ).
But one thing I realised for sure ( well, not that I didn't know that ), is that I CAN'T MODELING !!! ( didn't I say that already ? )