Grasshopper

algorithmic modeling for Rhino

hi,

 

has anyone else experienced 'Display Pipeline' errors in kangaroo?

 

I am new to the plugin, so I've modelled a *very* basic series of fixed and unfixed springs to simulate gravity.

 

But when I run the simulation I get this in the command line:

 

An error occured in the display pipeline @ 10:35:29(856ms)
An error occured in the display pipeline @ 10:35:29(856ms)
An error occured in the display pipeline @ 10:35:30(387ms)
An error occured in the display pipeline @ 10:35:30(387ms)

etc

etc

 

I have tried changing between Windows and Open GL in 'Pipeline and Conduits' settings in Options> Appearance> Advanced Settings> Other Settings - doesn't solve the problem.

 

I am running:

- Rhino 4 SR 8

- Grasshopper 0.80004

- Kangaroo 0.044

 

rhino model and grasshopper definition attached....

 

any help would be really appreciated!!

 

thanks,

Jeg

Views: 1509

Attachments:

Replies to This Discussion

Hi Jeg,

 

Sorry I've just seen this discussion. Can I ask - do the demo files with Kangaroo work for you ?

 

I think there may be some issues when simulations explode (if stiffness values are too high for the chosen timestep) and send particles way outside the normal view area, causing problems for grasshopper to display.

hi Daniel,

 

Thanks for the prompt reply.

 

The WALKER and CRADLE examples open and run perfectly.

 

If I open CONFORMALIZE, I get an error message pop-up :

 

Plugin version: 0.8.0004

The archive contains an unrecognized object: Face Polylines {4098ecba-269a-1ced-9ce4-86836dae2101}

This object cannot be deserialized

The archive contains an unrecognized object: Mesh edges {4098ecba-299a-1ced-9ce4-86835dae21c9}

This object cannot be deserialized

Object list read


And the simulation will not run afterwards.

 

Is this because the face polylines and mesh edges that need to be in the Rhino example file are missing? (the Rhino file contains 5 points, and no other geometry).

 

I get a similar error if I open TENSEGMEM :


Plugin version: 0.8.0004

The archive contains an unrecognized object: Mesh edges {4098ecba-299a-1ced-9ce4-86835dae21c9}

This object cannot be deserialized

Object list read

 

If I open one of the examples which is just a GHX file (such as CATENARY), it loads without errors, and a series of Grasshopper generated objects appear on screen - but the simulation will not run. The grasshopper definition says it is "unable to load a series of points". Please see attached JPEGs.

 

sorry for the headache !!

 

thanks,

Jeg

Attachments:

Hi Jeg,

 

Most of these errors sound like they come from a missing WeaverBird

 

http://www.giuliopiacentino.com/weaverbird/

 

Do you have the latest version of that installed ?

 

ah, no I didn't have that installed!

 

I've installed it, and now CONFORMALIZE and TENSEGMEM work correctly. Sorry for the confusion.

 

I still cannot get CATENARY running though. Same problem as before -- it creates a MeshPlane and 4 corner Points in Rhino, but the Pt parameter in the top left of the Grasshopper definition is orange coloured and says "unable to load a series of points" - so the simulation will not run. See the previously sent screenshots.

 

thanks for your help,

Jeg

 



Can you try with this file ?

 

Attachments:

The new CATENARY file works perfectly - thank you Daniel.

 

I wanted to get Grasshopper running, so that I can do some tests ahead of the 'Generative Design for Robotic Manufacture' workshop you and Gregory Epps are holding in February. I will see you then!

 

thanks,

Jeg

Hi Daniel,

I'm going to piggyback on this thread as I'm having a similar problem.I don't think my stiffness values are too high, but I am having issues with the display pipeline as well.

The GeometryOut output is giving me only 'invalid curves'. Although I can use the particles to interpolate new curves as a kind of work around, these don't preserve my data tree structure.

Rhino 4.0 SR8

Grasshopper 0.8.0066

Kangaroo 0.080

Thanks!

Attachments:

Try feeding your curves through a 'Line' parameter before going into the geometry input - that way they get converted and it works.

Also - you can always feed a data tree of points into the geometry input, and they will come out of GeometryOut with their tree structure intact (unlike ParticlesOut, which flattens and removes duplicates)

Thanks Daniel!

That did the trick. I suppose "Line-like" != "Line". ;)

I'm loving the kanagroo plugin! Really great work.

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service