-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
FD crashes if sound card removed #64
Comments
Hi - this might be related? These two settings (set as sound FX device) in FDSetup cause FDOOM to lock up during launch on my rig. It won't even respond to CTRL ALT DEL.
Selecting normal PC Speaker works fine (I selected the others by accident). Cheers |
What are your rig specs? The PWM mode abuses the system timers, maybe the system is not compatible with this idea. It works fine on my systems. |
Wow it's been over a year! Unfortunately I encountered this again, must've forgotten to run fdsetup. So I guess what's frustrating is trying to guess the sound card params in FDSETUP, saving and hoping for the best, only for FDOOM fall over at the sound initialisation part, requiring a hard reboot: Occasionally it will crash, with an error about sound card, which is fine as I can easily try FDSETUP again. Most of the time though, it gets stuck. I think Duke3D let you test your sound card in the SETUP which was nice. I'm using UNISOUND to setup my sound card, which magically works for all the usual games like Keen, Jazz, Wolf3D. Thanks again! |
I've uploaded a new release, can you test if it still crashes? Thanks! |
You might want to update the title to something more intelligent sounding 馃榿
Basically, (this could be a DOOM issue), if I remove my soundcard (when machine off of course) or REM out UNISOUND (sound card driver), FastDoom gets stuck when trying to load a game/episode.
I have to hard reset my machine to recover. Occassionally I'm fiddling with autoexec.bat/config.sys which is why I bypass some drivers and forget until I try to play Doom.
Obviously an edge case, it just seems to not like any changes to soundcard environment. Hope that made sense!
The text was updated successfully, but these errors were encountered: