Report this content

If it were to bake in the fleck density, instead of storing 2 points for that long line... it would now need to store 500 points, two for each new stroke (or at least 1 per fleck)--ballooning the data required to store that painting, and defeating the purpose of using it to lower thermo.

Weird, because when I did some testing after the update to the thermo meter I noticed it took about 53~ flecks (give or take 2) to add 0.01% to paint thermo. I then made two paintings:

• Painting A consisted of 5 paint strokes at 53 flecks to total 265 flecks. Result was 0.05% paint and about 0.045% shared memory.
• Painting B consisted of individual flecks, no strokes, totaling 265 flecks. Result was 0.05% paint and about 0.045% shared memory.

Merging both did not raise overall paint thermo, but oddly enough shared memory does go up another 0.045%. Doing the Start/End Point trick before merging however does reduce thermo on both metrics.

Fleck density is still useful for optimising rendering because it's rendering fewer flecks. And can be used in conjunction with "stretch fleck" to cover the gaps of a line while still rendering far fewer flecks per stroke.

I'm aware of that, but I'm trying to animate some things, and while it appears that the tools had animation in mind (the animation reel tab being a big indicator) thermo wise it's very difficult to manage over many frames. There's also paintings as textures which I'm very fond of but I'm finding myself having to go back and retexture things due to some things taking up more thermo than I'd like and there's no simple way to reduce it other than to redo the whole thing.

All that said........ they do actually have a "reduce detail" type tool for paintings in the works! https://trello.com/c/x5NC0ZmA/211-paint-reduce-detail-tool

Oh thank God! You just made my day lol. Well I would still take my idea into consideration but I'd much prefer that.