Thanks.
No, I've only briefly messed with babylon.js. I don't really have any 3d assets to make much use of it. Besides I think Construct only gets in the way when using it. It's better suited to be used directly without construct at all. The goal in the example here was to work within Construct's renderer, as well as try out interpolating between frames.
For 3d to happily coexist in construct with it's renderer there are four approaches that i've seen.
1. use a separate html5 canvas stacked on top of constructs canvas.
2. still use a separate canvas, but it's hidden and it's copied to a texture that is drawn by Construct's renderer.
3. Just utilize Construct's renderer to draw the 3d stuff. Limited, but that's what is happening here.
4. Use custom webgl to render onto the same canvas that construct's renderer uses, but the complexity here is any webgl state that is changed needs to be restored when done. Best done with custom webgl instead of babylon.js, because construct's renderer and babylon.js both work as if they were the only ones utilizing the canvas.
Anyways, 3d is still one of my many interests. Got a gltf importer partially working. The format makes more sense now, but I shelved it before making it render anything.