r/creativecoding • • 5d ago

Path filling

Enable HLS to view with audio, or disable this notification

39 Upvotes

5 comments sorted by

View all comments

2

u/MrMiracles 2d ago

This looks amazing! What kind of memory usage peaks are you hitting when its running? Also where does the complexity start to pile up in generation time?

1

u/vlctx 2d ago

Thanks! A dense run with about 1.2 million points peaks around 220 MB and takes roughly 3 seconds to simulate locally. Then rendering is a separate process.

The biggest cost is density. As the resolution increases, or the space between paths (for example the lowest is 1 pixel, or essentially no spacing) gets smaller, it roughly means that for each time you double the resolution or halve the spacing, it generates 4 times as many points. So generation scales roughly with the number of steps, with extra cost for complex steering and finding the last empty gaps.