From 446cfa85b9c3be4c94dfc6524a566203a51887ec Mon Sep 17 00:00:00 2001 From: Lokathor Date: Sun, 4 Feb 2024 17:04:25 -0700 Subject: [PATCH] . --- book_src/introduction.md | 2 -- book_src/overview.md | 4 +++- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/book_src/introduction.md b/book_src/introduction.md index e9b61b8..a16f6f4 100644 --- a/book_src/introduction.md +++ b/book_src/introduction.md @@ -40,8 +40,6 @@ one for LLVM and one for GNU. To run `objdump` on our GBA executable we'd run `arm-none-eabi-objdump`. You'd also need to pass the correct path to your executable files, which are generally buried in the `target/` directory. -However you wanna do it. - ### `cargo-show-asm` [GitHub](https://github.com/pacak/cargo-show-asm) diff --git a/book_src/overview.md b/book_src/overview.md index 1f5030b..b3caee0 100644 --- a/book_src/overview.md +++ b/book_src/overview.md @@ -38,7 +38,9 @@ While drawing, pixels are updated from left to right in each line, and top to bo The display unit takes 4 CPU cycles to determine the color for each pixel. After the visible 240 pixels of each line are drawn, there's also a 68-pixel "horizontal blank" (h-blank) before the next line begins. After all 160 lines are drawn, there's also a 68-line "vertical blank" (v-blank) period before the screen draw cycle starts over. -Changes to any video related memory or controls usually take effect as soon as they are made, so video settings should usually only be altered during h-blank and/or v-blank periods to avoid graphical artifacts. + +Changes to any video related memory or controls usually take effect as soon as they are made. +Video settings should usually only be altered during h-blank and/or v-blank periods if you want to avoid graphical artifacts. The entire draw loop runs at 59.73 FPS, which means that GBA games can run at "60 fps" if you round up just a tiny bit.