Program compatibility: Difference between revisions
From NESdev Wiki
Jump to navigationJump to search
Rainwarrior (talk | contribs) (adding year in case it helps put compatibility in perspective (is there a table class that would allow optional sort by year?)) |
m (→Common compatibility problems: fix link) |
||
| (13 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
:''This page describes defects in homebrew games. For defects in games prior to 1996, see [[Game bugs]].'' | :''This page describes defects in homebrew games. For defects in games prior to 1996, see [[Game bugs]].'' | ||
Homebrew development is as subject to bugs as old software was, but many suffer from additional compatibility problems with the NES hardware due to being tested on emulators exclusively. | Homebrew development is as subject to bugs as old software was, but many suffer from additional [[Accuracy|compatibility problems]] with the NES hardware due to being tested on emulators exclusively. It is often the case that early homebrew ROMs will not run correctly on hardware. Since the release of the [[PowerPak]] in 2008, and general improvement in emulators over time, these problems have become less frequent. | ||
For a partial list of homebrew projects, see: [[Projects]] | For a partial list of homebrew projects, see: [[Projects]] | ||
== Common compatibility problems == | |||
This is a list of issues that commonly appear due to lack of popular support in emulators, or sometimes even hardware limitations of flash-carts like the [[PowerPak]]. | |||
Many emulators are merely trying to be compatible with existing games, rather than accurately reflecting the hardware, making them inadequate for verifying the correctness of new software. | |||
* Use of DPCM samples causes a [[DPCM conflict|conflict]] with controller and PPU reads during sample playback. | |||
* Writes to [[PPU registers]] outside of [[The frame and NMIs#VBlank, Rendering Time, and NMIs|VBlank]] with rendering enabled conflicts with internal use of the PPU address, causing graphical corruption. | |||
* Failure to initialize registers not guaranteed by the [[CPU power up state]] or the [[PPU power up state]]. | |||
| | * Failure to initialize RAM, nametables, or [[mapper]] registers. (Few mappers have guaranteed power up states.) | ||
* Failure to delay use of the PPU after power/reset to avoid conflicts with its [[PPU power up state|warm up state]]. | |||
| | |||
== References == | == References == | ||
<references /> | <references /> | ||
Latest revision as of 17:57, 24 January 2023
- This page describes defects in homebrew games. For defects in games prior to 1996, see Game bugs.
Homebrew development is as subject to bugs as old software was, but many suffer from additional compatibility problems with the NES hardware due to being tested on emulators exclusively. It is often the case that early homebrew ROMs will not run correctly on hardware. Since the release of the PowerPak in 2008, and general improvement in emulators over time, these problems have become less frequent.
For a partial list of homebrew projects, see: Projects
Common compatibility problems
This is a list of issues that commonly appear due to lack of popular support in emulators, or sometimes even hardware limitations of flash-carts like the PowerPak. Many emulators are merely trying to be compatible with existing games, rather than accurately reflecting the hardware, making them inadequate for verifying the correctness of new software.
- Use of DPCM samples causes a conflict with controller and PPU reads during sample playback.
- Writes to PPU registers outside of VBlank with rendering enabled conflicts with internal use of the PPU address, causing graphical corruption.
- Failure to initialize registers not guaranteed by the CPU power up state or the PPU power up state.
- Failure to initialize RAM, nametables, or mapper registers. (Few mappers have guaranteed power up states.)
- Failure to delay use of the PPU after power/reset to avoid conflicts with its warm up state.
