Anim8or Community

Please login or register.

Login with username, password and session length
Advanced search  


An update to Anim8or, v1.00b, is available with a few bug fixes. Get your copy HERE. See the "ReadMe" file for details.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - chuft-captain

Pages: [1] 2 3 ... 5
General Anim8or Forum / Re: Arrgh! Hard Disk Crash!
« on: November 12, 2018, 01:41:04 pm »
I've made a lot of progress. I'm in Italy now but will return to Califonia in a week and should have an update not too long after.
Great to hear Steve. Along with your re-writes, I hope you also found a solution for that frustrum issue we discussed.


PS. Looks like they don't have the letter "r" on Italian keyboads either. (Hope you make it back safely to "Califonia" though!) :LOL:

General Anim8or Forum / Re: Arrgh! Hard Disk Crash!
« on: August 28, 2018, 05:02:54 am »
BTW Steve,

Sent you a PM / Email about an issue we discussed a few months ago. (No panic obviously  8) )

General Anim8or Forum / Re: Arrgh! Hard Disk Crash!
« on: August 26, 2018, 03:47:46 pm »
I can sympathize Steve as this has happened to me in the past.
On the positive side, I find I usually write better and more elegant code on the second attempt!

Selden makes a good point.

We would not want to break the export scripts!

Fortunately, though, there is a workaround: Object/Point Edit's "Drag Select" option can be used to select all of the surfaces in the current Object, including those that Ctrl-A doesn't select.
That's interesting because in the scenario I describe above, the drag-select does not select the group in question.
No hurry for me to get a fix though Steve, because I'm not really doing any actual modeling lately ... just using some models I was playing with last year, to test your new code.

Also, to Selden, have you considered importing the STL's directly into Anim8or to see if there's any difference in how they're handled when not converted into OBJ format first?

Yes, I suspect you're right. It's probably always been the case as you say (I've confirmed it as far back as build 1269, so it seems this would be a new feature.
I'm not sure how hard this would be for Steve to implement, but what do other's think of the idea to be able to export only visible layers?

It looks like I broke this in my latest changes to groups. I'll fix it.
Thanks Steve,

... although FYI I think this has been happening for a while, maybe as far back as build 1269 or earlier, so you might have to look back a ways to find the fault.

Any groups involved? ... in my case I definitely saw a difference in "selectability" between meshes and groups... which makes me suspect some issue with group-layer memberships.

YMMV - well obviously it does!  ;D


I've seen something similar. I haven't yet worked out exactly what's going on, so take my comments with a grain of salt.
I think this is related to the Group/Layer changes. It looks like there may be still some gremlins to work out.

In my case I had one group of meshes in layer 6, and another group in layer 0. The (faces of) the groups/meshes in layer 6 were selectable, but (faces of) the group in layer 0 were not.
I disabled the visibility of layer 6, and ungrouped the group which was unselectable. It disappeared, so I re-enabled layer 6, and there were it's constituent parts (whose faces are now selectable). However, if I re-group those objects, they automatically return to layer 0 (at least their group does) and once again, the faces are not selectable.

So there seems to be a few issues here.
1. The sub-meshes seem to retain a "memory" of their previous layer membership when grouped, and on un-grouping, they return to that layer (in this case layer 6). If I then immediately re-group those objects, the new group returns to layer 0. The combination of these 2 things it seems to me makes it impossible to permanently change the layer membership of a group of meshes, because they retain their memory of another layer instead of inheriting the layer of the group.
IMO, if you move a group to a different layer then the sub-groups and sub-meshes of that group should also inherit that change, whether they remain grouped or are subsequently un-grouped.
2. It seems to me that the fact that the faces are not selectable has something to do with the fact that they are in a group. Is this also the case with you?
When I ungrouped, the faces of the ungrouped objects became selectable (in layer 6), but these were also grouped objects themselves, which again suggests to me that this has something to do with the object layer not matching the contained object's layer(s), rather than simply the fact that they are part of a group.

None of this I'm sure of ... more testing is required ... but I hope this helps.

EDIT: Bingo! I've just worked it out.
As I said. the objects contained in my "unselectable" group seem to think they are members of layer 6, even though they are grouped in layer 0. When layer 0 (the group's layer) is visible the group is visible, and the faces are also selectable, BUT ONLY IF LAYER 6 IS ALSO ENABLED. If layer 6 is disabled, the objects remain visible (because they are members of a group in layer 0 (which is still enabled), however they are not selectable because they "think" they're still members of layer 6 (which is now disabled).
It seems that the "selectability" of objects and their faces is linked to their layer membership (and it's visibility status) ... (probably as it should be), but, because they seem to be retaining their memory of layer 6 membership, they are not selectable when that layer is disabled.... even though they are grouped (and visible) in layer 0.

The selection issue, only seems to be an issue for "sub-groups", "meshes" however still seem to be selectable when part of a group in another layer, even when their own layer is disabled. It seems to me that layer membership is not being propagated down and applied from the top-level group to the sub-groups.

Anim8or v1.0 Discussion Forum / Invisible layers are always exported ...
« on: February 02, 2018, 10:24:08 am »
One thing I have noticed recently (prior to this latest 1318 build) is that when exporting a model with hidden layers (into CMOD format) it seems that the hidden layers always get exported regardless of their visibility. This, to me seems counter-intuative, and caused a few duplicate mesh issues in exports, until I realized what was going on.

IMO, what is exported should be only what's visible at the time (otherwise unexpected extras can end up in the export).
It would be good to be able to easily export an assembled model as a series of sub-models (if so desired) by just enabling the desired layers, and disabling all other layers, then exporting the partial model.

This has a lot to do with my workflow, so YMMV. The opposing argument would be that users would have to make sure that all inhabited layers are visible if and when they wanted to export the complete assembly, rather than in parts.

I hope this makes sense ... what do you think of this idea?


I just did a very quick check of the Group/Layer changes, and on first glance it looks great!
Individual and combinations of layers can now be displayed or hidden at will, regardless of the status of Layer 0, and it appears that Layer 0 is no longer treated as a special case. (This I agree with completely.)

I'm sorry, I don't have time to test these changes in depth at the moment, but on a very cursory first glance it looks really good, and I'm amazed you got this done in such a short time since Christmas! Thanks a lot!
I'll do some more in-depth testing of the interaction between Group/Ungroup actions and layer memberships when I have more time, but it's looking good so far.



Sorry, I appear to have hijacked this thread a bit. If you want to keep this thread on topic, you can split off all my suggestions into a separate thread if you like (especially as it turns out you've already implemented most of my suggestions in some form or other a long time ago!)


No need to apologize,

Tried that out, and it seems to do pretty much what I was suggesting to Steve, so it looks like he has already long ago implemented this, just in a form which I was unaware of.
(There are large sections of Anim8or functionality that I have barely touched on, so please excuse my ignorance.)

Thanks for the guidance. I learn something new about Anim8or every day, and it just keeps getting better and better!


I can't find that button in my version (latest dev build 1318).
The only button that looks vaguely like it is in the Coord section (group of three) but when I hover over it, it says "World Coordinates <w>".
Is that the button you meant?

EDIT: Forget that, I think I just found the button you mean (just above the other one) ... sorry about that. I'll try that out to see it's effects.


That's good to know ... but to borrow a phrase by Slartibartfast from Hitchhiker's Guide, "I don't know this 'Axis' mode of which you speak".
The only "modes" I have ever seen are Object, Figure, Sequence, Scene.

(I did say my knowledge of Anim8or features was not that broad, didn't I?  8) :D :D ::) )


Pages: [1] 2 3 ... 5