Frisky Posted April 18, 2016 I was going to start playing on GZDoom again after a while, so I deleted a few unneeded WADs and PK3s. I started GZDoom, but there is no sound or music. I'm not sure what the problem is. I've checked my sound settings and volume, but I don't know how to solve it. Can somebody please help? 0 Share this post Link to post
Danfun64 Posted April 18, 2016 You posted too little information about your problem. Operating system? Architexture? Sound Drivers? Sound card? Version of GZDoom? *avoids getting shot by Damerell* 0 Share this post Link to post
Edward850 Posted April 18, 2016 Or more importantly, the startup log! (Start GZDoom with +logfile somelogfilename.txt) "Help I have an error" is not as descriptive as showing us what the error actually is. 0 Share this post Link to post
Frisky Posted April 18, 2016 Edward850 said:Or more importantly, the startup log! (Start GZDoom with +logfile somelogfilename.txt) "Help I have an error" is not as descriptive as showing us what the error actually is. How do I start GZDoom with that? Also, it's just straight up not even working anymore since I updated to 2.1.1. Danfun64 said:You posted too little information about your problem. Operating system? Architexture? Sound Drivers? Sound card? Version of GZDoom? *avoids getting shot by Damerell* My operating system is Windows 10 and like I said, my version of GZDoom is 2.1.1. 0 Share this post Link to post
Edward850 Posted April 18, 2016 Frisky said:How do I start GZDoom with that? Also, it's just straight up not even working anymore since I updated to 2.1.1. Batch file or command line, like any other launch command. 0 Share this post Link to post
Frisky Posted April 18, 2016 Edward850 said:Batch file or command line, like any other launch command. Honestly, I need a step-by-step tutorial on how to do that, because I have never actually done that before or seen anybody do that. 0 Share this post Link to post
scifista42 Posted April 18, 2016 Make sure that the following files are in your GZDoom folder: "gzdoom.pk3", "fmodex.dll", "libsndfile-1.dll", "OpenAL32.dll". My suspiction is that maybe you accidentally deleted one or more of them. 0 Share this post Link to post
Edward850 Posted April 18, 2016 Frisky said:Honestly, I need a step-by-step tutorial on how to do that, because I have never actually done that before or seen anybody do that. We've been doing it for atleast 20 years of Windows. In Windows 10, you can hold shift+right click the empty space in your GZDoom folder (with nothing selected), and select the option "open command window here". Then it's just as simple as typing 'gzdoom +logfile thisisstillalogfilename.txt' and hitting enter. You have several other ways you can open a command prompt as well. Windows 10 especially doesn't exactly hide it. 0 Share this post Link to post
Frisky Posted April 18, 2016 Thanks! This is the full log. Spoiler Log started: Mon Apr 18 02:21:25 2016 M_LoadDefaults: Load system defaults. Using program directory for storage Gameinfo scan took 0 ms W_Init: Init WADfiles. adding C:/Users/Ace/Games/GZDoom/gzdoom.pk3, 610 lumps adding ./doom2.wad, 2919 lumps I_Init: Setting up machine state. CPU Speed: 2295 MHz CPU Vendor ID: GenuineIntel Name: Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz Family 6, Model 42, Stepping 7 Features: MMX SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 I_InitSound: Initializing FMOD FMOD Sound System, copyright © Firelight Technologies Pty, Ltd., 1994-2009. Loaded FMOD version 4.44.61 V_Init: allocate screen. S_Init: Setting up sound. ST_Init: Init startup screen. Checking cmd-line parameters... S_InitData: Load sound definitions. G_ParseMapInfo: Load map definitions. Texman.Init: Init texture manager. ParseTeamInfo: Load team definitions. LoadActors: Load actor definitions. R_Init: Init Doom refresh subsystem. DecalLibrary: Load decals. M_Init: Init menus. P_Init: Init Playloop state. ParseSBarInfo: Loading default status bar definition. ParseSBarInfo: Loading custom status bar definition. D_CheckNetGame: Checking network game status. player 1 of 1 (1 nodes) I_InitInput I_StartupMouse I_StartupKeyboard I_StartupXInput I_StartupRawPS2 I_StartupDirectInputJoystick Warning: 'Object' is freed outside the GC process. And like I said, GZDoom just simply "won't work." 0 Share this post Link to post
Edward850 Posted April 18, 2016 GZDoom seems to be starting up your sound fine. It's either an external problem (you haven't accidentally muted GZDoom in the windows mixer have you?) or a conflict that GZDoom isn't picking up (you must be using only the DLLs packaged with the build of GZDoom you grabbed). Make sure you're also running the latest build. Still failing that, also try removing your gzdoom-Ace.ini config file. 0 Share this post Link to post
Graf Zahl Posted April 18, 2016 And of course, try switching the sound system to OpenAL and see if that makes any difference. 0 Share this post Link to post
Frisky Posted April 18, 2016 Edward850 said:GZDoom seems to be starting up your sound fine. It's either an external problem (you haven't accidentally muted GZDoom in the windows mixer have you?) or a conflict that GZDoom isn't picking up (you must be using only the DLLs packaged with the build of GZDoom you grabbed). Make sure you're also running the latest build. Still failing that, also try removing your gzdoom-Ace.ini config file. I got the latest build and GZDoom still continues to be broken. 0 Share this post Link to post
Master O Posted April 18, 2016 Frisky said:I got the latest build and GZDoom still continues to be broken. Does your sound card work in other applications? Are you only experiencing the problem in GZDoom? 0 Share this post Link to post
Frisky Posted April 19, 2016 Master O said:Does your sound card work in other applications? Are you only experiencing the problem in GZDoom? Yes. It works perfectly in ZDoom, but not GZDoom. 0 Share this post Link to post
Graf Zahl Posted April 19, 2016 Then it must be a configuration problem, since both engines use the same sound library. 0 Share this post Link to post
Maes Posted April 19, 2016 There's also the possibility that you have ended up with a "Franken-GZDoom" installation: a mixture of new and old libraries and user .ini files as a result of "installing" (actually, just unzipping a file) into the same folder over multiple revisions. Most of the time, it will work asymptomatically. Other times, it will clamorously fail. 0 Share this post Link to post
Chipper35 Posted November 12, 2019 A very helpful discussion.....thanks to all! 0 Share this post Link to post
DwarfCleric Posted November 26, 2019 Always extract GZdoom ZIP to a new clean folder, start it up and it will create the INI file by itself. Don't re-use files from past versions, or in-between versions. Also, for people that don't have OpenGL3, there's LZdoom (Legacy gzdoom) which retains compatibility with mods 0 Share this post Link to post
Arkoree Posted February 25, 2021 how do you change it back to openAL tho, sorry for bumping the thread 0 Share this post Link to post
Kappes Buur Posted February 28, 2021 On 2/25/2021 at 2:32 PM, Arkoree said: how do you change it back to openAL tho, sorry for bumping the thread Options - Options Search Type in OpenAL Choose your preferred settings 0 Share this post Link to post