Your console: DSi
Launch Method: Launched through Twilight Menu 22.1.0. My DSi is on the latest firmware (North American) and is set to automatically launch Twilight Menu on boot. I have Unlaunch 2.0 installed. HiyaCFW is not installed.
Version used: 0.49.0
Game tested/used/applicable: lolSnes 1.1 latest git build (01/01/2014) (http://lolsnes.kuribo64.net/download.php)
Expected Behavior: Super Mario World (also applies to compatible Super Mario World romhacks) title screen logo and wooden border should have been visible. Black artifacts on the title screen shouldn't have been there. The title screen menu and text boxes should have worked fine. World map HUD shouldn't have been corrupted. Level HUD should have been visible. melonDS and DeSmuME both exhibit correct behavior:
MelonDS:
www.youtube.com/watch?v=LMyNE5tCQWY
DeSmuME:
https://youtu.be/GhJvj_ojdagActual Behavior: Title screen logo and wooden border were absent. Black artifacts were present on the title screen. The title screen menu looked corrupted and text boxes were missing text. World map HUD looked corrupted. Level HUD wasn't visible (reserve item aside). Video:
https://www.youtube.com/watch?v=8z7_gnONX4U (may still be processing)
Steps to reproduce
Put lolSnes on your SD card root. Create an "snes" folder on your SD card root and put your Super Mario World ROM inside of it. Launch lolSnes and launch Super Mario World from it.
nds-bootstrap.txt
Multiple configurations were tested. Setting "Run in" to "DSi mode" prevented lolSnes from launching, setting "ARM9 CPU Speed" to "133mhz (TWL)" increased performance and setting "Direct Boot" to "Yes" got lolSnes stuck on the splash screen. The graphical issues weren't affected. The configuration attached was the one used in the video. The log, however, was taken after the video was recorded since I'd forgotten to turn logging on while recording.
Super Mario World was the only one tested, but more games are very likely affected.
EDIT: Oh, right, the reason I think this may be a regression is that the compatibility list makes no mention of any issue with lolsnes.
Your console: DSi Launch Method: Launched through Twilight Menu 22.1.0. My DSi is on the latest firmware (North American) and is set to automatically launch Twilight Menu on boot. I have Unlaunch 2.0 installed. HiyaCFW is not installed. Version used: 0.49.0 Game tested/used/applicable: lolSnes 1.1 latest git build (01/01/2014) (http://lolsnes.kuribo64.net/download.php)
Expected Behavior: Super Mario World (also applies to compatible Super Mario World romhacks) title screen logo and wooden border should have been visible. Black artifacts on the title screen shouldn't have been there. The title screen menu and text boxes should have worked fine. World map HUD shouldn't have been corrupted. Level HUD should have been visible. melonDS and DeSmuME both exhibit correct behavior: MelonDS: www.youtube.com/watch?v=LMyNE5tCQWY DeSmuME: https://youtu.be/GhJvj_ojdag Actual Behavior: Title screen logo and wooden border were absent. Black artifacts were present on the title screen. The title screen menu looked corrupted and text boxes were missing text. World map HUD looked corrupted. Level HUD wasn't visible (reserve item aside). Video: https://www.youtube.com/watch?v=8z7_gnONX4U (may still be processing)
Steps to reproduce
Put lolSnes on your SD card root. Create an "snes" folder on your SD card root and put your Super Mario World ROM inside of it. Launch lolSnes and launch Super Mario World from it. nds-bootstrap.txt
Logs
NDSBTSRP.LOG
Other notes
Multiple configurations were tested. Setting "Run in" to "DSi mode" prevented lolSnes from launching, setting "ARM9 CPU Speed" to "133mhz (TWL)" increased performance and setting "Direct Boot" to "Yes" got lolSnes stuck on the splash screen. The graphical issues weren't affected. The configuration attached was the one used in the video. The log, however, was taken after the video was recorded since I'd forgotten to turn logging on while recording. Super Mario World was the only one tested, but more games are very likely affected. EDIT: Oh, right, the reason I think this may be a regression is that the compatibility list makes no mention of any issue with lolsnes.