
So a DC door component would have a behavior attribute with a formula like: “onClick(Animate(…))” so that the door swings open when the user clicks it with the DCInteractTool.īuilt-in plain-Jane scene animations, cannot stop and “click” DCs. (They are actually just a component with a special named attribute dictionary, that has specially named attributes and attributes that are formula.)
Revizto tutorial pro#
You can code dynamic components in Ruby, but the nifty dialog wizard to create them, is a Pro Only feature. (It looks like a browser’s hand cursor clicking a link.) The Dynamic Components functionality is actually an extension, but it is distributed with all editions of SketchUp. I need to portray a succession of doors openingĪt this time, built-in component animation, can only be triggered by the DC Interact tool.

The model itself is the same in every scene however, parts of it are visible in some scenes but not others. By turning the visibility of each door instance on and then off in sequence through a series of scenes (typically using layer visibility), you can create the illusion of motion, like some old-time stop action animation, but at the expense of adding a bunch of extra geometry to the underlying model. The only way to cause the door to appear to swing open or shut is to superimpose a series of instances of the door component, with each instance shown at a point along the swing arc.

The scene simply provides a “filter” through which to view the model using some set of display attributes, including point of view, visibility of certain layers, lighting, shadows, etc. As for the model–it’s the same model in every scene if you open the door a crack in Scene 1, it’s open a crack in all scenes. SU scene animation is not intended to cause models to “move,” but rather to cause the camera to move through the model.
