
this makes my browser almost entirely unusable, should definitely have been hidden in a details, still v cool tho
Ah, sorry! At least for me, if you scroll past the post it should return to normal speed?
this is so rad (and disastrously inefficient, I have to imagine ^__^;)
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…
please consider hiding this in a <details> tag to avoid tanking lower-end mobile devices completely
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
Do you have your device set to prefer reduced motion? I believe that might disable the spin animation.
It’s an accessibility setting on your phone or computer, to say “show me less animation”
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
might be forced layout reflows, according to chrome's profiler https://web.dev/avoid-large-complex-layouts-and-layout-thrashing/#avoid-forced-synchronous-layouts
all the movement happening is with transforms, so there shouldn't be any layout changes at all unless the browser is trying too hard
oh my god this is dropping so many frames lmao
congrats! this is the first CSS animation in the history of cohost that actually lags my computer
this is a true CSS crime, absolutely amazing. 100% the first one worthy of the tag. repeating what's been said here but it totally mutilates my browser (both ff and chrome) lmao
thank you for the content warning, I did not realise css needed content warnings but this monstrosity does