From b0e6947f23c69e52e4a5f202d8f0f34617af4ad4 Mon Sep 17 00:00:00 2001 From: Lior Halphon Date: Sat, 30 Nov 2024 20:49:58 +0200 Subject: [PATCH] Updated GB_read_memory (markdown) --- GB_read_memory.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GB_read_memory.md b/GB_read_memory.md index d6850d9..7240771 100644 --- a/GB_read_memory.md +++ b/GB_read_memory.md @@ -14,7 +14,7 @@ Performs a memory read on a 16-bit address on the emulator instance, as if it wa ## Notes -To read data outside of a currently mapped bank, you can use [[GB_get_direct_access]]. +To read data outside of a currently mapped bank, or to read from a memory region that might not be currently readable (e.g. VRAM during mode 3), you can use [[GB_get_direct_access]]. Because this functions goes through the same routines used by a CPU memory read, it will trigger any side effect caused by a memory read, including, for example, OAM corruption. If you wish you avoid this behavior, you can use either [[GB_safe_read_memory]] or [[GB_get_direct_access]].