3D voronoi skeleton definition not working on final output

Hey, I was introduced to GH about a week ago, wondering if anyone can help me out.

It's someone else's definition but my own doesn't get the results I require.

The mesh attached isn't the final I wish to apply the definition to, but it allows me to understand if it will be of any success.

The file attached under " test" are my efforts in trying to achieve my desired output. However, the bases of that uses a box and not a mesh. So I scoured the forum here to discover someones definition that achieves it with a mesh.

However, only half of the definition works, I cannot get the final output

Many thanks in advance.

Attachments:

Replies to This Discussion

Permalink Reply by peter fotiadis on February 25, 2015 at 1:34am

Added that TSpline "desk" in the def. Your desk is ready to support some very expensive glass (one flat area + the other "end" = sufficient enough). But there's some Z difference that may cause "issues", he he.

Attachments:

TestVolonoiDesk_V4.gh, 52 KB
TestVolonoiDesk_V4.3dm, 2.6 MB

Permalink Reply by peter fotiadis on February 25, 2015 at 2:07am

Here's the 1m(*) idea: we could create an avant garde design company named "GetTheMoneyAndRun"(C)(tm) : then we could sell such desks at around 666,66 dollars (per tube) ... and buy TSplines from AutoDesk. Genius or what?

Monaco wait for me.

(*) m for micron.

Permalink Reply by Kim hauer on February 24, 2015 at 3:46pm

Kyle:

1. Your Test.3dm file appears to be an imported .obj file not a native file created in Dhino, sorry I meant say Rhino.
Any program that still uses the old Autocad command line structure, clearly show it had not moved forward since 1988. (just joking, I don't want to wake up the old timers) :)
2. Your Test.3dm file is also not "water-tight" meaning its has an opening in the mesh, this affects how Grasshopper components will work when they encounter your geometry.
3. Creating "water-tight" geometry did not become a big deal, until 3d Printing came on the scene.

Permalink Reply by Kyle Koops on February 24, 2015 at 3:54pm

That is understandable, I've always known rhino to be very forgiving though!

Permalink Reply by Kim hauer on February 24, 2015 at 5:46pm

That's precisely the common misconception about using Rhino. As long as you build stuff in Rhino, Grasshopper will work. However importing geometry and then applying Grasshopper wont work. A Mesh definition is only a word, not universally agreed upon by 3D software companies writing software.

And that's the reason that Grasshopper is so difficult to learn, Grasshopper would be half as difficult to learn were it not for all the old left over AutoCad way to doing 3D. Its no wonder AutoDesk finally went out and bought Revit.

As I have said before: If David were to write a stand alone Python version of Grasshopper, or plugins for Catia, SolidWorks, Houdini, and even Blender which is free, he would be making better use of his passion for Grasshopper and its use universally. Most if not all state of art programs now allow programmers to write Python API addons.

Download a free copy of Moi http://moi3d.com/download.htm.... See how easy it is to use, compared to Rhino.

my 2 cents!

Attachments: