Yes. Instances inheriting animation would be awesome. Can it be toggled on/off?

Cool find! Radio & Site!

Scott me up beamie.

@rich o brien said: An interesting dissection (...) Looks good. Thanks, Rich. @pbacot said: (...) one thing I am sure of is the Republican elite are going to hate it if Trump gets elected. Yeah. I'm sure there's quite a few Republicans who fear Trump'll run the GOP into the ground. They might be right, too.

@rich o brien said: I was testing the feature. Didn't put a lot of thought into it. But for 25secs of render time and to get a 360 pano to easily share it's a great feature True! It's excellent!

@pilou said: A visual effect by example can be a Blue face at the beginning becomes a Red face at the end of the Animation? Pilou brings up an interesting question. Is there/will there be a way to change the color/texture of an object? Once again, I have an interesting thought related to my car wash (isn't it always about my darn car wash). As the car goes through some of the equipment, like the spray or foam equipment, I would like to be able to apply a different texture to the car (like a foam added to the car or changed the color just a little to get the effect of the water, foam, or chemical) and then change it back after the car goes through the dryers/blowers. Or maybe the car comes in with a bunch of mud/dirt on it and gets "cleaned". Just a thought Careful hear beta team, we are headed toward a full move/gaming engine.

@rich o brien said: Why does the Sequence Editor duration always list 2.0s if the Unit translation is less or more? Sequences have a nominal duration when created most of them get 2 s by default view camera and visual effects get 0 second by default However, when you insert a sequence in the timeline, that is a clip element, it becomes an instanceof the sequence and you can freely change its duration (and some other parameters). Keep in mind that a Sequence is nothing else than a reusable Definition. If you remove a clip element, the Sequence (i.e. Definition) remains. You can delete a sequence indeed, but via the Maintenance dialog box. This is similar to Sketchup Component. You create it at a given scale and in a given position, but most often, you would instantiate it somewhere else, with a different scale, and you may reuse the Component Definition as several instances, each with different scales and positions. The nominal duration of a sequence is the duration of its instances unless you change it. Animator uses the same hierarchical recursive framework as Sketchup Components. Not always obvious in Sketchup for newbies, so not always obvious in Animator! Fredo

Currently, a new movement or camera gets the proper name by default, unless you change it. When you open the Movement Editor, the sequence is named "Movement_X". But as soon as you select which type of transformation, say a Translation, the name becomes "Translation_X". However, if you exit the editor with the saved sequence, the name remains "translation_X", even if you later change it to be a rotation. The issue I raised is about that and the inclusion of parameters in the name. That's why it's a good habit to give your own name to sequences. Similar to what we should all do with the naming of Groups and Components in Sketchup. What I can do anyway is to have a consistent numbering, so that the second translation created is named "Translation_2" by default. Fredo

I suppose I'd better not edit his code.

Maybe a custom method to read SVG files and draw them in openGL could be doable.

That promo video felt so BS... I'm curious to see how it actually works with the Hololens.

http://rengacad.com/en/ Bim system!

Ah Paris! [image: 338cbef52d6de35b04b5b1dcd370fe69.jpg]

Each definition has a unique name. Editable in the Component Browser etc... A definition can have one or more instances placed in the model. If you use 'make_unique' on one [or more] of several instances, then the instance[s] gets a new definition, duplicated from the original, with its name getting an incrementing suffix auto-appended - e.g. 'widget' becomes 'widget#1'... Any instance can also have its own individual name [set in Entity Info] - these instance-names are not directly connected to their definition's name. Unlike definitions instance-names can be repeated and shared by several instances, and even instances of different definitions !