Homebrew [DS(i)/3DS] TWiLight Menu++ - GUI for DS(i) games, and DS(i) Menu replacement

[RocketRobz]

Before I get too deep into chasing the issue, does the AP patch feature work for you on Mario vs DK Mini-Land Mayhem (USA)?
I have everything apparently set up correctly but I still get the issue reported in the compatibility list. I also noticed that the AP_FIX_PATH field in the nds-bootstrap.ini file is blank after I force-close the game, so I think it may not be writing it in the first place. Writing it by hand before launch did not work for me either.

Did you update both TWLMenu++ and nds-bootstrap?
Also, if you're referring to the glitched sprites, that's not caused by AP.

 

[themanuel]

Yet, both are up to date, according to the updater. I am able to launch the game but I can't see the sprites, and the game crashes eventually. The first time it crashed after the introduction and afterwards it was crashing in other places.

Do you think then, that this is not due to AP measures, but rather a general nds-bootstrap compatibility issues with this game?


PS:
I should clarify, sprites do not show up at all, instead of just being glitched.

 

[NANASHI89]

In Twiligiht Menu ++, is there anyway to get DS ROMs to display their file name, and not the name as seen in the DS(i) menu? I'm using the Saturn Theme.

 

[RocketRobz]

In Twiligiht Menu ++, is there anyway to get DS ROMs to display their file name, and not the name as seen in the DS(i) menu? I'm using the Saturn Theme.

You can see it in the per-game settings.

 

[Kupa]

I recently had to do a new install of homebrew on one of my 3ds (original non xl) due to some issues, and now I cant open twilight menu, it just gives me two black screens and doesnt do anything, and returns to the 3ds main menu when any face button is pressed. Any ideas of what i could do to get it working?

 

[RocketRobz]

I recently had to do a new install of homebrew on one of my 3ds (original non xl) due to some issues, and now I cant open twilight menu, it just gives me two black screens and doesnt do anything, and returns to the 3ds main menu when any face button is pressed. Any ideas of what i could do to get it working?

https://3ds.hacks.guide/troubleshooting#dsi--ds-functionality-is-broken-after-completing-the-guide

 

[themanuel]

Yet, both are up to date, according to the updater. I am able to launch the game but I can't see the sprites, and the game crashes eventually. The first time it crashed after the introduction and afterwards it was crashing in other places.

Do you think then, that this is not due to AP measures, but rather a general nds-bootstrap compatibility issues with this game?


PS:
I should clarify, sprites do not show up at all, instead of just being glitched.

I just verified that the Europe version does the exact same thing: no sprites for the mini Marios are shown. This leads me to believe that the patch is not being applied.
Could somebody that has this game verify if the problem occurs on their system?

 

[RocketRobz]

I just verified that the Europe version does the exact same thing: no sprites for the mini Marios are shown. This leads me to believe that the patch is not being applied.
Could somebody that has this game verify if the problem occurs on their system?

The glitched/no sprite issue is an nds-bootstrap issue, not AP.
The AP issue is when starting a new game, it crashes on a black screen.

 

[themanuel]

The glitched/no sprite issue is an nds-bootstrap issue, not AP.
The AP issue is when starting a new game, it crashes on a black screen.

Got it. Thanks.

 

[sion_zaphod]

@Robz8 I know i'm asking a few questions between this thread and the gbarunner2 one but as there is widescreen support on 3ds via OTF ips patches. Would it be possible to enable twilightmenu to use widescreen just for 3DS?

 

[RocketRobz]

@Robz8 I know i'm asking a few questions between this thread and the gbarunner2 one but as there is widescreen support on 3ds via OTF ips patches. Would it be possible to enable twilightmenu to use widescreen just for 3DS?

If you mean for the GUI, yes, but that'll increase boot time.

 

[sion_zaphod]

If you mean for the GUI, yes, but that'll increase boot time.

I don't mind waiting a few seconds more if it looks better.

 

[themanuel]

The glitched/no sprite issue is an nds-bootstrap issue, not AP.
The AP issue is when starting a new game, it crashes on a black screen.

Beating on the dead horse: I just noticed that when I launch the game, I get the message about AP, which is not supposed to appear when there is an ips patch for the game. I can see the ips file in the apfix folder ("V2GE-CC32.ips"), and when I open my game in a hex editor, I can confirm that the game's ID is "V2GE01".

Understanding that the game has glitches, even with the AP patch applied, I believe that getting the AP screen confirms that the patch is not being applied in my case, even thought it is available in the ipfix folder. I am able to load other AP sensitive games like Pokemon HeartGold and don't get the message, the game doesn't freeze, and I can see that nds-boostrap.ini has the game's ips file name added into the ap_fix_path variable.

Am I on to something here or still treading water?

 

[RocketRobz]

Beating on the dead horse: I just noticed that when I launch the game, I get the message about AP, which is not supposed to appear when there is an ips patch for the game. I can see the ips file in the apfix folder ("V2GE-CC32.ips"), and when I open my game in a hex editor, I can confirm that the game's ID is "V2GE01".

Understanding that the game has glitches, even with the AP patch applied, I believe that getting the AP screen confirms that the patch is not being applied in my case, even thought it is available in the ipfix folder. I am able to load other AP sensitive games like Pokemon HeartGold and don't get the message, the game doesn't freeze, and I can see that nds-boostrap.ini has the game's ips file name added into the ap_fix_path variable.

Am I on to something here or still treading water?

Check the header CRC in the ROM as well. It's at 0x15E in the ROM.

 

[themanuel]

I'm afraid I don't know how to do that, but the dump checks out fine against the no-intro dat ("Nintendo DS Decrypted"), with CRC of 17989fe4.

 

[RocketRobz]

I'm afraid I don't know how to do that, but the dump checks out fine against the no-intro dat ("Nintendo DS Decrypted"), with CRC of 17989fe4.

Use a hex editor to open the ROM and go to that offset.

 

[themanuel]

This is what I see on the first page. I'm not sure which offset I should examine:

 

[RocketRobz]

This is what I see on the first page. I'm not sure which offset I should examine:

Ah, I see now.
It's Rev 2 of the ROM. That one isn't supported yet.

AP-patch the ROM using DS-Scene ROM Tool, then make the .ips using LunarIPS, and upload it here.

 

[themanuel]

Ah, I see now.
It's Rev 2 of the ROM. That one isn't supported yet.

AP-patch the ROM using DS-Scene ROM Tool, then make the .ips using LunarIPS, and upload it here.

Hmm, when I tried to create the ips file with LunarIPS, based on the modified file created by DS Scene Rom Tools, I get the error below. The original .nds file is 32MB and the AP patched one is 26.3MB and I am not selecting any trimming when patching. If I select to safe-trim it, the resulting file is actually closer in size, and I still get that error.
https://imgur.com/Yw0ciG9

 

[RocketRobz]

Hmm, when I tried to create the ips file with LunarIPS, based on the modified file created by DS Scene Rom Tools, I get the error below. The original .nds file is 32MB and the AP patched one is 26.3MB and I am not selecting any trimming when patching. If I select to safe-trim it, the resulting file is actually closer in size, and I still get that error.
https://imgur.com/Yw0ciG9

Using a hex editor, insert `FF` bytes to the end of the AP-patched file, 'til it reaches 1FFFFFF.