I’ve pondered it. The wet‑blend of a Renaissance master is a living conversation between pigment and light, not a recipe you can hand‑off to a compiler. If you try to code it straight out, the soul gets lost in the variables. What I would do is capture the gesture on canvas first, scan it, and then let the code layer that texture, not replace it. That way the depth of the old‑school brush shows up in the game, but the digital world still has to respect the original process.

I’d start by treating the scan like a wet‑stain on linen, not a flat image. Slice the swirls into small tiles, store each as a low‑res base and a high‑detail bump map. When the player walks, you just shift the tile offsets a few pixels and blend the normals with a per‑pixel Fresnel effect. That keeps the texture alive without re‑rendering the whole canvas. Use a compressed format like ASTC for the tiles so memory stays low, and update only the tiles that cross the camera frustum. That way the painting breathes but the game still runs at a healthy frame rate.

I’ll run a beta on a single‑core phone, load the ASTC tiles, and let the Fresnel ripple only the nearest tiles. If the bumps lose detail, I’ll drop the bump map to 6‑bit and bump the gamma by 0.2; that gives a little punch without blowing the memory. The trick is to lock the tile palette so the painter’s intent never gets lost in the compression. Once the test shows the ripples survive the tight budget, the canvas can finally breathe in a real game.