The most CPU intensive SNES game / part / effect ever

Anything else related to bsnes goes there.
Posts: 28
Joined: Wed Sep 08, 2004 12:05 pm

Post by d4s »

Here's something I frequently do in my SNES projects during development:
Latching the scanline counter once before entering the NMI/IRQ-waitloop and using that as the y-position of a sprite.
The more that sprite moves toward the bottom of the screen, the more time the CPU needed to calculate the last frame.
A no-brainer, really. Very quick way to estimate current effective cpu load and track down causes of slowdowns.
I've seen a couple of games use that in debug mode, too.

Also, if you're looking for CPU intensitive stuff on the SNES in the sense of most effective use of the available cpu cycles, have a look at the long forgotten tiny part of snes history that is demoscene/cracktros.
Posts: 327
Joined: Thu Jun 30, 2005 1:54 pm
Location: USA

Post by blargg »

On the NES, people often change the color tint bits, which affect all pixels drawn. You could do similar on the SNES by adjusting the overall brightness (set it to normal in NMI handler, then set to darker before entering wait loop).
Posts: 861
Joined: Wed Aug 04, 2004 5:43 pm
Location: Sloop

Post by FitzRoy »

Liberty or Death's transition effect before getting to the game map. Crunch!