3 ms·
> Consider taking a layered svg and applying a box blur. > Now you want an svg again. > It’s not a trivial problem. Lines blur and merge, you have reconstruct
by yorwba 5y ago
> Consider taking a layered svg and applying a box blur.
> Now you want an svg again.
> It’s not a trivial problem. Lines blur and merge, you have reconstruct an entirely new svg.
Nerfs are not svgs.
Consider taking a nerf and applying a box blur. Easy, a box blur on voxel data takes multiple samples within a box and averages them together, so to do the same thing to a nerf just take multiple samples and average them together.
That does get slower the more samples you need, but you never have to materialize a full voxel representation.
- wokwokwok 5y agoYou still have to process every voxel. > Doing all your transformations on the fly is a lovely idea, but you gotta understand reason nerf exists is that the raw voxel data is too big to store in memory. > It’s simply not possible you can dynamically run a image processing pipeline over that volume data in real-time.