Metroid Prime Dev Stuff

Discuss anything about video games here if you cannot find anywhere else to post it! No serious gaming and real life topics in this forum! Those go in the Debate, Serious and Politics Forum (and you will need 200 posts to post in there!)!
Forum rules
No serious gaming and real life topics in this forum! Those go in the Debate, Serious and Politics Forum (and you will need 200 posts to post in there!)!
User avatar
cm2
Verified


RPG Character: Marshall Silas
Senior Member
Senior Member
Posts: 526
Joined: January 12th, 2022, 23:22
Cash on hand: 4,600,013.07
[Donate][Start Robbery]
Nintendo 3DS Central Vault balance: 353,300,544.19
2
Title: PLOT Master
Has thanked: 333 times
Been thanked: 2380 times
Gender:
    Windows 7 Firefox
Nintendo 3DS Central

Metroid Prime Dev Stuff

Unread post by cm2 »

Read Dev's tweet:


Metroid Prime Game Dev Story – The One Where We Fridged a GameCube.

Shortly after Prime shipped, Nintendo told us that a “bad batch” of GameCube CPU’s shipped, and apparently Prime was the only game that misbehaved on them. We saw videos and it was clear what was going on.

All animated objects were freaking out. I’ll get into the techy reasons later, but the point was we needed to actually slow down some of our code, because it was running too fast for these CPUs to handle! We needed to be able to test this, but Nintendo only had one dev kit with this CPU. We couldn’t detect the CPU, and if we slowed it down too much, the game’s framerate would tank. If we didn’t slow it down enough, it would glitch. Even worse, we had to burn disks for this kit. So each test was hours. Even weirder was to see the problem, the kit had to be cold. Like, freezer cold. So we literally had to put the kit in the freezer, test the game for 15 minutes tops, then start all over. It was crazy.

We literally were running the kit from the break room freezer to the TV, and loading save games as fast as possible to as many places as possible in 15 minutes, then trying new code, re-freezing, and back. I’ll never forget it.

Techy stuff: Our skinning used the locked cache DMA to read in data and the write gather pipeline to write it out. Most of the Nintendo samples used the locked cache for both read and write, so my method was a bit faster. But it also hit memory bandwidth limits. As I recall, the issue was that the write gather pipe on these broken CPU’s wouldn’t stall when it was full or properly report its status, so we had to keep inserting NOPs in the code to slow it down just enough to stop stalls from happening, but not so much to slow down the game.

In case you were wondering, when someone called support about this animation problem, Nintendo actually sent them a new game disc with this updated code! That’s how we did “patches” back in the old days!
word count: 386
"I am not the law, but I represent justice so far as my feeble powers go." -- Sherlock Holmes
ImageImage

Last 255 Members Who Visited This Topic! Total 21 visits

Maria (2), User avatar DPadDoc (2), User avatar Tiger21822 (3), User avatar Lyn (3), User avatar Tiger21821 (3), User avatar Tiger21820 (6), User avatar cm2 (2)

Return to “General Video Game Discussion”

Who is online

Users browsing this forum: Claudebot [Bot], Google [Bot] and 0 guests