Grasshopper

algorithmic modeling for Rhino

Hi,

I think this question is for David Rutten,

when creating c# custom components that generate a high number of geometries, one can experience a general slowdown while previewing output in shaded mode, even on a fast computer.

I do not know how is internally implemented GH display conduit, but  multiple small-sized bounding boxes computing stage may be sometimes slow and could be pre-computed, see for instance :

http://wiki.mcneel.com/developer/rhinocommonsamples/displayconduit

This kind of slowdown kills interactivity but should be solved too by switching manually between "very low quality preview" (wireframed) to highest quality visualization.

How to do it directly inside the component script ? (overriding display conduit implementation)

Views: 422

Replies to This Discussion

Grasshopper has it's own display conduit. And if you're smart, you'll also precompute your bounding box inside your SolveComponent() (to make sure your bounding box do not have to be recomputed every turn.).

You can get a lot more out of this post if you show your current implementation of your component.

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service