Posts made by pcmoor
-
RE: Animer deux composants en même temps /animate two components
The drawer and face has to be within the component that is copied, most likely you need a handle too. So place all within a "opening" component and copy this as needed.
May I know if this is a one / two off project or are you hoping to create a collection?
-
RE: Animer deux composants en même temps /animate two components
create a separate attribute and reference that
https://forums.sketchup.com/t/dynamic-components-animation/120381
Si besoin je peux partager mon composant dynamique afin que vous puissiez naviguer dedans.
can do -
RE: New to DC: topic for my simple questions to the pros
The condition is either true or false, 0 or any negative number is read as false whereas any positive number is true.
A bit of a short cut in logic.The space is not required for mathematical functions, just there for my own readability
-
RE: New to DC: topic for my simple questions to the pros
Hi
To work out the number divide the opening by the whole door size and convert to integer
To get the remainder take this number times the size from openingFor door lenx, use condition if remainder then the last copy (= copies) is to be remainder
There were some issues with the geometry and scaling, first applied lenX to two faces, then had to make a group of the edges so that it obeyed the formula rather than its natural scale
made outline to size to opening, added some copy function to the support
-
RE: Automatic naming of sub-components
Instance names are automatic updated in outliner, DC option and attribute dialog, also labels in layout. So my recommendation is to use component names for generic terms like panel, board, box...then their #numbers are somewhat redundant. And specific for instance names
The attached file contains a DC, select one of the instance name for any of the generic panels in outliner. Change this instance in Entity info and you will see that its updated in the option and attribute DC dialog. There is a report attached to the file and this is reference to the instance name too.
The parts are made from one DC panel that is placed using a version of the rotation rectangle script, to place, orientate and scale as require, plus excess to the options.As you would be aware, cutlist 4.1 reports component definition names. However you can change the cutlist script to use the instant names if available otherwise the component name by going into the ruby file and replacing compName = c.definition.name in the reporter
if c.name == "" then compName = c.definition.name else compName = c.name end
save, if sketchup open, close and reopen for the script to reload,Note if you do decide to use the "power" of instance names for your DCs, then you cannot use the "Name" attribute in the component info section as this disables this function, plus when first creating a DC this does not work, until you have "saveas" it to a folder and inserted an instance.
(You can use _name in the value section to reference the existing definition name if require for an attribute like description = _name & " " & lenx & "x" & leny )If you wish to create the DC placing script, please ask, then will show what I use, but note the ruby,though works is still at a basic level, I am still learning and do not have the expertise of some of the others on this forum.
-
RE: Simple dynamic windows, doors, skylights etc
Hi Franz,
DCs involving more than one level will become unique if internal sizes or positions are changed, its unusual for animation to trigger this, unless the operation changes the original size or position of a part. So please upload the DC so can offer some explanation or solution.
Rather than relying on the definition name, I suggest using the instance name to document your project.
https://sketchucation.com/forums/viewtopic.php?f=289&t=71346
https://sketchucation.com/forums/viewtopic.php?f=289&t=70511&start=30
Simplification using ruby scripts is another approach, also consider some developed ruby solutions like FlexTools extension
Philip -
RE: Componentes dinsmicos para carpinteros
There are two ways to create this, one is to use parts and hide the common edges and faces, the other is to use cutting components
In this case its parts and hidden faces/edges as shown @ 2.04 on videoyou can see the outline of the end face/component when the offset is matched to the thickness with a given back thickness,
When you create such. I recommend you use solids then can outer-shell the subs to create a whole (retaining the parent for data and ability to reinstate with swap with its definition)
cutting components work if the edges are hidden (outlines can be added as dynamic groups or components)
Either way, it involves making sub components or (I prefer) groups to suit your purpose -
RE: Componentes dinsmicos para carpinteros
can not see anything on the video, can you upload link to you tube?
-
RE: Nested dynamic components
The rotation is causing a problem as you are going into each level to make the interaction.
You can isolate the effect (X to Z swapping) by making another group / component of the geometry then move that in the rotated context.Generally I would use a switch on one of the levels to animate all the actions using conditional statement to give priority. However the attached solution may suffice your needs
-
RE: Nested dynamic components
On the bottom of the return full reply (not quick), second tab, choose upload attachment. Then choose file button, the little plus sign if more than one file, then bottom button to add the file to your message
-
RE: Nested dynamic components
The trigger point(s) to any animation must be all on the same level, then any changes referenced up or down.
There is no limit to the number of nesting provide the data is passed through each levelIt would be easier to advise if you post the model
-
RE: 3D Warehouse
you could download make2017 and run it along side
https://www.sketchup.com/download/allnot sure if this allows you to saveas to 2015, but worth a try
-
RE: New to DC: topic for my simple questions to the pros
saveas the DC to a folder then bring it into another file, for some reason it does not initially work within its created file, after that, should work, regardless of the number of changes, the references are still maintained
-
RE: New to DC: topic for my simple questions to the pros
you can use the component instance name to give each instance an unique name which is reflected in all the dialog, which is the natural inbuilt way
otherwise set
Name = _name
in the DC then
use a button from the toolbar extension to fire the code snippet to alter the _name attribute, which reads the current definition name, updates the original name to update the option dialog -
RE: New to DC: topic for my simple questions to the pros
The components instance name is already tied to both the attribute and option dialog, this can be updated on the fly. This works if you do not use the name attribute and only after loading the component.
Otherwise the component definition name can be accessed via a ruby script and placed into an attribute value.