Grasshopper

algorithmic modeling for Rhino

Hi,

I would like to ask about Rhino 6 WIP preview in grasshopper.

I noticed that my previous components for mesh preview also some of human plugin components displaying geometry in a slow manner comparing with rhino 5. 

Before I was overriding bounding box, and displaying mesh and wires through args.display... Did  the display procedure change?

If yes is it possible to get an example how can I properly display geometry from component?

Views: 468

Replies to This Discussion

If you find that calls to Rhino.Display.DisplayPipeline.DrawXXXX() methods are slower than expected, probably best to ask on discourse.mcneel.com

There have been a lot of changes to the core display and I think a lot of them were meant to improve performance for Rhino document objects that could have useful display data cached. These changes will undoubtedly affect the drawing methods. I think Steve is actually going to focus on GH preview performance next week or otherwise soon, so it would be a good time to mention it to him.

Thank you.

I would like to ask one more thing about grasshopper and meshes.

When I internalize mesh with ngons. I close rhino or copy internalized component it loses all information about ngons. Do you know why this happens?

Hey Petras - if you have an example file where human in the WIP is behaving more slowly than in rh5 I'd love to see it :) 

There are weird stuff, like I have my gh geometry displayed without any preview components and its display is gone once I use your components to show 2D text.

And before I used to display geometry through overrides in C# , that resulted in quite efficient performance, because grasshopper used to be slow when outputting too many elements. I did not compute anything in overrides , but when I rotate camera in rhino it is slows the performance. In rhino 5 my preview components seems to work fine.

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service