[smoothshot]

Hi people,

I dont' know what it's happening... but I notice a strange behaviour when engage a fight with an opponent... for example, I'm with the primary arm (ie. Psg, AK whatever else..) the fight start and if we go to be close,, suddenly my weapon change to knife :-\ ...but, not for my choice... simply auto switch... Other example I'm with my primary weapon behind a corner... an opponent come out suddenly close to me and my weapon autoswith to knife... I don't know wtf it's happening, but it's really annoying...

I dont' think to have a particular config... I use an autoexec.cfg with some bind as :

// WEAPON BIND
bind g "ut_weaptoggle Knife"
bind f "ut_weaptoggle grenade"
bind AUX1 "ut_weaptoggle primary sidearm"


thx in advance

[iynque]

The only thing that comes to mind would be MWHEELUP and/or MWHEELDOWN is bound to weapnext and/or weapprev

I used to randomly switch weapons until I realized the game was set to change them on "mouse wheel" and my touch-scrolling mouse was frequently sending tiny scroll commands to UrT.

…but since you always seem to land on knife, if might be useful to search all of your configs for weapon 1 and then for ut_weaptoggle knife. Both of those should switch directly to the knife, so check to see if there's anything odd that might be triggering it.

[smoothshot]

iynque, on 11 December 2013 - 09:37 PM, said:

The only thing that comes to mind would be MWHEELUP and/or MWHEELDOWN is bound to weapnext and/or weapprev

I used to randomly switch weapons until I realized the game was set to change them on "mouse wheel" and my touch-scrolling mouse was frequently sending tiny scroll commands to UrT.

…but since you always seem to land on knife, if might be useful to search all of your configs for weapon 1 and then for ut_weaptoggle knife. Both of those should switch directly to the knife, so check to see if there's anything odd that might be triggering it.

thx for ur advices...

btw... the MWHEELUP and MWHEELDOWN are set for the zoom... nevertheless in autoexec.cfg I have a bind for knife on key 'g'

bind g "ut_weaptoggle Knife"

now, I'll try to disable it and test it...

thx

[smoothshot]

iynque, on 11 December 2013 - 09:37 PM, said:

The only thing that comes to mind would be MWHEELUP and/or MWHEELDOWN is bound to weapnext and/or weapprev

I used to randomly switch weapons until I realized the game was set to change them on "mouse wheel" and my touch-scrolling mouse was frequently sending tiny scroll commands to UrT.

…but since you always seem to land on knife, if might be useful to search all of your configs for weapon 1 and then for ut_weaptoggle knife. Both of those should switch directly to the knife, so check to see if there's anything odd that might be triggering it.

Hi,

just for update this post... as wrote above, I tried to comment that bind, but unexpectedly that bind still work ?! :O

looking more in deep, I looked into q3config.cfg and I found that bind still alive there... ?!? and also another same bind to other key 'x' ... :|

..but isn't the q3config.cfg always rewrite ?!? btw I del every bind on knife, I let it only on '1' ... and know I'll test if happen such beaviour...

[rastablaster]

just for update this post... as wrote above, I tried to comment that bind, but unexpectedly that bind still work ?! :O

it may be that your cfg.file is marked as "read only"

[smoothshot]

rastablaster, on 13 December 2013 - 11:00 AM, said:

just for update this post... as wrote above, I tried to comment that bind, but unexpectedly that bind still work ?! :O

it may be that your cfg.file is marked as "read only"

it no seems, it is 600 (rw - - ) ?! now I changed it to 666 ...I'll see...

[Mod [dswp]JRandomNoob]

When you start the game q3onfig.cfg is loaded first and autoexec.cfg second. If any of the entries differ the one in autoexec.cfg takes precedence. Note the wording: “entries differ”. If you delete or comment out a bind in your autoexec.cfg it will still be loaded from the q3config.cfg because there’s nothing in the autoexec.cfg to overwrite it; if a bind is loaded on startup it will of course be written back on shutdown. If you want to ensure that a key is definitely unbound by your autoexec.cfg you should bind it to empty value (bind x ""). It’s a good idea to go through your q3config.cfg every now and then and delete old garbage that inevitably accumulates if you try out new things.

[smoothshot]

JRandomNoob, on 13 December 2013 - 02:08 PM, said:

When you start the game q3onfig.cfg is loaded first and autoexec.cfg second. If any of the entries differ the one in autoexec.cfg takes precedence. Note the wording: “entries differ”. If you delete or comment out a bind in your autoexec.cfg it will still be loaded from the q3config.cfg because there’s nothing in the autoexec.cfg to overwrite it; if a bind is loaded on startup it will of course be written back on shutdown. If you want to ensure that a key is definitely unbound by your autoexec.cfg you should bind it to empty value (bind x ""). It’s a good idea to go through your q3config.cfg every now and then and delete old garbage that inevitably accumulates if you try out new things.

completely agree with you... thx to point out this...