Quake3e requires jack (audioserver) running? Is that intentional? about quake3e HOT 8 CLOSED

Team arena is the missionpack folder so not baseq3 folder. Maybe residual setting when changing mods.

Launch with +set fs_game missionpack +set s_device pulse after the binary name

from quake3e.

Engine tries to open "default" ALSA device, there is no such hardcoded jack dependencies, so this looks like as your local configuration issue.

You may try to set USE_SDL = 1 in Makefile and recompile engine

from quake3e.

i forgot to mention that the binary i used was the one latest github release (20191119). When i run the ./ioquake in the same folder, same configs, some mods etc... everything works fine. i don't understand it... yet :) thanks for the info, i'll report back when i make progress.

from quake3e.

when i compile the latest source code without any modifications, quake3e needs jack to be running in order to work. Probably influenced by some local circumstances, but my system is in no way special, it's a pretty standard manjaro linux i'd say.

from quake3e.

Even when i set USE_SDL = 1 in the makefile, the result is the same: jack server needs to be running.

from quake3e.

Comparison to ioquake3 not valid entirely. ioquake3 uses OpenAL by default. But no matter what backend code in q3e seems to still choose that specific alsa device.

When NOT in USE_SDL=1 mode, s_device defaults to "default" but you can also put "sysdefault" or "front" or try using aplay -L in your shell to get a list of available.

from quake3e.

SDL may still want to open the same default ALSA device, I see no engine-specific dependencies there

from quake3e.

seta s_device "pulse" in baseq3/q3config.cfg did the job. default and sysdefault needed jack running.

Odd thing is that when i click on "Team Arena" in the main menu, it still requires jack running, no matter what s_device is set to in baseq3/q3config.cfg or missionpack/q3config.cfg.

Thanks for the help!

from quake3e.