search

ZDoom / gzdoom

GZDoom is a feature centric port for all Doom engine games, based on ZDoom, adding an OpenGL renderer and powerful scripting capabilities
http://zdoom.org
GNU General Public License v3.0
2.52k stars 545 forks source link

[BUG] binaries built with "auto-setup-windows.cmd" fail to initialize audio #2780

Open rooScream opened 1 week ago

rooScream commented 1 week ago

GZDoom version

g4.14pre-30-g40546420b

Which game are you running with GZDoom?

Doom 2

What Operating System are you using?

Windows 10

Please describe your specific OS version

Windows 10 Pro

Relevant hardware info

i3-10110U, UHD Graphics, Vulkan 1.3, D3D 12_1 feature level, Intel(R) Display Audio

Have you checked that no other similar issue already exists?

A clear and concise description of what the bug is.

When building gzdoom with the auto-setup-windows.cmd script, the resulting binaries do not detect any sound cards, HDMI audio, or onboard audio. The built ZMusic DLLs contain no version information.

Console output:

S_Init: Setting up sound.
Sound init failed. Using nosound.

Upping the developer/debug level doesn't reveal any further details.

I have also tested the script on two additional Windows 10 Pro computers:

Computer 1: Board Form factor: ATX Board: ASUS ROG STRIX X670E-A CPU: AMD Ryzen 9 7950X3D Audio: ESS Sabre DSP, Solid State amp GPU: MSI Suprim GeForce RTX 4090 24GB GDDR6X PCI Express 4.0 (Overclocked)

I tried all Audio output options available, including HDMI and a cheap USB dongle

Console output:

S_Init: Setting up sound.
Sound init failed. Using nosound.

Computer 2: Lenovo Thinkpad T520 CPU: Core i7 2.9GHz Ivy Bridge (Quad Core) GPU: Quadro 4200M Audio: Some Realtek DAC, not sure

I did not test the external DP++ modes.

Console output:

S_Init: Setting up sound.
Sound init failed. Using nosound.

Steps to reproduce the behaviour.

  1. run .\auto-setup-windows.cmd
  2. copy gzdoom and zmusic files to a new folder
  3. run gzdoom

Your configuration

Fresh config.

Provide a Log

No error log generated.

RicardoLuis0 commented 1 week ago

IIRC auto-setup-windows.cmd shouldn't be used, since vcpkg is not required for builds anymore, you can just run cmake-gui directly

madame-rachelle commented 1 week ago

Regardless of how it's built, try the .dll's from a recent release, instead of the .dll's it builds, they probably will work a lot better in any case.