Hmm... that is strange, if you convert to plain mesh SUbD should not be interfering... Can you show a video/gif of what you observe? Maybe we are talking about different things?

This thread may be of interest. http://sketchucation.com/forums/viewtopic.php?t=43257

cool, I am glad I learned something new today. Thank you all.

I love it

I'm keeping mine as an incentive. I'm determined that I'm going to be able to wear it at some point this year without looking like the love-child of a Smurffette and the Michelin man.

I think this link is supposed to be a sort-of open invitation to G+ - only 150 invites left... https://plus.google.com/_/notifications/ngemlink?path=%2F%3Fgpinv%3DEFagzNRbraQ%3AXlAIo30CCFQ

[image: THpH_25249-Gurande.jpg]

@Remus: yes, you can trigger several animations with one click by separating them with ; but all these animations start and end at the same time. therefore the 'Time Line' approach is more suitable for some models. @Chris: damn! I dimmly remember your ping pong component. so there was no need to figure it out on my own on the other hand. it was a lot of fun @Thomthom: my goal is a bit more humble - an armada of robots cleaning up my flat is enough for the time being. and I should be careful with 'taking over the world' plans. I am German and I dimmly remember this moustached guy...

Choppy here as well. SU 7.1M1 Processor Intel(R) Core(TM)2 Quad CPU Q9650 @ 3.00GHz Memory (RAM) 8,00 GB Graphics ATI Radeon HD 4870 X2

Also with Walkabaout 3D http://www.walkabout3d.com/# note that it works with LightUp, too http://www.walkabout3d.com/Tutorial/lightUp.php

unfortunately that doesn't seem to be working for me. imagine the following situation: you have got a 'onClick' function assigned to a subcomponent. the function animates a Variable. and now I want this variable to multiply the length of another subcomponent (or even the daughter of another subcomponent). somehow I don't seem to get this to work... [Edit] I just checked again. the value of the subcomponent's variable isn't passed on to the parent component. neither does it reach another subcomponent. to me it seems values can only be passed down the chain, but not up. unless you have to use a different way of referencing it, than 'subcomponent!variable'...

yes, SketchUp 7.1 on a Windows 7 laptop. (although I discovered a few minutes later, that I didn't have textures enabled. when I redid it with textures, it took about 20 seconds...

first image is awesome! the simplicity of the building really works... great graphic quality to it... and the yellow tone/grain..

Let me rephrase that: Thanks for pointing out a great plugin, Pilou!

thanks Anssi. it seems to me though, that your Dynamic Component works if you scale it in only one direction. the other direction is unscalable. that was the problem I was fighting with. now we needed a way to implement the same behaviour to both sides.

You can leave the plough at home, a hair dryer would probably suffice now.

cool, it was Zermatt! thanks holgster. although it doesn't work properly with my new laptop (probably have to check my graphics drivers). well, and Quest3D is a bit mighty for most architects...

@plot-paris said: [Edit] Damn, wanted this thread to appear in the 'Wish List' section of course. but now that I come to think of it, maybe that could be a sensible and realistic ruby request. could one of the moderators move this thread to the ruby-section? that would be fantastic. and sorry for the trouble [] I could!ve moved it there ut as there seem to be a couple of good solutions, I decided to move it to the main SU Discussiosn. (<--- no "special" meaning for the wink)