After Windows Updated, It killed Chocolate Doom's sound, AGAIN.

[forgettable pyromaniac]

Alright, time for "Microshaft fucked up", version two.

This happened to me before, I fixed it by simpily updating my version of Choco Doom, but now that I'm on the latest version, and the audio is completely fucked again after my windows update, I'm at a loss for what to do. I tried the latest devbuilds from the chocolate-doom website, but no dice on those either. ChocoRenderLimits, however, works perfectly okay.

Audio settings are fine and are in working order, I tried all possible audio combinations in the setup exe, and the sliders in game are at max.
(I also just learned that the volume mixer slider for the program isn't even there - it's like windows doesn't recognize it at all.)
Everything else works, but for some reason, not this. What the hell, Microsoft.

Ok basically - what other options should I try to get the audio working for Choco Doom?

Edited June 16, 2022 by forgettable pyromaniac

[Edward850]

Windows isn't the cause of your problem, obviously because if it was everyone would be having the same problem, so focusing exclusively on that isn't going to fix anything.

 

Make sure your primary sound device is set correctly. Delete chocolate Doom's existing config files as well to make sure everything is reset. Is chocolate render limits the 3.0.0 version or the old SDL1 version? If it's the new version, try copying over it's config into chocolate doom. If it's old version, it could be a fault your sound drivers are experiencing, you can try redownloading their latest drivers.

Edited June 16, 2022 by Edward850

[forgettable pyromaniac]

3 hours ago, Edward850 said:

Windows isn't the cause of your problem, obviously because if it was everyone would be having the same problem, so focusing exclusively on that isn't going to fix anything.

 

Make sure your primary sound device is set correctly. Delete chocolate Doom's existing config files as well to make sure everything is reset. Is chocolate render limits the 3.0.0 version or the old SDL1 version? If it's the new version, try copying over it's config into chocolate doom. If it's old version, it could be a fault your sound drivers are experiencing, you can try redownloading their latest drivers.

It's actually ALL SDL2 applications - Chocolate Doom, Crispy too, ECWolf straight up crashes, mGBA doesn't load anything, but the software opens.

[Edward850]

Then yeah, seems like an audio driver issue that the SDL2 mixer is tripping up on. Reinstall the latest audio driver for your hardware, and make sure the correct sound device is set as your primary.

Edited June 17, 2022 by Edward850

[forgettable pyromaniac]

20 minutes ago, Edward850 said:

Then yeah, seems like an audio driver issue that the SDL2 mixer is tripping up on. Reinstall the latest audio driver for your hardware, and make sure the correct sound device is set as your primary.

both are correct - nothing.
I think it's and SDL issue of some kind, because it's not just audio. things that rely on it for video and such also don't work properly.

[Edward850]

It's too exclusive of a problem to be an SDL2 issue, given it's only happening to you. It's an issue SDL2 is exposing but it itself is not where the problem lies. If I started getting unexplainable problems, the first thing I'd be looking at is if the hard-drive is in good condition, and from there clean reinstall the whole OS and stick to only installing drivers necessary to run an SDL2 game to eliminate or isolate any potential driver or service failure.

Edited June 17, 2022 by Edward850

[forgettable pyromaniac]

12 hours ago, Edward850 said:

It's too exclusive of a problem to be an SDL2 issue, given it's only happening to you. It's an issue SDL2 is exposing but it itself is not where the problem lies. If I started getting unexplainable problems, the first thing I'd be looking at is if the hard-drive is in good condition, and from there clean reinstall the whole OS and stick to only installing drivers necessary to run an SDL2 game to eliminate or isolate any potential driver or service failure.

ouch. I really don't wanna do that unless I have to. I could try opening it in safe mode, though.

 

edit - just tried in safe mode. for the games that would open, it STILL wouldn't function.

Edited June 17, 2022 by forgettable pyromaniac