So i changed my hud yesterday, and now every time I boot up my game my movement keys are unbound and when I rebind them, my null movement script does not work. Does anyone know what could be going on here?
bind them in your config.cfg and they will save. i had the same problem a while back
Check if you have -autoconfig in your lauch options.
You might want to check if they are binded correctly in your autoexec as well.
You might want to check if they are binded correctly in your autoexec as well.
HypnotizeCheck if you have -autoconfig in your lauch options.
You might want to check if they are binded correctly in your autoexec as well.
My null movement script is in the end of my autoexec, but I did notice something, when I went to save my autoexec it was saving as a text document, but it still shows it is a cfg, could that be what is causing my problem?
Also I do not have -autoconfig in my launch options, should I?
You might want to check if they are binded correctly in your autoexec as well.[/quote]
My null movement script is in the end of my autoexec, but I did notice something, when I went to save my autoexec it was saving as a text document, but it still shows it is a cfg, could that be what is causing my problem?
Also I do not have -autoconfig in my launch options, should I?
aliases don't save between sessions. null movement is all aliases.
Restart TF2, try walking around on a server, look at console. if it shows a bunch of "unknown command" errors this means whatever cfg file has the null movement script in it isn't getting exec'd
Restart TF2, try walking around on a server, look at console. if it shows a bunch of "unknown command" errors this means whatever cfg file has the null movement script in it isn't getting exec'd
BazingaBarry82HypnotizeCheck if you have -autoconfig in your lauch options.My null movement script is in the end of my autoexec, but I did notice something, when I went to save my autoexec it was saving as a text document, but it still shows it is a cfg, could that be what is causing my problem?
You might want to check if they are binded correctly in your autoexec as well.
Also I do not have -autoconfig in my launch options, should I?
yes make sure it's a .cfg file
You might want to check if they are binded correctly in your autoexec as well.[/quote]
My null movement script is in the end of my autoexec, but I did notice something, when I went to save my autoexec it was saving as a text document, but it still shows it is a cfg, could that be what is causing my problem?
Also I do not have -autoconfig in my launch options, should I?[/quote]
yes make sure it's a .cfg file
TobBazingaBarry82HypnotizeCheck if you have -autoconfig in your lauch options.My null movement script is in the end of my autoexec, but I did notice something, when I went to save my autoexec it was saving as a text document, but it still shows it is a cfg, could that be what is causing my problem?
You might want to check if they are binded correctly in your autoexec as well.
Also I do not have -autoconfig in my launch options, should I?
yes make sure it's a .cfg file
I did, still not working and I did check my console, there were no errors
Edit: Actually in addition, every time I save my autoexec as all files it says one exists and to overwrite it, but when I go back and attempt to save it again, it's listed as a txt file
You might want to check if they are binded correctly in your autoexec as well.[/quote]
My null movement script is in the end of my autoexec, but I did notice something, when I went to save my autoexec it was saving as a text document, but it still shows it is a cfg, could that be what is causing my problem?
Also I do not have -autoconfig in my launch options, should I?[/quote]
yes make sure it's a .cfg file[/quote]
I did, still not working and I did check my console, there were no errors
Edit: Actually in addition, every time I save my autoexec as all files it says one exists and to overwrite it, but when I go back and attempt to save it again, it's listed as a txt file
BazingaBarry82
Edit: Actually in addition, every time I save my autoexec as all files it says one exists and to overwrite it, but when I go back and attempt to save it again, it's listed as a txt file
Are you saving it as autoexec.cfg or just clicking all files and leaving it as autoexec?
Edit: Actually in addition, every time I save my autoexec as all files it says one exists and to overwrite it, but when I go back and attempt to save it again, it's listed as a txt file[/quote]
Are you saving it as autoexec.cfg or just clicking all files and leaving it as autoexec?
Save the script in your autoexec and make your config.cfg read-only.
smittenBazingaBarry82
Edit: Actually in addition, every time I save my autoexec as all files it says one exists and to overwrite it, but when I go back and attempt to save it again, it's listed as a txt file
Are you saving it as autoexec.cfg or just clicking all files and leaving it as autoexec?
I am saving as autoexec.cfg, but I did some further testing and the autoexec is indeed execing, it's just the null movement script isn't working and it's unbinding my keys
Edit: Actually in addition, every time I save my autoexec as all files it says one exists and to overwrite it, but when I go back and attempt to save it again, it's listed as a txt file[/quote]
Are you saving it as autoexec.cfg or just clicking all files and leaving it as autoexec?[/quote]
I am saving as autoexec.cfg, but I did some further testing and the autoexec is indeed execing, it's just the null movement script isn't working and it's unbinding my keys
BazingaBarry82Edit: Actually in addition, every time I save my autoexec as all files it says one exists and to overwrite it, but when I go back and attempt to save it again, it's listed as a txt file
If you're on windows, when using save as to save your autoexec, make sure the dropdown below the filename is "all files" and not "TXT document".
If you're on windows, when using save as to save your autoexec, make sure the dropdown below the filename is "all files" and not "TXT document".
BazingaBarry82I am saving as autoexec.cfg, but I did some further testing and the autoexec is indeed execing, it's just the null movement script isn't working and it's unbinding my keys
So you can confirm 100% autoexec is executing? (You can put a statement in your auto exec like "echo AUTOEXEC RUNNING" and see this output in console after startup.
If so, can you post the contents of your autoexec in a pastebin link?
If applicable, post any other configs that get run, such as a class config, or reset config if you've configured things this way.
I am saving as autoexec.cfg, but I did some further testing and the autoexec is indeed execing, it's just the null movement script isn't working and it's unbinding my keys[/quote]
So you can confirm 100% autoexec is executing? (You can put a statement in your auto exec like "echo AUTOEXEC RUNNING" and see this output in console after startup.
If so, can you post the contents of your autoexec in a pastebin link?
If applicable, post any other configs that get run, such as a class config, or reset config if you've configured things this way.
KairuBazingaBarry82I am saving as autoexec.cfg, but I did some further testing and the autoexec is indeed execing, it's just the null movement script isn't working and it's unbinding my keys
So you can confirm 100% autoexec is executing? (You can put a statement in your auto exec like "echo AUTOEXEC RUNNING" and see this output in console after startup.
If so, can you post the contents of your autoexec in a pastebin link?
If applicable, post any other configs that get run, such as a class config, or reset config if you've configured things this way.
Yeah, I'm running cowmanglia's so I'm getting the confirmation.
It's specifically the null movement script that's causing the issue
bind w +mfwd
bind s +mback
bind a +mleft
bind d +mright
alias +mfwd "-back;+forward;alias checkfwd +forward"
alias +mback "-forward;+back;alias checkback +back"
alias +mleft "-moveright;+moveleft;alias checkleft +moveleft"
alias +mright "-moveleft;+moveright;alias checkright +moveright"
alias -mfwd "-forward;checkback;alias checkfwd none"
alias -mback "-back;checkfwd;alias checkback none"
alias -mleft "-moveleft;checkright;alias checkleft none"
alias -mright "-moveright;checkleft;alias checkright none"
alias checkfwd none
alias checkback none
alias checkleft none
alias checkright none
alias none ""
this is the one I'm using, I don't know if it's outdated and that could be the problem
EDIT: I was able to find another null movement script and this one is working for some reason, I'm good to go now.
I am saving as autoexec.cfg, but I did some further testing and the autoexec is indeed execing, it's just the null movement script isn't working and it's unbinding my keys[/quote]
So you can confirm 100% autoexec is executing? (You can put a statement in your auto exec like "echo AUTOEXEC RUNNING" and see this output in console after startup.
If so, can you post the contents of your autoexec in a pastebin link?
If applicable, post any other configs that get run, such as a class config, or reset config if you've configured things this way.[/quote]
Yeah, I'm running cowmanglia's so I'm getting the confirmation.
It's specifically the null movement script that's causing the issue
bind w +mfwd
bind s +mback
bind a +mleft
bind d +mright
alias +mfwd "-back;+forward;alias checkfwd +forward"
alias +mback "-forward;+back;alias checkback +back"
alias +mleft "-moveright;+moveleft;alias checkleft +moveleft"
alias +mright "-moveleft;+moveright;alias checkright +moveright"
alias -mfwd "-forward;checkback;alias checkfwd none"
alias -mback "-back;checkfwd;alias checkback none"
alias -mleft "-moveleft;checkright;alias checkleft none"
alias -mright "-moveright;checkleft;alias checkright none"
alias checkfwd none
alias checkback none
alias checkleft none
alias checkright none
alias none ""
this is the one I'm using, I don't know if it's outdated and that could be the problem
EDIT: I was able to find another null movement script and this one is working for some reason, I'm good to go now.