RAYLIB 5.5

I'm not a big fan of riding the endless software upgrade treadwheel. In fact, I've probably ranted about that somewhere quite recently.

I've been meaning to jump up from Raylib 4.5 to 5.0 for a little while, and upon checking the other day, I saw that 5.5 is fresh off the press (as in, the announcement went out ~5 hours prior to my checking. Neat.jpg). So, feeling just a hint of that old masochistic itch that all programmers must have in some form or fashion, I backed up my dev environment, downloaded the 5.5 package (now a whopping ~650 megs. Holy fuck?), girded my loins, and went to installing.

And you know what? Things worked. I rebuilt several recent 4.5 projects and absolutely nothing broke. I didn't run into any visual or audio glitches. Everything... just... went right. And that was it, I thought, until I realized I needed to try out the web build. I was pretty curious, partly because 5.5 made getting the web build less painful, but mostly because I've been making web builds of all my Raylib projects for a while now, and that's not going anywhere soon. The 5.5 package comes with Emscripten installed (goddamn that's the most awkward title for a piece of software), and there's a pre-built .a file so you don't have to rebuild Raylib with PLATFORM_WEB enabled. It's ready to go.

So............................... uh, that's the end of the good news.

The bad news is that there are some bugs in the Web stuff that weren't there before. For starters, fullscreen mode is borked and I only get ~70% of the screen, with the bottom portion being scaled so it's off the screen. This was definitely not an issue back in the 4.5 days. The mouse is also a bit wonky, but I'm not 100% convinced this is a recent problem, since this is the first web project I've compiled with mouse support. It's entirely possible it has always been janky like that. There are still some annoyances, like having to mark textures as repeatable if you want them to wrap properly, and obviously shaders need to be busted back to ~v1.00 to get them to compile. It's all so tiresome, but whatever. Those things are not going to change.

Either way, I managed to get a web build out after a few evenings of fiddling, but never managed to resolve the fullscreen bug; nor do I care to bother with it. If you want the proper experience, you'll download the Windows binary and run it natively or via Wine. Everything else is YMMV.