>>48211134anon has no idea how the DS processes graphics, shocker.
The reason Mario 64 DS worked as well as it did was because it had far better geometry engine combined with larger texture storage. Mario 64 original was a hot mess of code and relied on pathetically small textures that the DS was more than capable of outputting, and treating it like it's something special for the DS to handle is a meme. You'd be better off discussing Mario Kart DS with much more complex mapping and texture management, but still the DS was actually quite capable running a lot of simple 3D geometry. This includes your Dragon Quest Monster Joker. Sorry to say it but it took very little of the DS's polygon and vertex RAMs to actually run 3D games smoothly and most games would rarely exceed half of it.
The hardest part of the DS's processing was texture manipulation and that's what would be the challenge of Gen 5. Pokemon's battle sprite engine used filtering to de-noise some of the blockiness of the textures, especially when zooming out for moves like Fusion Flare and Bolt. The DS wasn't well equipped to doing this on any part of its GPU, so filtering was handled by the CPU.
The background are simple texture maps but still did need to be manipulated and filtered which put additional strain on the CPU. The GPU was mostly responsible for loading textures to hand off to the CPU and keeping the camera functional, and wasn't too strained until the GPU would shit itself trying to scale textures during attacks.
If you ever wondered why these games played better/faster on the DSi and 3DS, the larger CPU and GPUs could handle more of the load.
>>48211153Happy?
