DS game is not picking up save file in saves folder

[coyote1284]

Your console: New3DSXL Launch Method: Luma; nds-bootstrap; TWiLight Menu++ Version used: Bootstrap v0.35.1, TM v15.1.1 Flashcart used: System SD Game tested/used/applicable: Final Fantasy 4 Heroes of Light

Expected Behavior: Main game menu has Continue option for loading saved game. Actual Behavior: Only New Game displays

Steps to reproduce

Logs

Other notes

Save file is and has been in DS/saves folder; save loaded properly before 15.1.1 update.

[RocketRobz]

Does the same issue happen with other games?

[coyote1284]

Unfortunately, FF:4HoL was the only game I had progress on since converting to CFW.  I loaded up a different game that had no progress, Luminous Arc, until I could make the first save. (BTW, LA had overlapping duplicate text boxes.) Exited TWiLight and turned off 3DS. After I turned the 3DS back on, I explored the file structure via FTP and found both save files in the "saves" folder. Started TWiLight, (Huh? 4HoL is displaying as "DS Program File... maybe it got corrupted, I hope not from the anti-piracy 'cheat') LA save was recognized. I will try removing 4HoL and copying a new copy to the 3DS SD and update later.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, June 12, 2020 8:29 PM, RocketRobz notifications@github.com wrote:

Does the same issue happen with other games?

—

You are receiving this because you authored the thread.

Reply to this email directly, view it on GitHub, or unsubscribe.[https://github.com/notifications/beacon/AP6CAQXN4ZHGMRD2FVXCYBLRWLI7XA5CNFSM4N4YN6HKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZN4NCQ.gif]

[coyote1284]

Update, replacing 4HoL copy on SD did not resolve the problem, nor did changing save location under the game settings (from 0 to 1) or turning off the "save anywhere" cheat.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, June 12, 2020 8:29 PM, RocketRobz notifications@github.com wrote:

Does the same issue happen with other games?

—

You are receiving this because you authored the thread.

Reply to this email directly, view it on GitHub, or unsubscribe.[https://github.com/notifications/beacon/AP6CAQXN4ZHGMRD2FVXCYBLRWLI7XA5CNFSM4N4YN6HKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZN4NCQ.gif]

[2ndstatus]

Same issue as OP, except it seems as though this happened after I mounted the SD in my PC to transfer over some files. No roms, Saves, or anything relating to the bootstrap were manipulated or edited.

Your console: New2DSXL Launch Method: nds-bootstrap; TWiLight Menu++ Version used: Bootstrap v0.35.1, TM v15.1.1 Flashcart used: MicroSD 64GB Game tested/used/applicable: Jump Ultimate Stars (english patched)

Expected Behavior: When the game starts, an opening plays. The opening is a non-skipable opening only unless you have already had a save file for the game itself. Pressing start with a save file skips the opening. Actual Behavior: Opening plays in it's entirety and wants to autosave over the existing file

Other notes Save file is and has been in DS/saves folder. The save was originally made in v15.11, and will work normally after an initial save, but will cease if the SD Card is removed. With a bit more testing, it seems the Game listed is the only game affected out of the 10 other romsin my SD Card

[ahezard]

Another user : Ishuka is reporting the issue via discord. All of his games are affected. This problem seems to be quite frequent and not related to a specific game.

[ahezard]

Ishuka fixed this : "I was so mad that the .IMG file didn't work that I simply decided to take all of my files and transer them to a new card (16GB) to take a .IMG of that SDCARD. I just plugged it in my 3DS to see if all files were in, and Boom, saves started booting. Just to be clear, I think my SD Card was somehow broken enough to make the saves unable to be applied, but not broken enough so that the system will work." So I suggest users affected by this issue to do the same.

[ahezard]

I still suspect that nds-boostrap itself may have corrupted the sd card somehow The fat table caching may trigger something like that in some rare cases if the cache fat table on the disk became no more synchronized with the real fat table. This may happen if you copy / move file around, never copy an existing fat table cache file to a new disk for example.

[ahezard]

It may possible to implement some check on the fat table cache file in order to detect a change that requires to rebuilt it.

[coyote1284]

By the way, is it normal to have more than just the game saves in the saves folder, like copies of folders and files also found in the /_nds/TWiLightMenu folder?

Sent from ProtonMail mobile

-------- Original Message -------- On Jun 15, 2020, 2:57 PM, ahezard < notifications@github.com> wrote:

It may possible to implement some check on the fat table cache file in order to detect a change that requires to rebuilt it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[coyote1284]

Well, what doesn't work is this:

I copied my original save for 4HoL to my computer. Loaded back up 4HoL and got as quickly as possible to first chance to save, which overwrote the original save on the SD. Quit TWiLight and went back in and Continue was available to the new save. So I quit and copied the original save from my computer back to the SD, overwriting the new save. Only New Game showed when I returned to the game.

Luminous Arc still had save avaliable. I may be starting 4HoL over yet again.

Sent from ProtonMail mobile

-------- Original Message -------- On Jun 15, 2020, 2:57 PM, ahezard < notifications@github.com> wrote:

It may possible to implement some check on the fat table cache file in order to detect a change that requires to rebuilt it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[ahezard]

I thought again about this and crosschecked nds-boostrap code, it extremely unlikely that a bug in nds-bootstrap can cause any sd card corruption :

• the rom file that have the FAT table cached is accessed only via read operations
• write operation are done only to the save file that does not have persistent FAT table cache is actually extremely limited in order to prevent sd corruption, it can write only to already allocated sector and cannot append data to a save file

So the worse that can happen is to corrupt the save file itself while you are playing but not the whole file system.

[coyote1284]

IOW the save was corrupted in a previous saving operation (in my case, likely from the cheat that allows saving anywhere) and thus would never work again. Sigh, so I start 4HoL from beginning, again.

Sent from ProtonMail mobile

-------- Original Message -------- On Jun 15, 2020, 3:59 PM, ahezard < notifications@github.com> wrote:

I thought again about this and crosschecked nds-boostrap code, it extremely unlikely that a bug in nds-bootstrap can cause any sd card corruption :

• the rom file that have the FAT table cached is accessed only via read operations
• write operation are done only to the save file that does not have persistent FAT table cache is actually extremely limited in order to prevent sd corruption, it can write only to already allocated sector and cannot append data to a save file

So the worse that can happen is to corrupt the save file itself while you are playing but not the whole file system.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[RocketRobz]

Can you try updating Nightly bootstrap, and then setting Nightly in TWLMenu++ Settings, and see if the latest nightly fixes this?

[coyote1284]

That did not help.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, June 16, 2020 1:18 AM, RocketRobz notifications@github.com wrote:

Can you try updating Nightly bootstrap, and then setting Nightly in TWLMenu++ Settings, and see if the latest nightly fixes this?

—

You are receiving this because you authored the thread.

Reply to this email directly, view it on GitHub, or unsubscribe.[https://github.com/notifications/beacon/AP6CAQXRNOSGJVI7REWP2PTRW4FDVA5CNFSM4N4YN6HKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZVSHCA.gif]

[RocketRobz]

What's the nds-bootstrap commit number shown in TWLMenu++ Settings?

[coyote1284]

a31f6d4b

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, June 16, 2020 10:21 AM, RocketRobz notifications@github.com wrote:

What's the nds-bootstrap commit number shown in TWLMenu++ Settings?

—

You are receiving this because you authored the thread.

Reply to this email directly, view it on GitHub, or unsubscribe.[https://github.com/notifications/beacon/AP6CAQW3RABYNH36XYE5E7LRW6EXLA5CNFSM4N4YN6HKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZXV75I.gif]

[RocketRobz]

Is Save FAT table cache turned on or off?

[coyote1284]

It is set to No

Sent from ProtonMail mobile

-------- Original Message -------- On Jun 16, 2020, 10:27 AM, RocketRobz < notifications@github.com> wrote:

Is Save FAT table cache turned on or off?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[Kaisaan]

Since there haven't been any reports of this issues in a while (almost 2 years), I think it's good to assume that this issue has been fixed. Closing.