emukidid / swiss-gc

Swiss - The swiss army knife of GameCube homebrew
GNU General Public License v2.0
1.23k stars 93 forks source link

[Issue]: Unable to reset back to swiss via igr.dol #809

Closed some-username-here1 closed 1 year ago

some-username-here1 commented 1 year ago

Describe the bug

I'm having an issue where the uncompressed file of swiss's dol, compressed file untested, is unable to be launched to from in-game when playing a gamecube game from my SD2SP2. I am not sure if this is because of launching swiss via game save exploit, such as Paper Mario: TTYD, or the game itself or game region I'm launching after the exploit, being Animal Crossing. My microSD card is a SanDisk SDHC ImageGate 32GB

Steps to reproduce

1) Execute a game save exploit for a supported game and get launched into swiss via boot.gci from the memory card 3) Launch any Gamecube iso 4) Execute the IGR button combination, being Start+A+Z 5) GameCube gets reset back to the startup logo playing

Expected behavior

1) Execute a game save exploit for a supported game and get launched into swiss via boot.gci from the memory card 2) Launch any GameCube game (or homebrew app) of choice 3) Reset back to swiss after a couple of seconds waiting, post-launch

Relevant log output

No response

Add screenshots

No response

Extrems commented 1 year ago

Duplicate of issue #745.

some-username-here1 commented 1 year ago

Are you sure this issue is a duplicate? my SD card is a Sandisk 32GB formatted to FAT32, not exFAT

Extrems commented 1 year ago

Do you have a autoexec.dol, boot.dol, boot2.dol, igr.dol or ipl.dol file in the root directory of your SD card?

some-username-here1 commented 1 year ago

I have IPL.dol, boot.dol and igr.dol, yes. Although any of those never worked, unless it breaks IGR when there's multiple?

some-username-here1 commented 1 year ago

By chance has the instructions or steps for setting up IGR has changed? Without being properly documented, too?

some-username-here1 commented 1 year ago

Can this issue be reopened? or has the issue been fixed in a new recent commit?