Continuing after out of lives in Lionheart often causes the entire Windows sound environment to die.

[MrBlastman]

This is an odd bug. Probably one of the strangest ones I have seen in a long time. And it is isolated to the game "Lionheart" for the Amiga in pUAE.

For whatever reason, if I run out of lives and have to continue, a good percentage of the time the game audio will die.

Except...

This affects Windows 10, and everything Windows 10, as well.

The only fix being a total reboot.

I have a dedicated soundcard - Sound Blaster AE7, and you can hear a crackle immediately after pressing continue when this happens, and poof, silence.

Updating to the latest Nightly core build gave one minor improvement: In the older build, dated 11/20/25, I had a 100% chance of sound loss. Now I have a lower one--maybe 50%, but chancing continuous reboots is annoying. This should not happen.

I am also on the Steam version of Retroarch, using the release build.

[sonninnos]

Host soundcards can not possibly matter since cores do not communicate with them directly, but simply push sound data to the frontend audio driver. Impossible to guess anything without a log.

[MrBlastman]

I have switched Retroarch audio drivers between xaudio and directx, and the issue happens with both.

Will the vanilla Retroarch log suffice? I will reboot for science. :)

[sonninnos]

There are no other useful logs than regular RA log with both log levels at 0. What is also important to know is what happens in standalone WinUAE 5.3.1. Also cores are always "nightly".

Edit: Tried to continue until game over with WHDLoad slave version 2.2 with both full and dma cycle-exact, and no audio issues of any kind.

Edit2: Accidental pin, whoops