VRAM inaccessibility: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
>Torchickens No edit summary |
>Torchickens mNo edit summary |
||
| Line 5: | Line 5: | ||
Due to the fact that VRAM can only be read or written to at specific periods of time, attempting to read the data there may result in data substituted with 0xFF bytes, and how much of the data is read is difficult to predict as it depends on precise timing. |
Due to the fact that VRAM can only be read or written to at specific periods of time, attempting to read the data there may result in data substituted with 0xFF bytes, and how much of the data is read is difficult to predict as it depends on precise timing. |
||
Some of the glitches VRAM inaccessibility is relevant for include [[arbitrary learnset glitch Pokémon]] and [[glitch type]] names. |
Some of the glitches VRAM inaccessibility is relevant for include [[arbitrary learnset/evolution glitch Pokémon]] and [[glitch type]] names. |
||
==See also== |
==See also== |
||
Revision as of 00:54, 30 December 2017
This article lacks images.
| |
|
Emulator screenshots are preferred to pictures taken with a camera or a capture card; however, a medium-quality image is better than no image. Any contributions are highly appreciated! |
VRAM inaccessibility is a phenomenon that occurs in Game Boy games.
Due to the fact that VRAM can only be read or written to at specific periods of time, attempting to read the data there may result in data substituted with 0xFF bytes, and how much of the data is read is difficult to predict as it depends on precise timing.
Some of the glitches VRAM inaccessibility is relevant for include arbitrary learnset/evolution glitch Pokémon and glitch type names.
See also
External links
This article or section is a stub. You can help Glitch City Wiki by expanding it. 
|