Full experiment, screenshots and runnable kit on Digital Garden
A still image looked like a successful renderer migration. All three lavender clumps appeared, and a real click reached the HUD above them. The first sign of trouble came from the loaded geometry.
The same 53,561-triangle GLB went through Three.js 0.186.1 and official @pixi/3d 0.1.0. Three.js retained eight custom plant attributes. Both Pixi backends warned that each one was skipped. The stem still had position, normal and UV data, enough to render the static picture. A wind shader depending on stalk IDs, anchors and bend weights would need those inputs restored.
Across 15 fresh Chrome contexts, all three routes had a median animation callback interval of about 16.7 ms. That cadence tells us little about spare GPU capacity. The missing attributes give a better first estimate of the porting work.
Alicia authored the garden assets. Codex assisted with the harness, measurements and writing. Inspect the source data and repeated runs.
