Woo hoo! My students are going to LOVE this! Thanks David! --Mitch
If anyone has any ideas on how to improve the trajectory picker, please let me know. At the moment it’s really cumbersome to use for anything more than a small number of different trajectories.
This is FANTASTIC! would love to see if the trajectories can be mapped along a curve during explosion/implosion.
The animation is just a joke really, the purpose of the plugin is to switch between regular and exploded views, not to provide a set of animation tools. I sympathise with the sentiment, but I think that way madness (and feature creep) lies.
Mostly what I would like to do is have better ways to define the trajectories (perhaps also allowing for scaling and other transformations?) and better ways to inspect trajectories already assigned. It’s a bit of a shame that I had to recreate a movement and rotation UI, it would be nice if somehow I could fall back onto all the commands Rhino already provides for transforming objects. I’m just not sure how yet.
I cannot unblock the plugin, Windows 10 & Rhino5sr12
I keep getting this error while trying to unblock.
Thanks, Randy
Wow even Google isn’t much help here, seems like you’re one of the few people lucky enough to get this error. I’m sorry, I have no idea what the problem could be, though I suppose it should work better if I upload an RHI file instead of an RHP file. I shall endeavour to do so with the next release.
Thanks, I may see if a restart helps almost finished my work. Looking to try this out.
Yes, I feel that this will be necessary to make this truly useful. And I cannot see any simple way of accessing move, rotate, and scale information with the existing Rhino tools. I am more leaning towards something like the Bongo UI where you have keyframes that store the information that is accessible through dialog boxes.
Sure, if you have Bongo installed you don’t need any of this stuff. And I’m certainly not going to try and duplicate any Bongo features, that would be pointless since we already have Bongo features through Bongo.
The way I see this Explosion/Implosion logic is very similar to Hide/Show and Lock/Thaw. It’s just two states the object can be in and this plugin allows you to toggle between them. It is complicated somewhat because I really don’t want people to have to actually move the original object, nor do I want the commands to move it. Object positioning can be difficult to get right and messing with it can be a terrible idea if something goes wrong.
I’m thinking now the solution is to create a duplicate of the original object, and this duplicate can be modified at will and eventually deleted. It can persist between commands and all I need to do is keep track of the transformation applied to the duplicate, and make sure to channel them to the original.
it’s really GREAT! Thank you very much!!!
If you accept a wish list, I would like to see trajectories, in a similar way as projection lines in Make2d: do you think it will be possible?
Thanks again
Stefano
I don’t understand. Do you mean dashed lines?
Well I got it working by downloading new copy on my Mac. No need to unblock file now.
Loaded fine, will be playing in a bit.
Thanks
yes, dashed lines on separated layer. But I would not be asking too much and to be rude 
Thanks to reply.
Stefano
Works very well! The functionality here seems like a natural extension of the ‘Named Positions’ panel. At the moment, it is missing the ‘Animate’ aspect of what this provides.
You think you might want to define multiple exploded views that can be invoked by name?
I love it !
Thank you David !
Great plugin, thanks
@wim, @Helvetosaur, @ottocad_com, @emilio
I just uploaded a newer version (first post, I amended the download). This is almost a total rewrite, completely different approach. As a result you can now use regular Rhino commands to define the transformations, but it also means the animations are less pretty.
@davidrutten, I see that there is an Explosion command available after installing this new one but I cannot set a trajectory. The Trajectory command appears to have disappeared.
Yup, see the first post in this discussion for all the changes.