DS-Homebrew / nds-bootstrap

Boot an nds file
https://wiki.ds-homebrew.com/nds-bootstrap/
GNU General Public License v3.0
1.19k stars 75 forks source link

Fire Emblem : Shadow Dragon - Red Screen #1356

Closed Fu2chN closed 2 years ago

Fu2chN commented 2 years ago

Your console: New 3DS XL

Launch Method: SD Card

Version used: TWiLight Menu++: v24.1.0 nds-bootstrap: Release v0.54.1

Game tested/used/applicable: FIREEMBLEM11_YFEP01_00.trim.nds Ver. SDK: 4.2 NTR-YFEP-EUR Title ID: 0004800459464550

Expected Behavior: The game start correctly.

Actual Behavior: The game not start, red screen on boot

Steps to reproduce

  1. Juste launch the game by TWiLight Menu++ or the forwarder.

nds-bootstrap.ini

NDS_PATH = sd:/roms/ds/FIREEMBLEM11_YFEP01_00.trim.nds
SAV_PATH = sd:/roms/ds/saves/FIREEMBLEM11_YFEP01_00.trim.sav
BOOST_CPU = 0
DEBUG = 0
LOCK_ARM9_SCFG_EXT = 0
CACHE_FAT_TABLE = 0
BOOST_VRAM = 0
CARD_READ_DMA = 1
ASYNC_CARD_READ = 0
DSI_MODE = 1
SWI_HALT_HOOK = 1
EXTENDED_MEMORY = 0
DONOR_SDK_VER = 0
PATCH_MPU_REGION = 0
PATCH_MPU_SIZE = 0
CONSOLE_MODEL = 2
LANGUAGE = -1
LOGGING = 1
REGION = -2
RAM_DRIVE_PATH = sd:/null.img
GUI_LANGUAGE = fr
USE_ROM_REGION = 1
FORCE_SLEEP_PATCH = 0

Logs

NDSBTSRP.LOG

Screenshots

1645549745734

RocketRobz commented 2 years ago

Your ROM is most likely corrupt, as the game boots on my side. Try replacing your ROM, and/or turn off cheats.

Fu2chN commented 2 years ago

mmh, i'dump my rom by gm9 it's a correct way ?

RocketRobz commented 2 years ago

Yes. Are cheats enabled?

Fu2chN commented 2 years ago

All setting are Default

RocketRobz commented 2 years ago

Both the USA and EUR versions boot on my side, all with default settings and no cheats. Try re-dumping your ROM, as it might've got corrupt somehow.

Fu2chN commented 2 years ago

Yep, I'm look that.

Fu2chN commented 2 years ago

Ok my gamecard have a probleme. I tested why other fire emblem rom and it's work. Thx for this app ^^

RocketRobz commented 2 years ago

You're welcome!

Fu2chN commented 2 years ago

I fixed the bug by updating godmode9 to 2.1.0 (I was on 1.9.3pre1).

RocketRobz commented 2 years ago

I fixed the bug by updating godmode9 to 2.1.0 (I was on 1.9.3pre1).

Ah, nice. Glad to hear it's fixed!