devkitPro

As it turns out a file I/O optimisation we did in devkitARM was broken under very specific circumstances (see https://github.com/devkitPro/newlib/issues/16) and the fix slowed it down slightly. For what it's worth testing with our optimisation completely reverted led to a load time of 839.02ms so t...

(This is mostly a repost of this issue.) I recently updated all of devkitARM's packages through dkp-pacman, and after recompiling my homebrew with everything, I found that my call to C2D_SpriteSheetLoad from citro2d now takes an obscene amount of time (about 1.5 seconds on o3ds) for the spritesheet ...

I went through and looked at citro2d to see if it had anything to prevent unnecessary texture switching. It actually does have some checks for that, and when I tried recompiling with them off to see what would happen, I could draw even fewer sprites before things slowed down. So that's definitely no...

I've been making a homebrew game for a little while now using citro2d. Through making it, I've noticed that citro2d, at least through the way the gpusprites demo draws sprites, can only get around 350 sprites drawn to both screens (~700 total draws) before it starts to lag on o3DS. I know the consol...

Hi there - I wasn't sure which board to post this on, so I hope this one is alright. I recently was able to get a very hacky setup going for compiling code written in the D programming language with devkitARM, specifically on the 3DS. I also was able to generate some partially complete bindings for ...