OK, today's aim is obvious. Extra Squishiness in the Bug Department!!

Success!!

I did a rather large bulk of coding, yesterday. Enough to get the top-screen on the emulator to finally change colour!

All appears to be going OK on the 3DS front, but now I need to take the loaded image data and shift it over to video-ram. And this is where things start to break down!

I can now launch, quit, relaunch, requit, re-relaunch, home, resume, sleep, resume, and quit the 3DS Framework, over and over, without it crashing!! Turns out, I had "gfxInitDefault();" occurring twice. Such is the chaos of my framework, took me bloomin' ages to find the bug.

So, the R4 3DS i Gold + (or something) turned up last night, at around 6pm, and I spent the next two and a half hours faffing about to get the Homebrew Launcher installed onto my old 3DS.

This racing game really doesn't seem to be going anywhere.

Spent most of today rewriting the track converter tool.

I've been trying my best to work on the car racer thing, but after the past few days of tweaking the 3DS Homebrew stuff, the racer's certainly been neglected.

After a bit of a breakthrough, this morning, I've now got THIS displaying on the 3DS. This is potentially a good sign. Now all I have to do is code all the stuff that gets sprites and sounds loaded into memory, and then outputted from the 3DS somehow. Should be a cakewalk!!

I'm currently unsure whether I can get the framework running on 3DS at all, or at least, not in it's current condition.

Yesterday, I spent about 3 or 4 hours wrestling with DevKitPro, trying to figure out the best way to get my Framework running as 3DS Homebrew.