Warsow 0.7 BETA2 Release!

Heartlesss wrote:

SkulP wrote:
Just found this weird bug: after executing my cfg I noticed the custom values for m_side and m_forward weren't there(0.25 for both). Anyways this was fixed manually by editing the .cfg doc. Still maybe this should be fixed? ;)

m_side and m_forward are 2 useless cvars, unless you are strafing with your mouse :D Just like in doom or quake 1 back in the day :>

oh lol weird, I always feel like my QL sens is different from my WsW. With different(same as QL) m_side and forward they felt closer to each other. Placebo then. :P
(updated 2012-07-03 15:38:46)

acidwdm2 and wdm1 dont feel the same without strong ammo :/ *whine*
(updated 2012-07-07 00:56:33)

and add a "add to friends" ingame option. A command like "addtofriendlist nickname" would be good enough.

For some reason i am still unable to play. I am able to launch menu and join a game, but then mouse stop working for some reason. Keys seem to work correctly in chat however. I have missing textures on some weapons. The game also launches in window mode, and when joining a game i sometimes get a signal 11 crashing the game.

I suspect the problem to be X-server related. I am able to play openarena and previous warsow version flawlessly, however. Fresh ubuntu 12.07, nvidia GeForce 8400M GS, driver v295.49, gnome desktop
(updated 2012-07-07 17:02:14)

kinda IMPORTANT:

there's no way to change mod (via menu, to actually switch over to ammomod demos for example)
(updated 2012-07-11 21:56:28)

a combobox to select a mod before starting local games would be appreciated

Found a really strange bug. Sounds that should be heard everywhere because they have attenuation set to ATTN_NONE can't be heard or aren't played at all.

K1ll wrote:
Found a really strange bug. Sounds that should be heard everywhere because they have attenuation set to ATTN_NONE can't be heard or aren't played at all.

steps to reproduce?

Create a little testmap with a button that is connected to a target_speaker and triggers it. The target_speaker must have spawnflags set to 8 and noise set to some sound. In Warsow 0.6 the sound plays when you press the button but in warsow 0.7 it doesn't.

Edit: Sorry seems like i was a bit too fast there. The problem seems to be more complicated. I've got the problem on this map. I'll try to find out how to build a testmap that can reproduce the problem.
(updated 2012-07-11 22:06:47)

since ctf3 has a lot of teamcolored walls it's often quite hard to find/trace the enemy model. that's nothing new but maybe sth could be done about this, would be nice

mouse stop working for some reason

I can reproduce this bug by typing fs_game ammomod in console. Basically, the mouse "focus" get lost when warsow launches the mod, and can't be retrived. Signal 11 errors can be reproduced that way too.

Some (unhelpful) log

Initialization of openal succesful
------------------------------------
Loaded font face Bitstream Vera Sans Roman (from fonts/Vera.ttf).
Loaded font face Bitstream Vera Sans Bold (from fonts/VeraBd.ttf).
Loaded font face Bitstream Vera Sans Bold Oblique (from fonts/VeraBI.ttf).
Loaded font face Bitstream Vera Sans Oblique (from fonts/VeraIt.ttf).
Loaded font face Virtue Regular (from fonts/Virtue.ttf).
Loaded font face Hemi Head Bold Italic (from fonts/hemihead-bd-it.otf).
Loaded font face Kimberley Black (from fonts/kimberley-bl.otf).
********************
ERROR: Received signal 11

********************
CIN module unloaded.
Error: Received signal 11

(updated 2012-07-15 21:17:09)

BBQsauce wrote:

mouse stop working for some reason

I can reproduce this bug by typing fs_game ammomod in console. Basically, the mouse "focus" get lost when warsow launches the mod, and can't be retrived. Signal 11 errors can be reproduced that way too.

Some (unhelpful) log

Initialization of openal succesful
------------------------------------
Loaded font face Bitstream Vera Sans Roman (from fonts/Vera.ttf).
Loaded font face Bitstream Vera Sans Bold (from fonts/VeraBd.ttf).
Loaded font face Bitstream Vera Sans Bold Oblique (from fonts/VeraBI.ttf).
Loaded font face Bitstream Vera Sans Oblique (from fonts/VeraIt.ttf).
Loaded font face Virtue Regular (from fonts/Virtue.ttf).
Loaded font face Hemi Head Bold Italic (from fonts/hemihead-bd-it.otf).
Loaded font face Kimberley Black (from fonts/kimberley-bl.otf).
********************
ERROR: Received signal 11

********************
CIN module unloaded.
Error: Received signal 11

i am also unfortunately plagued by this bug as well :/ i've tried using the native binaries for my system that I compiled as well but they are affected by the bug as well

some of my system info:
arch linux 64
xorg 1.12.3
can reproduce on intel graphics and nvidia (all three of my boxen)
i'd be happy to provide any additional information in fixing this bug! i've still yet to try ammomod because of this bug

dieteK wrote:

BBQsauce wrote:

mouse stop working for some reason

I can reproduce this bug by typing fs_game ammomod in console. Basically, the mouse "focus" get lost when warsow launches the mod, and can't be retrived. Signal 11 errors can be reproduced that way too.

Some (unhelpful) log

Initialization of openal succesful
------------------------------------
Loaded font face Bitstream Vera Sans Roman (from fonts/Vera.ttf).
Loaded font face Bitstream Vera Sans Bold (from fonts/VeraBd.ttf).
Loaded font face Bitstream Vera Sans Bold Oblique (from fonts/VeraBI.ttf).
Loaded font face Bitstream Vera Sans Oblique (from fonts/VeraIt.ttf).
Loaded font face Virtue Regular (from fonts/Virtue.ttf).
Loaded font face Hemi Head Bold Italic (from fonts/hemihead-bd-it.otf).
Loaded font face Kimberley Black (from fonts/kimberley-bl.otf).
********************
ERROR: Received signal 11

********************
CIN module unloaded.
Error: Received signal 11

i am also unfortunately plagued by this bug as well :/ i've tried using the native binaries for my system that I compiled as well but they are affected by the bug as well

some of my system info:
arch linux 64
xorg 1.12.3
can reproduce on intel graphics and nvidia (all three of my boxen)
i'd be happy to provide any additional information in fixing this bug! i've still yet to try ammomod because of this bug

Please recompile with debug settings, run make with parameter DEBUG_BUILD=YES then run the new binaries with gdb and once you have a break on error grab the stacktrace by writing backtrace to the gdb console and copy/paste for us to see. We have absolutely no use for error reports that don't give even this information to us, sorry :(

toukkapoukka wrote:

dieteK wrote:

BBQsauce wrote:

mouse stop working for some reason

I can reproduce this bug by typing fs_game ammomod in console. Basically, the mouse "focus" get lost when warsow launches the mod, and can't be retrived. Signal 11 errors can be reproduced that way too.

Some (unhelpful) log

Initialization of openal succesful
------------------------------------
Loaded font face Bitstream Vera Sans Roman (from fonts/Vera.ttf).
Loaded font face Bitstream Vera Sans Bold (from fonts/VeraBd.ttf).
Loaded font face Bitstream Vera Sans Bold Oblique (from fonts/VeraBI.ttf).
Loaded font face Bitstream Vera Sans Oblique (from fonts/VeraIt.ttf).
Loaded font face Virtue Regular (from fonts/Virtue.ttf).
Loaded font face Hemi Head Bold Italic (from fonts/hemihead-bd-it.otf).
Loaded font face Kimberley Black (from fonts/kimberley-bl.otf).
********************
ERROR: Received signal 11

********************
CIN module unloaded.
Error: Received signal 11

i am also unfortunately plagued by this bug as well :/ i've tried using the native binaries for my system that I compiled as well but they are affected by the bug as well

some of my system info:
arch linux 64
xorg 1.12.3
can reproduce on intel graphics and nvidia (all three of my boxen)
i'd be happy to provide any additional information in fixing this bug! i've still yet to try ammomod because of this bug

Please recompile with debug settings, run make with parameter DEBUG_BUILD=YES then run the new binaries with gdb and once you have a break on error grab the stacktrace by writing backtrace to the gdb console and copy/paste for us to see. We have absolutely no use for error reports that don't give even this information to us, sorry :(

like i said i'd be happy to provide any debugging information

i compiled with "make DEBUG_BULID=YES" and i'm getting this when running the new binaries in gdb:


Reading symbols from /home/lukas/warsow_0.7/warsow.x86_64...(no debugging symbols found)...done.

also i'm not reproducing the crash every time but i'm reproducing the loss of mouse focus on every join of an ammomod server -- should i just break after joining a ammomod server and provide a stack trace ?

dieteK wrote:

Reading symbols from /home/lukas/warsow_0.7/warsow.x86_64...(no debugging symbols found)...done.

also i'm not reproducing the crash every time but i'm reproducing the loss of mouse focus on every join of an ammomod server -- should i just break after joining a ammomod server and provide a stack trace ?

Recheck that you are using the correct rebuilt binaries, "no debugging symbols found" indicates that you aren't using the ones built with debug settings. Also did you type "make DEBUG_BULID=YES" incorrectly in the post or in the console?
We have a hunch or the mouse problem and Vic may have already fixed this.

I've got the same bug with a crash also

Gonna do a debug build.

toukkapoukka wrote:

dieteK wrote:

Reading symbols from /home/lukas/warsow_0.7/warsow.x86_64...(no debugging symbols found)...done.

also i'm not reproducing the crash every time but i'm reproducing the loss of mouse focus on every join of an ammomod server -- should i just break after joining a ammomod server and provide a stack trace ?

Recheck that you are using the correct rebuilt binaries, "no debugging symbols found" indicates that you aren't using the ones built with debug settings. Also did you type "make DEBUG_BULID=YES" incorrectly in the post or in the console?
We have a hunch or the mouse problem and Vic may have already fixed this.

I recompiled it again changing "DEBUG_BUILD" to "YES" within the "Makefile" as well, and I'm still getting the same message in gdb -- I'll run a make clean and try it again. I'm really glad to hear that Vic may have already fixed this! it would just really be a shame for this bug to be present in the release alienating players that hit this bug

I cant get it crash again.

Reading symbols from /home/lukas/warsow_0.7/warsow.x86_64...(no debugging symbols found)...done.

works for me on 32 bit Linux Mint 13

wait shouldn’t be the debug stuff in /home/user/warsow_0.7_sdk/source/debug
(updated 2012-07-16 18:01:43)

I got something:

Program received signal SIGSEGV, Segmentation fault.
0x0022a027 in _XRegisterFilterByType ()
   from /usr/lib/i386-linux-gnu/libX11.so.6
(gdb) backtrace
#0  0x0022a027 in _XRegisterFilterByType ()
   from /usr/lib/i386-linux-gnu/libX11.so.6
#1  0x0025a6dd in ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
#2  0x0023ed1a in XSetICFocus () from /usr/lib/i386-linux-gnu/libX11.so.6
#3  0x080a684c in HandleEvents () at unix/unix_input.c:946
#4  0x080a6cf9 in IN_Frame () at unix/unix_input.c:1131
#5  0x0809047b in CL_UserInputFrame () at client/cl_input.c:797
#6  0x080955c6 in CL_Frame (realmsec=10160, gamemsec=10160)
    at client/cl_main.c:2463
#7  0x0805dd0c in Qcommon_Frame (realmsec=10160) at qcommon/common.c:1395
#8  0x080ac877 in main (argc=2, argv=0xbffff954) at unix/unix_sys.c:444
(gdb) 

double check after fs_game ammomod:

Program received signal SIGSEGV, Segmentation fault.
0x0022a0a0 in _XUnregisterFilter () from /usr/lib/i386-linux-gnu/libX11.so.6
(gdb) backtrace
#0  0x0022a0a0 in _XUnregisterFilter ()
   from /usr/lib/i386-linux-gnu/libX11.so.6
#1  0x0025a664 in ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
#2  0x0023ed36 in XUnsetICFocus () from /usr/lib/i386-linux-gnu/libX11.so.6
#3  0x080a687e in HandleEvents () at unix/unix_input.c:955
#4  0x080a6cf9 in IN_Frame () at unix/unix_input.c:1131
#5  0x0809047b in CL_UserInputFrame () at client/cl_input.c:797
#6  0x080955c6 in CL_Frame (realmsec=7903, gamemsec=7903)
    at client/cl_main.c:2463
#7  0x0805dd0c in Qcommon_Frame (realmsec=7903) at qcommon/common.c:1395
#8  0x080ac877 in main (argc=1, argv=0xbffff964) at unix/unix_sys.c:444
(gdb) 

Same, so this is the bug probably
(updated 2012-07-16 18:15:27)

Ah, you are like 1 mn ahead of my own dump.

(gdb) bt
#0  0x00000000 in ?? ()
#1  0xb7e2b029 in _XRegisterFilterByType () from /usr/lib/i386-linux-gnu/libX11.so.6
#2  0xb7e5b6dd in ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
#3  0xb7e3fd1a in XSetICFocus () from /usr/lib/i386-linux-gnu/libX11.so.6
#4  0x080a67ec in HandleEvents () at unix/unix_input.c:946
#5  0x080a6c99 in IN_Frame () at unix/unix_input.c:1131
#6  0x0809041b in CL_UserInputFrame () at client/cl_input.c:797
#7  0x08095566 in CL_Frame (realmsec=4840, gamemsec=4840) at client/cl_main.c:2463
#8  0x0805dcac in Qcommon_Frame (realmsec=4840) at qcommon/common.c:1395
#9  0x080ac817 in main (argc=1, argv=0xbffff2b4) at unix/unix_sys.c:444
(gdb)