Game Freezes (MK8D) on 17.0.0 firmware, Atmosphere 1.6.2

[kanagaroo]

Bug Report

What's the issue you encountered?

After creating an EmuMMC running latest atmosphere 1.6.2, unmodified, titles may experience freezes which prevent them for being played, yet work on original firmware 17.0.0. I experienced this consistently with Mario Kart 8 Deluxe.

How can the issue be reproduced?

I could consistently recreate this issue for MK8D via the following:

1. Create EmuMMC of 17.0.0 System Firmware which has MK8D ver. 3.0.1 (latest, no DLC) installed and running fine. This error also occurs with older versions of MK8D (1.0.0, 2.4.0, 3.0.0).
2. Install latest atmosphere 1.6.2 to EmuMMC .
3. Boot into CFW and launch MK8D.
4. Press "Single Player" or "Multi Player".
5. Game freezes on the following menu (one or two frames may be pumped out over the course of a minute or so, but does not crash). Therein soft-locking the game.
6. Minimizing the game from this frozen menu takes some time, and when attempting to close the software it gives the error: "The software was closed because an error occurred".

System Firmware Version

System version 17.0.0, atmosphere 1.6.2

Environment?

• What bootloader (fusèe, hekate, etc) was Atmosphère launched by: hekate
• Official release or unofficial build: Official release version 1.6.2
• Do you have additional kips or sysmodules you're loading: none
• Homebrew software installed: daybreak, reboot to payload, usb file transfer (all bundled in official release).
• EmuMMC or SysNAND: EmuMMC, file-based, FAT32 SD Card

Additional context?

• Additional info about your environment: Issue persists with older system firmwares (I tested 16.0.3 and 16.1.0, downgraded through daybreak) with atmosphere 1.6.2. I initially thought this was a 17.0.0 compatibility issue which appears to not be the case, but then again I am unsure if Atmosphere is backwards compatible with regards to system firmware.
• For further context, this was tested on an unpatched Erika model switch.

[masagrator]

Like a week ago I gave my nephews MK8D to play on emummc, 17.0.0 Atmosphere 1.6.2. No issues in singleplayer and 2P, even for an hour.

Uploading crash reports could help. It can be also an issue with your sdcard (corrupted emummc/game base or update).

Did you try to recreate emummc on different sdcard to check if issue still persists?

[kanagaroo]

Yeah, seen that it's been working for others so hence I'm a little stumped haha.

I've reformatted my SD card, so I would be hesitant to call corruption as the cause, but of course possible. I'll test with another SD card once I have one handy.

I'm also loading the game base from cartridge - but even the base 1.0.0 version has the same issue in the menus, so I don't believe anything to be wrong with the install.

Regarding crash reports: Atmosphere itself doesn't crash, I only get a generic switch error upon trying to close the application, so I don't think an atmosphere crash report is even generated (Fresh install of atmosphere so the atmosphere/crash_reports folder doesn't even exist). Is there another dump location that might have some useful info?

[kanagaroo]

Apologies for the close and reopen, missclick!

[masagrator]

I only get a generic switch error upon trying to close the application.

This is a crash and report is generated. Application crashing is not crashing whole system, but it is still a crash.

[kanagaroo]

Tried on another SD Card, with no luck.

Interestingly, I allowed the game to continue in the perceivingly frozen state (instead of force-closing it) while spamming A to get through the menus, and it will eventually get me through to the character select screen. I would have to wait about 10 minutes to get through. So it's more akin to a heavy drop in performance in those menus as opposed to a complete lock-out.

I also note when transitioning between menus, the performance returns to normal for a brief moment. If i wait in the menu long enough (I think - I haven't been able to recreate this consistently), the menu will stop lagging for a while, but the video playback of Mario will stop. Perhaps it is something to do with these videos in the menus?

After getting to the character select screen, everything runs completely normally (within a race, and the race menus) until I quit back out to the main menu and re-enter the single player or multiplayer menus.

This led me to believe that this might be something to do with my switch's internal hardware, but I can still boot up to the sysNAND and not experience the issue, so I'm inclined to keep this issue open until I can pin down the behaviour some more.

I'm still not seeing crash reports generated in any of the following folders after I get the error message when force-closing:
/atmosphere/erpt_reports/, /atmosphere/crash_reports/, /atmosphere/fatal_reports/.

[Masamune3210]

This is for issues with atmosphere, if you want general help, go elsewhere