Why
Split from #349 (post-processing chain): six effects remain, each its own pull request. This issue holds them until a lead takes one; the CTO then splits that effect into its own issue.
To do
Code context
The effect chain #651 and #692 built (world.effects), the composed image of #349.
Proof
Per effect: a test by behaviour, the measurer's capture on both backends, the cost of the pass within the frame budget.
Links
Split from #349. Related #351.
Why
Split from #349 (post-processing chain): six effects remain, each its own pull request. This issue holds them until a lead takes one; the CTO then splits that effect into its own issue.
To do
Code context
The effect chain #651 and #692 built (
world.effects), the composed image of #349.Proof
Per effect: a test by behaviour, the measurer's capture on both backends, the cost of the pass within the frame budget.
Links
Split from #349. Related #351.