If my calculations are right, generating a sphere that has a radius of 64 nodes would require somewhere between 2-3 mil operations. A sphere that big usually requires running the command 4-5 times, add to that, i never know when its done and needs to be run again except by looking at my FPS. I tried adding progress indicators but that only resulted in smaller portions of the sphere spawning each time i run the command.
How would one go about splitting up large operations? Ive thought of maybe seperating the functions from the actually node placing, but that would require first writing the changes to a multidimensional table, and then processing it. Though i have a feeling such large tables would segfault :-/
FOSS gamedev and creative worlds
This is a mostly frozen copy of the Minetest forums through 2017. If you know phpBB3 and would like to host any G-rated forum here, you can email: me@minetest.org If the email doesn't work, find out who's taken over Final Minetest from OldCoder and email them to get write access or an admin account.
I should have set this up years ago. But it's no tale of woe.
Whether the temperature is high or low, regardless of cold winds blow,
away we go like Edgar Allan Poe, on now with the show. BTW rhymes are welcome.
optimizing large operations?
2 posts
• Page 1 of 1
-
mauvebic - Member
- Posts: 1550
- Joined: Fri Jan 27, 2012 11:32
optimizing large operations?
"Fuck the hat." - Paulie Gualtieri
Maybe its possible to save the border of the sphere and then fill it in a register_on_globalstep function.
2 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 10 guests