DS-Homebrew
IGM & screen swap not working in SMGDS 2022
Your console: DSi
Launch Method: SD card w/ Unlaunch
Version used: 80561c7
Game tested/used/applicable: Super Mario Galaxy DS (April 2022)
Expected Behavior: The in-game menu and screen swap functions would work correctly.
Actual Behavior: Attempting to swap screens will cause both screens to display nothing, until swapped back. Nothing is visible in the in-game menu, and it crashes with a white top screen after 45 seconds or so of being open.
Steps to reproduce
- Start SMGDS and begin a level
- Open the in-game menu or use the screen swap button combo
- If using the in-game menu, wait ~45 seconds for the white screen to occur
nds-bootstrap.ini
[NDS-BOOTSTRAP]
NDS_PATH = sd:/homebrew games/smgds.nds
SAV_PATH = sd:/homebrew games/saves/smgds.sav
DONOR_SDK_VER = 0
BOOTSTRAP_PATH = sd:/_nds/nds-bootstrap.nds
ROMREAD_LED = 3
BOOST_CPU = 0
DEBUG = 1
LOCK_ARM9_SCFG_EXT = 0
PATCH_MPU_REGION = 0
PATCH_MPU_SIZE = 0
LOGGING = 1
LOADING_SCREEN = 1
LANGUAGE = -1
DSI_MODE = 0
BOOST_VRAM = 0
SOUND_FIX = 1
GAME_SOFT_RESET = 1
CACHE_FAT_TABLE = 0
DMA_ROMREAD_LED = -1
CONSOLE_MODEL = 0
RAM_DRIVE_PATH = sd:/null.img
CARDENGINE_CACHED = 1
FORCE_SLEEP_PATCH = 0
EXTENDED_MEMORY = 0
CACHE_BLOCK_SIZE = 0
PRECISE_VOLUME_CONTROL = 1
SOUND_FREQ = 1
SDNAND = 0
MACRO_MODE = 0
HOTKEY = 284
GUI_LANGUAGE = en
REGION = -1
CARD_READ_DMA = 0
ASYNC_CARD_READ = 0
APP_PATH = sd:/VANILL~1/NINTEN~3.NDS
PRV_PATH = sd:/VANILL~1/SAVES/NINTEN~3.PRV
SWI_HALT_HOOK = 0
HOMEBREW_ARG =
B4DS_MODE = 2
USE_ROM_REGION = 1
Logs
Other notes
It's definitely doing something weird, the screen is pretty glitched in no$gba and it seems to be displaying from the sub engine for some reason (probably through display capture?) despite obviously being 3D... I'll try run it from nds-bootstrap in no$gba and see if I can't find out what's breaking the menu soon™, though might be better for the SMGDS devs to just fix whatever they're doing weird if possible.
It's definitely doing something weird, the screen is pretty glitched in no$gba and it seems to be displaying from the sub engine for some reason (probably through display capture?)
Maybe ask Gericom about it? He could probably explain what's going on with that side of things
Sounds like the dma that streams the captured 3d data to bg vram might overwrite the menu graphics and then runs out of control because it is not properly stopped
