Category:Mappers with scanline IRQs: Difference between revisions

From NESdev Wiki
Jump to navigationJump to search
m (redundant language)
m (fixed-timing scanline IRQ subcategory)
 
Line 4: Line 4:
Mappers with configurable [[:Category:Mappers with cycle IRQs|cycle-based IRQs]] can simulate a scanline-counter by waiting an equivalent number of CPU cycles, but have less robust horizontal timing, since they will fire relative to their start time, rather than relative to a rendering signal. The [[VRC IRQ]] has a convenient mode for this.
Mappers with configurable [[:Category:Mappers with cycle IRQs|cycle-based IRQs]] can simulate a scanline-counter by waiting an equivalent number of CPU cycles, but have less robust horizontal timing, since they will fire relative to their start time, rather than relative to a rendering signal. The [[VRC IRQ]] has a convenient mode for this.


Mappers with a fixed delay (even if clocked by the PPU) should go in the [[:Category:Mappers with fixed-timing IRQs|fixed-timing category]] instead.
Mappers with a fixed delay (but still clocked by the PPU) should go in the [[:Category:Mappers with fixed-timing scanline IRQs|fixed-timing category]] instead.

Latest revision as of 20:51, 18 May 2015

Mappers in this category have the ability to schedule an IRQ an arbitrary and continuously-adjustable number of scanlines in the future. This is triggered in response to a rendering signal such as PPU A12.

Mappers with configurable cycle-based IRQs can simulate a scanline-counter by waiting an equivalent number of CPU cycles, but have less robust horizontal timing, since they will fire relative to their start time, rather than relative to a rendering signal. The VRC IRQ has a convenient mode for this.

Mappers with a fixed delay (but still clocked by the PPU) should go in the fixed-timing category instead.

Subcategories

This category has only the following subcategory.

Pages in category "Mappers with scanline IRQs"

The following 106 pages are in this category, out of 106 total.