Warsow 0.7 BETA release!

any1 allready mentioned that stun is enabled in CA?

during the week of testing .7 I have logined to mm.warsow.net only once =( Mainly it says to me "MM Login: authentication timeout". What I have to do?

it's possible to spawnfrag your teammates when spawning as defense on wbomb6

i'd love the ramps @ attacker spawn to be widened too. currently they're a blockers paradise:[

I have a small problem with sensitivity now, I can't set +-0.0x values. I used to have sensitivity 3.18, but now when I try to set it, it goes automatically to 3.20000.
Btw I tried plasma climbing at a crooked wall but it didn't work :D Isn't it supposed to work with these octagon hitboxes?

Huksi` wrote:
I have a small problem with sensitivity now, I can't set +-0.0x values. I used to have sensitivity 3.18, but now when I try to set it, it goes automatically to 3.20000.

that's most likely because you're using UI to adjust some settings?

Btw I tried plasma climbing at a crooked wall but it didn't work :D Isn't it supposed to work with these octagon hitboxes?

octagon hitboxes have nothing to do with plasma climbing or other types of splash damage
(updated 2012-06-06 21:13:29)

o be more specific. I'm talking about info_player_start -> target_give -> some_weapon, where -> is a link, and info_player_start could also be a trigger_multiple.
Also here's a demo of the issue with give triggers. Here's an example
Expected behavior (This is from 0.4, but it works in 0.5,0.6)

doesn't work for me in 0.6 either

the prob was that since 0.5 target_give needed 'spawnflags' to have the first bit set to work in non-playtime match states. reverted this to 0.4 behavior. works now.
(updated 2012-06-06 23:12:11)

- plz add 1600x900 resolution as pre-setted to the video settings :) plz,plz,plz!

done

Any reply for this?:

Noobsow wrote:
After some tests, I think it is only the wsw_server_x86.exe that is bugged. wsw_server_x64.exe works fine.
Also, X86 creates "tempmodules" inside the basewsw of the folder where it is.
X64 (as do 0.6) creates at AppData\Roaming\Warsow 0.7\basewsw

I also noted that X86/X64 are eating up 100% of one cpu core for a second or two during initialization.
I got this from the stack of X64:

wsw_server_x64.exe!curl_getdate+0x374f9
[...]

As a side note, OS is Win 7 x64.

Noobsow wrote:
* On another area, I see Warsow has a predefined resolution of 1366x768, but some (or many?) monitors uses 1360x768 (mine is one of those)...

adem wrote:
- plz add 1600x900 resolution as pre-setted to the video settings :) plz,plz,plz!

plz replace 1366x768 with 1360x768 resolution as pre-setted to the video settings :) plz,plz,plz!
plox,plox,plox!
(updated 2012-06-07 04:10:22)

I apologize if this was noted elsewhere; I skipped through the thread searching for color and don't think I found it mentioned by anyone else.

I seem to have run into a bug where, on wda2, the gas in the background behind the glass is the same color as the forced enemy models.

This is illustrated in the following two screenshots:







I can't see why this would be intentional by the developers, but I could be overlooking something simple. This is a relatively minor issue, but in case it is a bug I figured it would best be brought to the attention of our beloved Warsow overlords.

Vic wrote:

- plz add 1600x900 resolution as pre-setted to the video settings :) plz,plz,plz!

done

yay, thank you, Vic!

dafaq wamph1





also i noticed smtn strange

i spect some matches and with maxfps 0 i had between 130 and 160 fps
then i caped them at 200 and i had no drops anymore (stable 199 as it says)
also when i tried 250 (still stable 249 in any situation)
only when i got up to 333 and 500 it droped back to 130 till 160

so cl_maxfps has some secret super boost hax in it

Noobsow wrote:
After some tests, I think it is only the wsw_server_x86.exe that is bugged. wsw_server_x64.exe works fine.
Also, X86 creates "tempmodules" inside the basewsw of the folder where it is.
X64 (as do 0.6) creates at AppData\Roaming\Warsow 0.7\basewsw

I also noted that X86/X64 are eating up 100% of one cpu core for a second or two during initialization.
I got this from the stack of X64:

wsw_server_x64.exe!curl_getdate+0x374f9
[...]

tempmodules is created in writable directory, wherever it might be. it could in your profile dir, or the installation directory itself in case of the portable launcher. however it does NOT depend on the binary platform. you probably used wsw_portable_x86.exe to launch the x86 bin.

and ye, curl can sometimes be evil, although we're not using blocking queries during initialization.

I seem to have run into a bug where, on wda2, the gas in the background behind the glass is the same color as the forced enemy models.

bizarre, I will look into this

Vic wrote:

I seem to have run into a bug where, on wda2, the gas in the background behind the glass is the same color as the forced enemy models.

bizarre, I will look into this

Much appreciated.

Vic wrote:

o be more specific. I'm talking about info_player_start -> target_give -> some_weapon, where -> is a link, and info_player_start could also be a trigger_multiple.
Also here's a demo of the issue with give triggers. Here's an example
Expected behavior (This is from 0.4, but it works in 0.5,0.6)

doesn't work for me in 0.6 either

the prob was that since 0.5 target_give needed 'spawnflags' to have the first bit set to work in non-playtime match states. reverted this to 0.4 behavior. works now.

Thanks! I didnt even think about match states for race.

BBQsauce wrote:
Warsow should switch to ncurses interface. It is fast, reliable, and supports color.

And I'm only half-trolling there. I'd personally love that, and the librocket performance seem terrible.

You sir are a genius. I'll see what I can do.

0.6 mapload so anoying!

Vic wrote:

Huksi` wrote:
I have a small problem with sensitivity now, I can't set +-0.0x values. I used to have sensitivity 3.18, but now when I try to set it, it goes automatically to 3.20000.

that's most likely because you're using UI to adjust some settings?

Btw I tried plasma climbing at a crooked wall but it didn't work :D Isn't it supposed to work with these octagon hitboxes?

octagon hitboxes have nothing to do with plasma climbing or other types of splash damage

No, I tried to set it via console but it sets it to 3.2 always.

And I'll try to explain the plasma climb: Plasma climbing works on walls that are to the direction or x- or y-axis, but not on crooked walls.

Before this version plasma climb didn't work on walls that were "crooked" (in a 45 degree angle with the x- or y-axis) because only the corners of the hitbox hit the wall. But now that it's octagon, one would think it works? But it still doesn't work. Well this is not a big problem anyway, just saying.

Mef!sto wrote:
dafaq wamph1





also i noticed smtn strange

i spect some matches and with maxfps 0 i had between 130 and 160 fps
then i caped them at 200 and i had no drops anymore (stable 199 as it says)
also when i tried 250 (still stable 249 in any situation)
only when i got up to 333 and 500 it droped back to 130 till 160

so cl_maxfps has some secret super boost hax in it

That's been there forever lol.

they changed to hole map, so why dont they fix it by then
even if it would be an easteregg i wonder wheres the egg?

Huksi` wrote:

Vic wrote:

Huksi` wrote:
I have a small problem with sensitivity now, I can't set +-0.0x values. I used to have sensitivity 3.18, but now when I try to set it, it goes automatically to 3.20000.

that's most likely because you're using UI to adjust some settings?

Btw I tried plasma climbing at a crooked wall but it didn't work :D Isn't it supposed to work with these octagon hitboxes?

octagon hitboxes have nothing to do with plasma climbing or other types of splash damage

No, I tried to set it via console but it sets it to 3.2 always.

And I'll try to explain the plasma climb: Plasma climbing works on walls that are to the direction or x- or y-axis, but not on crooked walls.

Before this version plasma climb didn't work on walls that were "crooked" (in a 45 degree angle with the x- or y-axis) because only the corners of the hitbox hit the wall. But now that it's octagon, one would think it works? But it still doesn't work. Well this is not a big problem anyway, just saying.

octagonal hitboxes are only for weapons, movement hitboxes are still square so you can't get tight up against the wall