-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Huge number of Particles - Performance Tipps? #111
Comments
Try the VTK to Blender Particles node. It allows point instancing. Docs have an example workflow, it should work if you get all the buttons pressed exactly in right order, but it's somehow very sensitive, can break upon any change. |
Youre right, its very sensitive.... thats not much fun to work with, however, it works! And considering the amount pf particles i ask it to render it is also very quick! Thanks so muc @tkeskita, this again helps me so much! Do you think there is any chance we can introduce motion blur into the particles? |
Hi, |
I think i found something. I am gonna give it a try again, lets see if that works. |
Hello @tkeskita,
I'm currently exploring the possibility of rendering approximately 10 million particles and am considering using Blender as an alternative to Paraview.
In Paraview, my approach to visualising particles involves either point gaussians or points themselves, which is notably efficient. However, this method restricts me from leveraging ray tracing capabilities.
I'm curious if you're aware of any strategies to reduce the mesh count when working with particles. Typically, I would opt for the Sphere-glyph representation, but this leads to an exorbitant triangle count of around 640 million, which is far from ideal.
What are your thoughts on this?
The text was updated successfully, but these errors were encountered: