Longtime programmer discusses N64, GameCube experiences
Posted on July 31, 2012 by Brian(@NE_Brian) in GameCube, General Nintendo, News
Munkyfun’s Cory Bloyd knows his video game hardware. He’s a longtime programmer who has been involved with hardware introduced nearly two decades ago, up through consoles we’re playing today.
Some of Bloyd’s experience includes the N64 and GameCube, though he didn’t work with the latter system too much. In any case, you can take a look at his comments below, which include lots of technical talk – just as you’d expect!
N64: Everything just kinda works. For the most part, it was fast and flexible. You never felt like you were utilizing it well. But, it was OK because your half-assed efforts usually looked better than most PS1 games. Each megabyte on the cartridge cost serious money. There was a debugger, but the debugger would sometimes have completely random bugs such as off-by-one-errors in the type determination of the watch window (displaying your variables by reinterpreting the the bits as the type that was declared just prior to the actual type of the variable —true story).
GameCube: I didn’t work with the GC much. It seems really flexible. Like you could do anything, but nothing would be terribly bad or great. The GPU wasn’t very fast, but it’s features were tragically underutilized compared to the Xbox. The CPU had incredibly low-latency RAM. Any messy, pointer-chasing, complicated data structure you could imagine should be just fine (in theory). Just do it. But, more than half of the RAM was split off behind an amazingly high-latency barrier. So, you had to manually organize your data in to active vs bulk. It had a half-assed SIMD that would do 2 floats at a time instead of 1 or 4.
