social.noyu.me

upcoming touchHLE game? (this is not Default.png!)

this game is still available on the modern App Store btw, but only as a Lite version. the website's still up too. I guess the developers just keep it up for posterity's sake?

hmm i'm sure this is normal, let's ship it,

this game does its own text rendering, this will be a pain to debug…

sigh here we go

people will tell you Rust is good for debugging because it has tightly controlled unsafeness, algebraic data types for results, bounds checks everywhere, assertions etc.

none of this is wrong but also i <3 <3 <3 std::fs::write

ah… I traced it to the code that fetches locale strings, and it's calling… bsearch, which I implemented earlier today but didn't test very thoroughly…

I think we all know where this is going.

aha, I found the bug. thankfully for my faith in my ability to write algorithms correctly, the binary search itself was correct… but the C standard requires you to pass the key as the first argument to the callback, whereas I had reversed the order. oops. ^^;

me, earlier: wow, isn't it weird that bsearch() requires the key and the elements of the array to have the same type? that's inconvenient
me, now: oh for fuck's sake

:3

finally, Fastlane Street Racing on Android

now I just have to figure out why the specular lighting effects are broken in my GLES1-on-GL2 layer. without working RenderDoc, because it's legacy APIs all the way down.

gods save me

yes I know I should just use ANGLE, it seems to have (some?) GLES1 support these days, but I don't want to use up all my remaining disk space on it or figure out how to integrate Google's weird build system :/

@hikari btw xscreensaver has an opengl 1 on opengl layer in it because all the old screensavers were written for opengl 1. It may be worth a look for inspiration?

@0x2ba22e11 ah that's a good point, I may have a look at it at some point

@hikari ooh sorry I misremembered. It's was opengl 1.3 on top of opengl es 1.1 https://www.jwz.org/blog/2012/06/i-have-ported-xscreensaver-to-the-iphone/

I'm not sure if it might have developed more than that subsequently because xscreensaver is still on iPhones and that may have necessitated another API bump in the intervening years?

@0x2ba22e11 the layer I have currently does basically the opposite of what jwz's did

@hikari oh god is it this function that Microsoft fucked up and flipped the callback on? they did it to one of the c standard functions. in case you wound up remembering their order or something.

@leftpaddotpy oh I think I read about that earlier this week, but I don't think it was this one