Ah, sorry! At least for me, if you scroll past the post it should return to normal speed?

it would make a GPU-knower (like me) cry, because every triangle is actually a quad that's half transparent! there's no easy way to avoid this that I'm aware of, it's a fundamental design choice of how web browsers render stuff. maybe I could try to merge neighbouring triangles into quads though…

I've put it behind a “css animation” content warning now. I think that in practice it's always going to be possible to scroll past it, but it is a bit obnoxious if your feed is all reposts of this post, so I hope the click-through helps.

the model camera should move around the model but alas the model itself won't animate. having skeletal animations would of course be nice to have but I'm not sure if it's even possible to do, and I haven't done the work for it

I am honestly confused as to why browsers struggle with this so much, I suspect they're trying too hard to optimise something that can't be optimised. throw all the quads directly at the GPU, cowards

thank you!!

its very powerful