devkitPro

When you encounter this kind of error, it is suggested to run make clean prior to make, in order to clear out stale dependency tracking.

Our official Docker images have now been updated with all the current packages as of July 30th 2020.

This might be of interest: https://github.com/devkitPro/3ds-exampl ... s-decoding

Nope, sorry. The console is really only meant to be used in quick prototype programs that are not interested in setting up proper rendering.

You were both creating a rendertarget on the bottom screen *and* a console. Put the console on the other screen so that they don't conflict.
When using citro3d/citro2d, you must not use gspWaitForVBlank, as these libs automatically handle screen synchronization.

Can you post your code? Without it I can't diagnose or give you advice.

New month, new release cadence. Today we bring some much needed love to the 3DS in the form of updated development packages. Use sudo (dkp-)pacman -Syu to update or sudo (dkp-)pacman -S 3ds-dev to install.

libctru v2.0.0 - major release with many under the hood changes and improvements.
citro3d ...

The DS's non-paletted bitmap modes only support RGB5551, with only 1-bit transparency. This means pixels are either fully opaque or fully transparent.

I think you might have to use the 3D engine with a texture in A3I5 or A5I3 format; however those are paletted formats with only 32 or 8 colors ...

Okay, I've looked at your problem and I've found the following issues:
Off-screen render targets must be created on VRAM. It looks like hardware clearing of render targets only functions properly when it's located within VRAM.
The off-screen render target was used completely uninitialized. I added ...

Hi,

You're not supposed to dynamically create and destroy render targets inside the main game loop, since that will cause synchronization problems with the GPU - in other words, your code may end up accidentally deleting resources that are still being used by the GPU (which executes in parallel to ...