Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cl_autowepswitch not working in Half-Life 1 #2749

Closed
TheStormN opened this issue Oct 27, 2019 · 16 comments
Closed

cl_autowepswitch not working in Half-Life 1 #2749

TheStormN opened this issue Oct 27, 2019 · 16 comments
Assignees

Comments

@TheStormN
Copy link

The Half-Life 1 update from 08.10.2019 added the long awaited client command "cl_autowepswitch" which for example CS had for... lets say forever. Anyway it is buggy, randomly stops working, especially after you are killed and respawn. The new update from this Friday does not fix it... Could you please fix it?

@mikela-valve mikela-valve self-assigned this Oct 28, 2019
@mikela-valve mikela-valve added this to the Next Release milestone Oct 28, 2019
@afwn90cj93201nixr2e1re
Copy link

@mikela-valve can you also fix something?
Add check is there IN_Attack flag - then skip switching, that's really anoying when i walking with knife and c4 dropped out at ground.

@TheStormN
Copy link
Author

@mikela-valve Anything new on this? I can confirm that after a respawn the command does not have any effect.

@mikela-valve
Copy link
Member

Hi @TheStormN, this should be fixed in the current beta version 8308.

@afwn90cj93201nixr2e1re
Copy link

afwn90cj93201nixr2e1re commented Aug 3, 2020

Did you add in_attack condition?
Coz it's really sometimes became useless to picking up some weapons when you shooting due weapon changes coz some weapons more powerfull than others.

I mean maybe you could add new cvar and add one more checkbox inside settings?

@TheStormN
Copy link
Author

TheStormN commented Aug 3, 2020

@mikela-valve Thank you, it is fixed!

Just a note - I would prefer to be spawn holding the pistol, instead of the crowbar. :)

@mikela-valve
Copy link
Member

@TheStormN That's a good point, I noticed that just now as well when I was checking something. I'll change the spawn behaviour specifically to ignore cl_autowepswitch for the initial weapon loadout.

@afwn90cj93201nixr2e1re That sounds fine to me, I'll add another cvar cl_autowepswitchinattack to toggle that.

@afwn90cj93201nixr2e1re
Copy link

afwn90cj93201nixr2e1re commented Aug 3, 2020

You know what?? Possible it's gonna be better if you keep use same cvar, but extend values, 1.0 - always, 2.0 - if not in attack something like that.

@mikela-valve
Copy link
Member

I thought about that but didn't want to make that cvar confusing. 2 is actually already in use in DMC to mean auto-swap if the weapon is better (DMC also has 1 to signify always auto-swap).

@afwn90cj93201nixr2e1re
Copy link

Oh, ok, that's your choice. Also acceptable. Thanks.

@mikela-valve
Copy link
Member

Actually, cl_autowepswitch is part of userinfo and anything else setting up player state also needs to be, so it's probably better to go with extending cl_autowepswitch. Since DMC has its own special logic already I'm not planning to change it so everything else will just treat 2 as switch if not attacking.

@afwn90cj93201nixr2e1re
Copy link

afwn90cj93201nixr2e1re commented Aug 3, 2020

x D, i forgot about that.

@mikela-valve
Copy link
Member

The beta branch is updated for HL1/HLDS and CS for the above changes.

@TheStormN
Copy link
Author

@mikela-valve Once again, it does not work after respawn...

@mikela-valve
Copy link
Member

@TheStormN Could you try uninstalling/reinstalling and double-checking that? I just ran through a few tests locally in HL1 with cl_autowepswitch 0 and 1 and each time it was still respected after respawn. Just to be sure I switched back to the crowbar for each test to ensure other weapons would have higher weight and each time it either switched or didn't switch as appropriate.

@TheStormN
Copy link
Author

@mikela-valve Ok, I've used verify integrity of game files and now it is working as expected. Sorry for the false positive and thank you for the good work! :)

@mikela-valve
Copy link
Member

Thanks @TheStormN! Closing as fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants