SD2Snes firmware is unresponsive.

[livesdlc]

Some games fail to connect to RA2snes, and I am getting the message "SD2Snes firmware is unresponsive." I tested different USB cables and older versions.
RA2Snes v1.1.2
QUsb2Snes v0.7.35
FXPAK PRO Firmware: 1.11.2
Games: Donkey Kong Country 2, Donkey Kong Country 3, The Magical Quest Starring Mickey Mouse [USA], Zelda: A Link to the Past.
Is it possible to connect using SNI?

[Factor-64]

This usually happens as the firmware usb interface soft crashes when getting info from the device. SNI functionality is broken in v1.1.2 due to a bug in QUsb2Snes that I made a hacky fix for. If you would like to try the beta to see if that fixes it you can with this link:
windows
linux
The beta supports SNI and is completely stable, I just haven't gotten around to fully testing it and ironing out some stuff for release. If you continue to have issues I would recommend joining the Usb2Snes Discord as there are some fixes involving OS settings that have helped some people

[livesdlc]

Great job, it's working with SNI.

I tested some achievements and found that of them are still not being triggered. These are the same issues I previously reported:

Turtles in Time: The achievements "The Leader", "The Baby Turtle", and "Where's the Ninjas??" were not triggered.
Some achievements that should unlock simultaneously in Turtles in Time are not being activated correctly. For example, "Finish the game as Raphael" and "The Final Challenge" were not triggered after completing the requirements.
The achievements "Turtle X-ing" and "A Little Too Raph..." also do not trigger simultaneously as expected. Only "Turtle X-ing" was activated, while "A Little Too Raph..." was not unlocked.
Super Mario World: The achievement "Change of Scenery" does not trigger.
It seems that some achievements are either not being detected correctly or are not triggering as expected, especially in cases where multiple achievements should unlock at the same time.

https://imgur.com/a/9NgyM8b

[Factor-64]

ill need to go back and look at the non-custom firmware implementation as in v1.1.2 I was doing very unsafe threading so data could get corrupted so i moved away from that and it seems non-custom firmware achievement evaluation has suffered.