Delete POP thin page unusual cpu cooking

Bugs
1

Hi,

Here’s a little example .tox, when using the thin page on the deletePOP set to random I get unusually high cpu cooking times (these can go even higher than in the example file). I’ve also added in the example file doing the same delete operation but by passing an attribute to delete by instead from the randomPOP and the cpu time is normal:

baseDeletePOPExample.tox (1.4 KB)

Cheers

Alex

2

Hi Alex,

Thanks for the feedback!

Under the hood the thin parameters builds a points or primitive list on the cpu, similar to the by pattern page, which can be cpu heavy when the input has a lot of points or primitives.

I think this was done to get a more predictible pattern but we’ll confirm, maybe we could add a GPU mode that would do what random attribute + delete by attribute does under the hood, results will be most likely be different.

Cheers,

Vincent

3

Thanks for the response.

Good to know the inner workings of how that part of the delete POP works!