New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
instancer full copy/deep copy loop rename continuously creates objects #119
Comments
The problem here is that the object instancer has to use the object names to identify the objects and if it cannot find the objects it will produce more, and more, and more.... |
I can see that above is not a complete solution,as it does recreate the instance, just not forever. Problem being that list is just using plane names. And there are other ways. so here are two :
*1. Create ID Blocks. I can see that such ID Blocks are considered a user of that data and get updated correctly if you change names. They are the appropriate way to reference something in a driver (This may also answer how to not use hard fake user on a tree but actually allow deletion and eventual purge on file close.) May be also used where in the object node the respective obj is not updated if renamed, but if this kind of reference was made it would be... Another example, but also as alternative list using a type of id block already existent. *2. Use object groups. (tied to the anim node container also?) there is a thing with obj groups that they actually work as object list. They have an order of the objects in the group, the order they have been added to it or the order of selection if add bunch and with manual renaming it works very well, object still there and does not change the order. note that the groups are also shown across all scenes and can be referenced across files etc. (so much about naming of the groups now.) |
Not that I don't want make this node a bit more advanced and that it cares about renaming etc.. and one of your methods may also work. I'm not sure how experienced you are in programming but maybe you can try your idea out yourself. And see if it works as you expect. Also I think that you shouldn't care about the names of the outputted objects... If you need more control you should duplicate the objects yourself using shift D or whatever. Then put them into a group and use the group input node. This way you have much more control. The only thing missing from this approach is that you don't have an 'Amount' slider because you have to deal with the amount yourself. Is this possible? Here are some things the object instancer has to care about:
lets say we use your group method: if the user duplicates an object of that group it will be in the group as well, the node will notice that there is an object too much, but how does it decide which one to remove? Same with keying sets I guess The holy grail would be to have custom properties which reference ID properties, but this isn't possible and propably will never be |
Thank you for the patience and explanations. First thing first: my programing skills are 0. Nada. As for scripts, I did scripts for movies, literary kind, ok? Thus, probably some lack of understanding for some things. Yes I may have a technical and mathematical side and I have used quite a bunch of soft for 3d and cad. And I even teached such. Back on topic: For this operation, probably separate text is more appropriate. As it has manual refresh. (The actual operation is supposed to create the alphabet as separate objects, for blender font) I will further investigate other ways to do this. I did not use the update settings node yet. Dunno if that is supposed to debug etc or it also has limiting possibilities (like not to refresh..) on the bug itself:
Then again I will explore this id/rna a bit as much as my skills will do. Not for instancer as that is too much. Very probably it is yet another area that is over my head. At least I know that much that there is no special place in the file to store some data, but in a scene or obj or another block like these. And I absolutely support the idea that it should create as few as possible custom things (that don't work in the default BL) ps. hope not to bother you too much with these long mumblings. |
Just that.
Is trying to make some instances with name001 002 ...00n name9 00n again and again?
use to work, and I did just that renaming a while ago where the instances had only random names
in the blend try to connect the list len to instances to see (and prepare to kill the nodes to stop it ...)
https://drive.google.com/file/d/0BzzAoBwXO8dsa3NFQUlpam5HVXc/view?usp=sharing
The text was updated successfully, but these errors were encountered: