Category:Mappers with scanline IRQs: Difference between revisions
Rainwarrior (talk | contribs) m (clarify that scanline IRQ should mean rendering-based) |
Rainwarrior (talk | contribs) m (link to PPU pin out and signal description for PPU A12) |
||
| Line 1: | Line 1: | ||
[[Category:Mappers with IRQs]] | [[Category:Mappers with IRQs]] | ||
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 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 pin out and signal description | ||
|PPU A12]]. | |||
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 PPU A12) should go in the [[:Category:Mappers with fixed-timing IRQs|fixed-timing category]] instead. | Mappers with a fixed delay (even if clocked by PPU A12) should go in the [[:Category:Mappers with fixed-timing IRQs|fixed-timing category]] instead. | ||
Revision as of 20:23, 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 pin out and signal description |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 (even if clocked by PPU A12) 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.
0
1
2
3
- NES 2.0 Mapper 313
- NES 2.0 Mapper 315
- NES 2.0 Mapper 327
- NES 2.0 Mapper 333
- NES 2.0 Mapper 339
- NES 2.0 Mapper 344
- NES 2.0 Mapper 345
- NES 2.0 Mapper 348
- NES 2.0 Mapper 351
- NES 2.0 Mapper 353
- NES 2.0 Mapper 356
- NES 2.0 Mapper 358
- NES 2.0 Mapper 359
- NES 2.0 Mapper 361
- NES 2.0 Mapper 364
- NES 2.0 Mapper 366
- NES 2.0 Mapper 367
- NES 2.0 Mapper 369
- NES 2.0 Mapper 370
- NES 2.0 Mapper 372
- NES 2.0 Mapper 373
- NES 2.0 Mapper 376
- NES 2.0 Mapper 383
- NES 2.0 Mapper 386
- NES 2.0 Mapper 387
- NES 2.0 Mapper 388
- NES 2.0 Mapper 391
- NES 2.0 Mapper 392
- NES 2.0 Mapper 393
- NES 2.0 Mapper 394
- NES 2.0 Mapper 395
- NES 2.0 Mapper 397
4
- NES 2.0 Mapper 401
- NES 2.0 Mapper 410
- NES 2.0 Mapper 411
- NES 2.0 Mapper 412
- NES 2.0 Mapper 430
- NES 2.0 Mapper 432
- NES 2.0 Mapper 441
- NES 2.0 Mapper 443
- NES 2.0 Mapper 444
- NES 2.0 Mapper 445
- NES 2.0 Mapper 446
- NES 2.0 Mapper 451
- NES 2.0 Mapper 455
- NES 2.0 Mapper 456
- NES 2.0 Mapper 457
- NES 2.0 Mapper 458
- NES 2.0 Mapper 460
- NES 2.0 Mapper 467
