My adventures into 3DS Audio are looking a little bit closer.

Clampett's returned in this odd little platforming game.

Back to my usual "End of Project" duties, today.

Game #558 is coming along rather well, and is mostly "complete" on the PC side of things.
The 3DS version is still all kinds of quirky, though, with issues such as the level generator taking WAY too long on the hardware. Again, something that the emulator has no trouble at all with, but that the hardware itself struggles to do.
I'm going to have to chop up the generator and build the level up over multiple frames, instead of clogging up the entire system for the duration.
Other than t...

OK, I really need to stop working on the 3DS stuff, and get this week's Clampett game done.

I tried out Flappadiddle again, today, and it was very very broken!!

128Mb Ram.. That's what the specs on Wiki says that the 3DS should have.
But all these complications I'm having.. The whole thing seems to be tripping up on pretty much anything I throw at it.

Spent most of this morning working on Error Messages.

Whilst working on this week's game, I'm constantly testing it on the 3DS to ensure everything's working correctly.

Turns out, the memory was perfectly fine!

I need to double check, but I think the big Grid[] array might be having issues.

I said I was going to work on a Mini Clampett sequel this morning, so I cloned the project folder and opened it up, and then went "Hey, I bet I know what's wrong with the 3DS Engine.."

3DS Homebrew is all kinds of broke, right now, and I'm doing my nut trying to figure it out.
I decided, last night, after the millionth crash of the day, that I'd instead focus on something else for the rest of the week.

Bah, humbug!
After spending hours writing a lovely function, the other week, which takes .png images and chops them down to 1/16th their size, so that they work better in the 3DS's memory, it seems that the memory required to load those initial images before chopping is actually too much for the poor little 3DS to cope with.
After having tried the same engine with the same images, but pre-scaled down, the whole framework is running a LOT better.
This means that..
A ) I'm goin...

Yeah, I really don't have a lot of RAM to play with in the 3DS, do I!?!

It's weird how many people have flooded my Twitter Inbox offering help on how to get various emulators and pirated games to run on my 3DS.
I appreciate that most people hack their 3DS for such purposes, but I'm not that guy. I'm LITERALLY only doing this for my own games!

Today's challenge.. Can't seem to get colours working. Hmm..

It works, but like I said this morning, I really need to fix the scaling quite a bit to get everything working properly.
But, yeah.. Our familiar Framework Menu! Woot!

Can't seem to get a grip on the texture switching stuff.
I've started a topic at GBATemp, and hopefully someone out there can figure this one out. Not sure.
In the meantime, the sprite-changing is at least working in "Immediate" mode, so.. until I can fix this, that'll just have to do.
The next step will be to have a play with my scaling routines.
Although this one single test has a decent-enough line of text, it's not exactly the world's most readable font, and...

Today's task will be to try and get multiple textures to work. I'm fairly sure it should be an easy task. They really can't have made it too complicated, right!?

OK, step 2 complete.. Only took about a week!!

If I toggle on the texture drawing, the three squares disappear.
At this point, it could be any of the following.
1. The Loader isn't loading the images correctly.
2. The drawing routine's slightly wrong.

Three little squares..

Had a rather frustrating day of GameDev yesterday, as I struggled to get any further than the blue screen.

Although the screen is still just blue, I have at least managed to get it to now load the image data without the emulator freaking out and throwing up as many errors.
The nasty looking purple error messages are gone, and all the errors that remain appear to be showing up on the examples, so I'm not "too" worried about that.
Next step is figuring out why on earth the images still aren't showing up on the screen.
Hmmm..

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

Success!!