Gravity acting on Voronoi fracture?

Replies to This Discussion

Permalink Reply by peter fotiadis on July 4, 2015 at 4:27am

Assuming that you know how to do it with K1/K2 ... by "capture" you mean something similar with the "animate" slider thingy?

Permalink Reply by Kim hauer on July 4, 2015 at 9:16am

Unfortunately I don't even know how I would even start the process in kangaroo. I was searching for a simple example, without success. :(

I would like to be able to save .3dm frames/sec, then I could render an animation in an external dedicated program. similar to the attached .jpg sequence.  https://www.youtube.com/watch?v=ThvTbiS1Tf4

Permalink Reply by peter fotiadis on July 4, 2015 at 11:36am

My dear Watson:

1. Doing "animations" from K is the easiest of things: just animate the slider that controls the sequence (connect that component to the K simulation reset) ...

... and then get the last item from the produced List using ..er... hmm ... an ultra complex C# thingy like this:

See attached sequence (slider was set to 70 "ticks").

2. For the actual thing (the collapsing simulation, that is), I'll post a bunch of defs that do things like that as soon as I could find them: in what workstation are? why I did them? when? what were the names? what was the directory? the partition? etc etc... (Unless some other good Samaritan ... could provide a similar def).

Moral: Alzheimer, what else?

best, Lord of Darkness

Attachments:

• 234_UAE_animate_Kangaroo_for_Kim.wmv, 3.8 MB

Permalink Reply by peter fotiadis on July 4, 2015 at 11:43am

BTW: Animate slider does this in a given directory (then sample them into some movie maker input panel):

Permalink Reply by Kim hauer on July 4, 2015 at 3:04pm

Watson!.... u mean the IBM guy!....... ur really being way too kind  lol!

Thanks again....I need a few moments to digest your script.

Permalink Reply by peter fotiadis on July 5, 2015 at 12:00am

Anyway ... after searching 123,45 K scripts > found some (in the SquishMeGently directory, what else?).

Get this for a start: the simplest around (a myriad of paranoid/conflicting/overloaded options available: only for the brave).

This can squish even Patrick and/or Bob The Sponge (purely in the Name Of Science).

BTW: With a dose of Karma >  you can even figure out what is required for the vanishing mesh (shape the surface as a black hole and go for it, he  he).

BTW: Designed to work only via spiritual assistance by some (proper) red pepper Vodka.

Load R file first.

Attachments:

• K1_Equilateralize_demo_V4A.gh, 452 KB
• K1_Equilateralize_demo_V4A.3dm, 699 KB

Permalink Reply by Kim hauer on July 5, 2015 at 2:25pm

No disrespect to your avi Peter, but I'm not looking at creating a preview movie scene, (basic geometry, devoid of lighting and shaders).

I want to create this: type of motion https://www.youtube.com/watch?v=M3caDa19PcA
Except in my case a total collapse of the Iceberg. So I really need a series of .3dm frames that capture the motion in Kangaroo.
Now the end result will still be a series of .3dm files with (basic geometry, devoid of lighting and shaders). But the rendering of each .3dm frame, will be handled by 3rd party rendering software. 

Perhaps I'm simply asking too much of Rhino, Grasshopper, and Kangaroo at this point in time.

Permalink Reply by peter fotiadis on July 6, 2015 at 5:17am

Ah! that one ...

... the easiest of things I must say.

Are you ready?

1. See this? You know what is I do hope (from the Sequence in Kangaroo:  I've already explained what this means and what it does).

2. See that? It's a rather simple (kinda) C# that gets the List/Tree of meshes from K1/2, makes automatically suitable layers (user controls names, prefixes, attributes, ... ,cats, dogs etc) and then bakes each item (a Mesh[case: List] or a List of Meshes[case:Tree]) from the mesh List/Tree to the corresponding layer.

3. See that? Well ... it's rather obvious what is is.

Moral: piece of cake (but handling/controlling the C# that does this ... is not, he he).

I'll try to (over) simplify the Dark stuff and I'll post it here.

best, Lord of Darkness

Permalink Reply by Kim hauer on July 6, 2015 at 1:13pm

Interesting...... I see another C# solution in the works, I will stay tuned! :)

Permalink Reply by peter fotiadis on July 7, 2015 at 12:14am

OK, get this (over)stripped version:

1. I've removed a lot of code related with nesting (meaning you can't manage "scenarios" : a parent layer, say, VERSION_x owns child layers that contain a given sequence of meshes for a given K simulation). I've also removed a rather complex K slider "state" management capability ("inquire" a slider via his nickname > get the value > store it in a Tree > create "slider value(s) scenarios" > blah blah).

2. Removed the Tree capability: works with only one meshList (from the Sequence K component).

3. NEVER have the K simulation mini dialog open and toggle Sequence ON:

4. Control the baking using ONLY this toggle in the yellow group:

5. Rhino is not Modo ... but I would strongly suggest to render the layer content(s) [the "states" of the simulation, so to speak] inside Rhino: after all it's just a very simple object in question without volumetric/occlusion/... rendering and numerous other WOW Nexus [Modo rendering engine] features/capabilities. 

6. Replace Ice Berg with Bob The Sponge.

may The Force (the dark option) be with you.

Attachments:

• Bake_meshes_from_Kangaroo_V1.gh, 337 KB
• Bake_meshes_from_Kangaroo_V1.3dm, 82 KB

Permalink Reply by Kim hauer on July 7, 2015 at 11:13am

I thank you for your effort Peter!

I will screw around with your script shortly :) 

Permalink Reply by peter fotiadis on July 7, 2015 at 12:25pm

Be my guest, he he

In fact ... I did nothing other than removing "some" lines of code: I use things like this (+ bake in/to nested blocks) to talk to CATIA/AECOSim.