After a day spent trying to track down the issue(s), I've finally got WinSock to return exactly what I expect it to return! I can't rest yet, as I need to foolproof the values being returned, and also then get it working on things other than Windows... WinSock is strictly for Windows, so .. It's going to be a system-by-system rewrite to get everything on the same level. But I'm about 50% confident that I'm able to send requests from the Windows editions of the games. *sigh* T...

I finally dug my heels into the Net code, last night. For the meantime, it'll be very Windows specific, and I'll have to tackle each different system in it's own way.

Logging into the Mac, I copied the AGameAWeek Framework folders over, and tried to run a lengthy scrambled mass of "Terminal" (stop calling it Command Prompt, Jay!) commands in order to get it compiling. After about an hour or so of tweaking the command, I got the thing outputting GLFW errors, which is an improvement from what I started with!

It's definitely picking up the controller..

Time for another test. If you're bored, are running Windows, have a controller or two at hand, and want to help out, please give this test a run. Download the Test Here (Windows only, right now. Linux is.. ... Being Linux!)

OK, the mouse stuff seems to be working with overscan, now, which is good. Additionally, the Game Controller code appears to be kinda ok. I've set up the engine/framework/etc to assume all controllers are "The player's input", so I'm going to be doing 1-player only stuff until I can be bothered to faff about with it some more and implement multiplayer controller code! Unfortunately, I don't 100% trust what GLFW3 is telling me. The controller input list here is suggesting that DPad Up...

Mouse, and of course, touchscreen. They both took a bit of a tumble, last night. The overscan seemed to be working, but I was only testing it with controllers, since the overscan is typically only used on Android TV versions of the games. Yesterday, however, I chose to reuse the overscan functions on iOS.

<- 4:3 | iPhone -> The menu seems to be scaling fairly well, which is nice. Poor single-pixel Platdude outline looks a bit gnatty, but that's "GL_Nearest" sprite scaling for you :\ I'm confident that, once on an actual device, the resolution increase will help to fix that. Either way, the screen seems to fit all my test screen resolutions well enough to move ahead with the next task. Gud gud!!

I must've spent about 5 hours, yesterday, trying to find the right sound for a new AGameAWeek Jingle.

Yesterday was a horrific day.

A simple AddCredits command, as well as default credits and a bit of scrolling, along with a nice swirly background. It all comes together to make a nice and simplistic little credits screen.

Also available on SoundCloud or in the Pulp'ish Album. I know it's not Friday!

Yesterday was a code-less day, and I expect today will be much the same.

*beep* I added the generic menu beeps, last night.

Or at least, the most basic of options work, anyway.

Seriously, though, I hate doing menus. Instead of finishing things off, last night, I instead gave up and rearranged a bit of my bedroom. Because.. Anything but Menus!!

A nice and simple (and awfully familiar looking) options screen. Next I need to implement the options, since they're currently not actually doing anything at all! But, yeay, options!

I need to add a bunch of default options to the menu, for generic functions like Fullscreen, Debugmode, Overscan and things like that. However, I also need to consider future projects, too.

It's a start..!

Spent a few more hours working on getting things a little neater.

I scrapped the idea of getting AndroidDev working on the PC. It just isn't going anywhere. .. But I wonder.. What would happen if I install the Android SDK/NDK devkit into one of my new Linux VirtualBox installs? Would that work any better?!

Android still isn't do-able.

Also available on SoundCloud or here, in the Music Archive.

Been trying to get High-Res Screenshot mode working. It'd be nice to have 1920x1080 screenshots from the engine, but trying to get OpenGL to render to a buffer larger than the screen resolution (my laptop's only 1366x768) seems to be quite a bit trickier than I thought. At the very least, I don't think it'll be something I can support outright, and will instead attempt to get it working "for me", and warn against widespread use. Unless, by some miracle, I find a foolproof way to do it, ...

The iOS edition of the new framework now crashes upon loading.

I swear, if I see another system update, this week, I'm going to go crazy..

I swear it only just updated with the Fall Creators' Update a week or so ago. But, nope.. doing it all again!!