Warzone 2100 Forums

Warzone 2100 stopped responding after like 10 seconds of the launch

System specs?
What version of Warzone?
What OS?

vexed wrote:System specs?
What version of Warzone?
What OS?

Warzone 3.2.0 build from source crashes immediately not finding a jack audio server, running Debian Sid. Jack has it's place for serious audiophiles but for studio work the jack user should also be running a dedicated box with a RT kernel. For the average Linux user alsa/pulse is more than enough. So, how to get rid of the jack dependency??

Jack is most likely unrelated. Could you post the crash dump?

wayward4now wrote:Warzone 3.2.0 build from source crashes immediately not finding a jack audio server, running Debian Sid. Jack has it's place for serious audiophiles but for studio work the jack user should also be running a dedicated box with a RT kernel. For the average Linux user alsa/pulse is more than enough. So, how to get rid of the jack dependency??

Warzone uses OpenAL, sounds like yours is configured to use jack by default.

I have an AMD 6 core tower with 16 gigs of ram and 4 gigs of nVidia vram with two video cards. All versions of warzone run slick as butter until the 3.2 series. The last thing I see on the terminal is a failure to load jack, but I hear the audio via alsa/pulseaudio. I get a black screen when I pick full screen. If I rm config in the dot-warzone directory, it starts just fine in default windowed mode. Older versions run spread across four monitors full screen and it is a hoot to play like that!! I'm not seeing a error log. Thanx, Ric

The logs in ~/.warzone2100-3.2/logs contain nothing related to run errors
WZlog-0729_020205.txt
::::::::::::::

--- Starting log [/home/ric/.warzone2100-3.2/logs/WZlog-0729_020205.txt]-

--
info |02:02:05: [realmain:1140] Using /home/ric/.warzone2100-3.2/logs/
WZlog-0729_020205.txt debug file