Bug #280
Default setinfo wswfix 1 always
| Status: | Closed | Start: | 11/08/2009 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assigned to: | - | % Done: | 100% |
|
| Category: | Core | Spent time: | 1.00 hour | |
| Target version: | 1.36 |
Description
using /setinfo wswfix 1 is stupid, people don't even know this, so better default it always when on KTX server, it's a damn stupid bug anyway.
History
Updated by qqshka 12 months ago
unfortunatelly I can't do it default, ezq have bug which make it unusable, can't recall but I think bug caused by cl_weaponpreselect 1, NG/SNG/LG starts fire with low (choppy) rate, however I can't reproduce it now.
Updated by JohnNy_cz 12 months ago
Hm, that's news to me, cant reproduce either.
The only problem with cl_weaponpreselect 1 i know about is that it makes wswfix 1 not working at all. Partially "feature not bug" but could be changed easily so that work together as 'expected'. But the bug you talk about .. no idea.
Updated by Renzo 12 months ago
Tonik said it can and should be done, but I haven't seen him doing anything for the issue.
Also, why KTX can't have a feature that works with normal impulse scripts just because some ezQuake's feature does not work as it's supposed to? Make KTX work like it should and solve the problem with the client.
Updated by JohnNy_cz 12 months ago
My previous comment is incomplete - cl_weaponpreselect 2 resolves the problem I talk about.
So for me: wswfix 1 + cl_weaponpreselect 2 works perfect.
Updated by qqshka 12 months ago
Renzo wrote:
Tonik said it can and should be done, but I haven't seen him doing anything for the issue.
Also, why KTX can't have a feature that works with normal impulse scripts just because some ezQuake's feature does not work as it's supposed to? Make KTX work like it should and solve the problem with the client.
I did it for KTX, dunno about client... lets see. :E