Grasshopper

algorithmic modeling for Rhino

100000 springs real time with FlexHopper and FlexCLI

This rough preview shows the functionality of the Grasshopper plugin FlexHopper (to be released soon).
FlexHopper brings the physics simulation engine NVidia Flex to Grasshopper. This unified particle engine allows for very fast particle based physics simulations.

Views: 405

Comment

You need to be a member of Grasshopper to add comments!

Join Grasshopper

Comment by Benjamin Felbrich on July 13, 2017 at 8:37am

@Petras Awesome! thanks a lot I'll implement it soon..

Comment by Petras Vestartas on July 13, 2017 at 8:34am

These ones:

Comment by Petras Vestartas on July 13, 2017 at 8:30am

For me drawing geometry through component when overriding the preview fastest options are two:

1. Pointclouds

2. Array of lines.

Somehow when avoiding looping in preview and just displaying one chunk of data is very fast. But to my knowledge it is only limited to pointclouds and array of lines. It was similar cases when having scripts in processing it ran very fast and using them in gh resulted in slower display. But once displayed through pipeline in one chunk performance was actually faster than processing display.

Comment by Benjamin Felbrich on July 13, 2017 at 7:59am

Hello!

Ángel, yes the display is definitely the bottleneck. Solver and display run in parallel so the slower one dictates the resulting FPS and usually the solver is much quicker. This was done in RH5, I'll give the WIP a try. Thanks for the info.
As you can see, especially drawing the vectors is very slow, while drawing GH_Mesh and GH_Line is pretty okay.
Anders, the solver outputs a Flex object and it is up to the user which objects to unpack and draw from this Flex object. What is actually the fastest way to draw something in the Rhino viewport? I guess, one can access the viewport directly somehow, but I didn't look into that yet...

Comment by Anders Holden Deleuran on July 13, 2017 at 6:49am

I think you're probably right here Angel. Another bottleneck might be outputting all the particle data from the solver component (especially with scripting components and/or not wrapping the data in Grasshopper.Kernel.Types).

Comment by Ángel Linares on July 13, 2017 at 6:34am

Hey! Nice project, correct me if I´m wrong but is it not the Rhino display pipeline the bottleneck in this simulation? Is it running on RH5 or the WIP? I found an incredible improvement in performance in the WIP. If you are using RH5, give it a try!

Translate

Search Grasshopper

Photos

  • Add Photos
  • View All

© 2017   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service