[plugin]Random replacement of components
-
Sdmitch has made a new variant with no Random integrated!
(see second post for more precsion of use
-
A little tut
No limite of number of any components source or target!
You can name all your source components by hand but it's painfull when you have numerous!
So a little trick
Just select Components source and copy this in the ruby console
Sketchup.active_model.selection.each{|c| c.name='Source'}
Your source components are now named "Source"
You can make the same for Target Component
Just select Components source and copy this in the ruby console
Sketchup.active_model.selection.each{|c| c.name='Target'}Edit : In fact for the rename Source and Target you can make the just with the Entity Info Box!
You can now use the random plug (click for zoom)
Of course it's infinite possibilities
You can fill the space with no periodic infinite volumes
you can play with this speedy one
Edit 31 May 2012
A new variant without random is integrated!
-
This is not working for me, Pilou can I send you a sample model by pm and you show how to do it?
-
Of course yes you can!
with a small file (sufficient for the concept) and a save as V7!!! -
Strange how the size of file increases 50% when saving as SU7 from SU 8.
-
Sorry it's always V8 when its arriving at home !!!
-
Here is a SU 6 version
-
This is an awesome plugin... thank you both very much!!! Jo
-
This plugin is indeed great with so much potential. Do you think it could be possible to
make it able to replace child components that are inside mother componennts?
You could do so many patterns just by replacing components inside components. -
coty82
Please check Personal Messages.
-
Hello sdmitch
Thanks for the fast reply! I have installed it but unfortunatelly when i try to use it it just freezes Sketchup no matter if i choose to include child components or not. Is it working for you? -
Update
I am trying to use it like this :
I have two components. One of them is named Target. I select them both and make them a mother component. This is how i was thinking of it to work.
I create another component named Source. When i use the plugin like this it just freezes.
But when i have two componenets and make them a group, and try to use the plugin, nothing happends, but it doesnt freeze neither.
Sorry i cannot reply in private because i dont have enough activity on the forums -
@coty82 said:
Update
I am trying to use it like this :
I have two components. One of them is named Target. I select them both and make them a mother component. This is how i was thinking of it to work.
I create another component named Source. When i use the plugin like this it just freezes.
But when i have two componenets and make them a group, and try to use the plugin, nothing happends, but it doesnt freeze neither.
Sorry i cannot reply in private because i dont have enough activity on the forumsThe plugin does not look for groups, components only. I see that the plugin has a bug, that I will fix, when there is only a single "Source" component. Create a second "Source" component and try again.
Check PM's for updated version.
-
Allright, it works now, thanks alot
! But i noticed that it only works with a single level in the components hierarchy, that is when i have some individual components part of a mother component. But if i include this in another larger component, it doesnt work. Even if i copy the source inside the larger component. Its still great but i wonder if this would be a difficult property to implement?Anyway i have another ideea about it
. In a previous post you said it is also able to replace components based on a rule? For example i have 3 sources 1, 2, 3 And i want to distribute them according to a repeating pattern for ex 11231123, etc. They could replace an array of targets. This would be amazing for creating panelling patterns for facades for example. But it would probably need to work with something like series, to know the start and ending point. Dunno if its possible or how complicated? -
Yes, it currently will only work for one level, mother and child, no grand kids.
As the name implies, it is supposed to be a random replacement.
-
I see there is another version with No random option, how is it working? I tried but i didnt see a difference.
-
@coty82 said:
I see there is another version with No random option, how is it working? I tried but i didnt see a difference.
Component Replacement has a random option which, if not selected, causes the "Target" components to be replaced in order by the "Source" components. The results is dependent on the order the "Source" components are found in the model or selection.
-
@sdmitch said:
@coty82 said:
I see there is another version with No random option, how is it working? I tried but i didnt see a difference.
Component Replacement has a random option which, if not selected, causes the "Target" components to be replaced in order by the "Source" components. The results is dependent on the order the "Source" components are found in the model or selection.
Oh i see. And what is the rule by which it finds the "Source" components? It always gives me the same result but the initial order seems random. I couldnt replicate your example where you have components 1, 2, 3 which then become a repeated sequence in the target. Could you also integrate this no random feature in the version with child option as well?
Thanks -
Can you post an image of results of this new version (parent / child) ?
-
@unknownuser said:
Can you post an image of results of this new version (parent / child) ?
The result looks the same.
Advertisement