Swallowing the elephant into Blender

Re:Swallowing the elephant into Blender by knolan on Friday July 22, 2022 @05:04AM (#32190033)

I disagree, the point was to show how object importing scales and he used an extreme example to make the point. He also gives an example of duplicating 10k cubes in Blender (something not out of the ordinary) also sees a massive speed up.

This kind of thing can help understand other bottlenecks in software like Blender as its users and developers get more ambitious as the software grows in capability.

Idealistically wouldn’t one like film makers to be able to work ‘in world’ decoupled from technical limitations?

[ Parent | on HN ]

Re:Swallowing the elephant into Blender by lukego on Friday July 22, 2022 @05:19AM (#32190126)

I've seen much the same problems when trying to programatically construct a large number of objects using the (low-level) Python API. If this kind of optimization improves throughput of those APIs that would be a major enabler for work that I want to do.

Otherwise I'm side-tracked looking for relatively awkward SIMD-style programming (e.g. Geometry Nodes) as a workaround for "CRUD" operations being too slow. Can't be just me...

[ Parent | on HN ]