Timeline for How to calculate an attribute for each point which depends on every other point
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 2, 2024 at 12:00 | history | edited | Gordon Brinkmann | CC BY-SA 4.0 | added 215 characters in body |
| May 2, 2024 at 11:47 | history | edited | quellenform♦ | CC BY-SA 4.0 | Refined Answer |
| May 2, 2024 at 11:28 | comment | added | Gordon Brinkmann | @quellenform Sure, edit it in. | |
| May 2, 2024 at 10:36 | comment | added | quellenform♦ | If I could make a suggestion for improvement here: If you replace the node Attribute Statistic with the following setup, performance can be greatly improved: i.sstatic.net/FypgskvV.png | |
| Apr 28, 2024 at 21:32 | comment | added | Gordon Brinkmann | @ÉricoPatto Oh damn, you're right I did not switch the Domain Size... My bad, most of the time I never use it so I did not pay attention to it. I agree it might be slow with lots of points but I did not find a more effcient way. Perhaps someone else might know a better way. | |
| Apr 28, 2024 at 19:47 | comment | added | Érico Patto | This works, though it can be slow with more points. Also, I believe it only worked with meshed in your case because the "Domain Size" node used to calculate how many iterations to perform is set to "Mesh", not "Point Cloud". | |
| Apr 28, 2024 at 18:05 | vote | accept | Érico Patto | ||
| Apr 28, 2024 at 17:49 | history | answered | Gordon Brinkmann | CC BY-SA 4.0 |