Warsow 0.7 BETA2 Release!

Ly0niki wrote:

Im saying i think Warsow needs more oficial models. And thanks for the links, but i dont have any skills to create things like that.

=/

you can learn such skills :P

did any1 mentioned that wsw needs moar modelz?

well then...

Today we play TDM and i notes the QUAD doesnt make sound when spawns.

I <3 Warsow

adem wrote:
I <3 Warsow

Maybe i'm missing something but the download seems to have no actual UI? I'm seeing an XML error in the console and can load maps via the console but menu just shows a single news post.

Also the website has a XSS error when hitting the reply button, have to go to warsow.net.picmip.org to actually reply.

Actually seems to be that my res on first load was not set right even in window mode, once I changed that I could see the menu at the top :)

Can we get 2560x1440 added to res options :D

Hi!

I found some bugs in this beta.

The ammomod disables my mouse in game (I can't left or right click, nor move the cursor). It still works if I change workspace. The binds are OK. I tried to unbind and bind it, but it doesn't work. I tried with 0.6 configuration, and it still doesn't work. Commands like +attack still works.

Here is what I get in the terminal : http://pastebin.com/1pjqgYVg

When I join a server with ammomod, It sometimes crashes (Segmentation fault) : http://pastebin.com/0180t1xk

I found nothing special in these logs, but I thought it could help you. Is there a way to have more verbose logs?

I also found bugs with the tdo gametype (With a local game). When I start a game, it always sets the score limit to 5 and the timelimit to 0. I have to set it back in the console in game to change it. (It's the same thing with ca and tdm, with other values, and maybe other gametypes too)

Tdo doesn't work on some maps (wdm4 and wdm9). The areas are displayed, but we can't capture them.

I'm using Archlinux (x86_64).

Anyway, thank you for this nice version :o) .

Dagrut wrote:
The ammomod disables my mouse in game (I can't left or right click, nor move the cursor). It still works if I change workspace.
...
When I join a server with ammomod, It sometimes crashes (Segmentation fault)
...
I'm using Archlinux (x86_64).

dang! which workspaces, the desktop environment ones?
are crashes unrelated to the gametype? x64 angle script was known to crash in 0.62, right?

i wonder how debuging is handled in developement. since wsw is built with gcc/mingw, i would expect gdb as debugger, but i dont quite see vic using that.

VectorVanDoom wrote:
dang! which workspaces, the desktop environment ones?
are crashes unrelated to the gametype? x64 angle script was known to crash in 0.62, right?

i wonder how debuging is handled in developement. since wsw is built with gcc/mingw, i would expect gdb as debugger, but i dont quite see vic using that.

Yes, the desktop environment ones (with Xfce).

This crash is hard to reproduce. I only saw it twice, with the duel gametype. I tried two hours to do it again, and it finally just happened, with ca.

The mouse bug always happens. I just have to load ammomod.

It would be nice if it was built with the -g flag, so I could run it with gdb and see what gives the segmentation fault.

it doesn't freeze your mouse, it is simply busy downloading the ammomod stuff, the download indicators are just missing in this beta.

and no, we won't ship our binaries compiled -g, who needs that kind of bloat except for a few nerds who can compile their own binaries from sdk anyway?

and no, I'm not using mingw/gcc/gdb since it's a pile of poop, we're just using it for cross-compilation. msvc ftw

Vic wrote:
it doesn't freeze your mouse, it is simply busy downloading the ammomod stuff, the download indicators are just missing in this beta.

It is not downloading (the network is not used). The mouse is stuck in the top left corner, and I have no way to move or use it (in game, or in any menu).

btw, I've been played with m_raw 0 and yesterday I was not able to use mouse with my config (mouse moving didn't affect on anything in game but mouse worked in menu). I've fixed dat with m_raw 1 :)

I don't really know what happened because I didn't update anything for last 2 weeks excepting nvidia driver (now it's 302.17).

Got a Problem with starting 0.7, all my terminal shows is this:

$ ./warsow
********************
ERROR: Received signal 4

********************
Error: Received signal 4

Compiling from SDK didnt change anything.
Would love to know what this Error means.

Running Xubuntu 12.04 with 1.10.4 XServer on
AMD Athlon XP 3000+
768MB Ram
Geforce FX 5700
(i know its crap, my gaming rig just broke <.<)

0.62 is running all fine.
(updated 2012-06-25 02:42:19)

did you read the thread? maybe its the startup resolution problem, whats your desktop resolution? try to run warsow with "+set vid_fullscreen 0" and/or to change your resolution. open ~/.warsow/basewsw/config.cfg and change or add these parameters:

vid_mode -1
vid_customheight <y resolution>
vid_customwidth <x resolution>

(updated 2012-06-25 04:26:19)

Statistics could show not only the accuracy of each weapon, but how many shots and kills you did.

Reply to topic

I'm having issues with BETA2. After joining some games, mouse input will no longer be recognized by warsow. I've tried using "in_restart" and the cursor will be visible, but it is not used within warsow.

Any ideas?

dieteK wrote:

Reply to topic

I'm having issues with BETA2. After joining some games, mouse input will no longer be recognized by warsow. I've tried using "in_restart" and the cursor will be visible, but it is not used within warsow.

Any ideas?

It looks like this issue only occurs on servers with the strong ammo mod. I've been able to join xannode, sunn.xannode without this issue but as soon as I join warsow-esport I'm unable to use my mouse.

I've also noticed that when joining ammo-mod enabled servers, there is a period of time where my desktop is visible during the map load. This period of time where I can see my desktop does not occur when joining vanilla servers -- the warsow loading screen is shown immediately without any intermission.

Hope this helps! If there is any other debugging info I can provide let me know ITT or pm me

dieteK wrote:

Reply to topic

I'm having issues with BETA2. After joining some games, mouse input will no longer be recognized by warsow. I've tried using "in_restart" and the cursor will be visible, but it is not used within warsow.

Any ideas?

I had the same issue. Check what value set for m_raw. For me that was 1. Setting m_raw 0 and restarting the client solved that problem for me.

i know i read somewhere a post by deli about setting for instance /sensitivity 0.87 automaticly turns into 0.9.
dno if this is a bug or w/e but i have it too :E sucks. peaceoutmahniggaz