i'm supposed to let the new chromebook battery run all the way down and charge it back up to condition it
so i'm trying to get sonic robo blast 2 kart to build on it before it dies
it's at 35% now, but I also let it run down for a while this morning
a solid 10-15 FPS right now
it would have been done way faster if I'd actually read what the cmake errors were trying to tell me, but we got there
I am getting a cool 20 fps in the menu
okay, yeah, hardware acceleration not working on these is a known issue. annoying.
this is probably about as good as I'm going to get.
I still got silver on daytona speedway. that's probably more about how i've practiced that one specific course a lot than any credit to the experience of playing srb2kart on the shitty chromebook
ten of god's own frames per second
i was gonna say "it's the damn doom engine" but maybe I should see if real doom runs better
@BestGirlGrace it's not the doom engine anymore, there's so much extra stuff stapled onto it that it's about like calling goldsrc quake
@KS That makes sense, I don't feel as bad about this now.
(and, you know, I can't imagine this 32-bit cheapo ARM core from 2014 is exactly a development priority)
@BestGirlGrace which is to say yes, doom is much more likely to keep its stable 35fps
back when i worked on the engine keeping software rendering running at a playable framerate was sometimes a chore, and i can't imagine it's gotten any easier in the time since!