-
Notifications
You must be signed in to change notification settings - Fork 84
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
Hang up with large grid sampling #57
Comments
You have to be careful with that. With a density of 10, in a single cube of 1 * 1 * 1, you end up with 1000 Position3D nodes. Scale that cube up to 10 * 10 * 10 you get exactly 1 million nodes. That's stored in a plain array for now so yeah it's definitely going to hang up even before trying to add them to the scene tree |
@HungryProton |
We can do this on a node level or on the whole graph level. Either add a warning and a confirm button on each nodes that potentially takes too long to finish I don't know what would work best from a user point of view, having the warning on the node itself makes it easy to know which one is problematic but also clutters the graph view. Let me know what you think about it or if you have another idea on how to handle this |
Oh yeah an error/settings panel sounds super useful. And yes bringing the problem node into focus sounds awesome. Perhaps do that automatically for the first error posted. |
That could work, I think there's no built in way in Godot to store plugin settings so they will be stored in a config file at the root of the plugin folder. I'll see what I can do |
I was using
Create point grid
and supplied (as a part of trying to figure out what to do) a large size vector (10,10,10) and a large density (might have also been 10?) and Godot went unresponsive.The text was updated successfully, but these errors were encountered: