I also tried converting all of the files to wavs (0Hz mono) and then into Doom Format which did not fix the problem. Classic Doom gZDoom Black Screen Fix? Submitted 2 years ago by Pixelcitizen98. Otherwise, I get just a simple black screen (with. So, when I try to start up GZDoom, the only thing that comes up is the cursor and the sound.
Gzdoom no sound drivers#
Just wanted to see if this was a known bug of some kind, or specific enough that someone will know a fix.Honestly it seems like it must be a soundcard issue of some kind, but I thought I would check here first in case there is a simple solution (and also because the sound used to work.)Using FMOD : All sound drivers are up to date. They are both.ogg files, but I tried converting the sound files to.wavs and replacing them in the wad and that didn't work either -also tried the 'convert wav to doom sound' in Slade, which did nothing.I have messed around with every sound option imaginable in Zdoom itself, although I haven't tried messing with my audio drivers yet. They make a popping sound and cut off completely and it is only these two sounds (well, I believe they're the same sound) that are not working everything else is working totally fine. I've recently started having a weird sound problem with Zdoom (same issue with GZdoom also) where the sound for the Realm667 M40A1 and Hunting Rifle don't work. If it starts to seem like a GZDoom bug I can post about it on the ZDoom forums, just want to determine that first. Has anyone seen artifacts like this before? I can provide whatever information is needed, I even know a bit about how GZDoom's OpenGL rendering works. I don't actualy know, so I'm asking here first. See the 16:40 mark in this video for an example:Oddly, it only happens in outdoor areas, so on the one hand this may be GZDoom doing something bad that exposes the problem in OBS, or on the other hand maybe it's something OBS should detect and fix.
Gzdoom no sound full#
When I try to put Brutal Doom over the main exe file, it shows me this error instead and does not launch at all.Hi, I've been streaming some Doom with OBS using the GZDoom source port, and haven't been able to figure out why these flickering artifacts happen when the game is running full screen. I think this also showed in the previous version too but I'm not sure and can't remember. It is currently 32.ĮDIT: did not work, open AL is in the files but doesn't seem to be in the sounds menu, and when I try to restart the sounds after changing the MIDI device or the sound channels, it says in game that it is initialising Fmod and not the one I set it to. It didn't work last time due to my not restarting. I changed to 2.2.0 after the problem started last night but that didn't fix it.
Gzdoom no sound upgrade#
That said, if you do upgrade to GZDoom 2.2.0, and FMOD Ex still doesn't work, you can now use OpenAL instead of FMOD Ex. Brutal Doom has a coding error that was ignored before ("0.l" is not an actual number) but which GZDoom will now complain about, and Marcos Abenante has stubbornly neglected to fix it even though it's been nearly a year now. the FMOD version it was compiled for has changed, so you'll need to replace the fmodex.dll with the one provided with the new GZDoom.
Gzdoom no sound update#
Be aware, if you update to GZDoom 2.2.0, that: (You can do that in the sound options menu.) Then quit, and restart.Īlso you're apparently using GZDoom 1.8.2, which is quite old. Try changing the value of snd_channels to something lower. Gaerzi: FMOD EX error code 77 is apparently FMOD_ERR_TOOMANYCHANNELS for this version of FMOD Ex.
0 kommentar(er)
