Has anyone been able to disable View Bob and Auto Aim?
I can’t continue playing the game with View Bob, I get really bad headaches and feel dizzy.
I also can’t disable Auto Aim.
Does anyone know the console commands for this?
Has anyone been able to disable View Bob and Auto Aim?
I can’t continue playing the game with View Bob, I get really bad headaches and feel dizzy.
I also can’t disable Auto Aim.
Does anyone know the console commands for this?
Settings/black mesa
and there you go (every option of game)
auto run
auto aim
viewbob (only weapon bob)
and roll (screen shake) put it to 0% and you have it
Auto aim enables when game starts i dont think the same is with the screen roll
For some reason it won’t remember your settings though, so check it each time you tsrat the game.
yah, a few settings (including view bob and auto aim) revert to the defaults every time you restart Black Mesa. As for the view bob:
that setting reverts on every restart too, so you will just have to reset it before playing.
Please, tell console variables responsible for ‘enable auto-aim’ and ‘enable train fail-safe’, to add its to autoexec.
Auto-aim seems to be broken anyway. Even with the setting on it doesn’t seem to do anything. I’ve had it mysteriously revert without my knowledge, and I didn’t realize because there isn’t any real difference.
Enable Auto-Aim:
sk_allow_autoaim 1
Note: 1 to enable / 0 to disable.
Enable Auto-Aim (Optional):
sk_autoaim_mode 1
Note: 1 to enable / 0 to disable.
Enable Train Fail-Safe:
sv_train_stop_owner_falloff 1
Note: 1 to enable / 0 to disable.
View Bob (Roll Angle):
rollangle 3.5
Note: Minimum = 0 (disabled); Maximum = 3.5 (highest)
Information (Reference) about more of the CVars used in the “Black Mesa” options menu, open ‘OptionsSubBlackMesa.res’ located in: ‘[b]…\SteamApps\sourcemods\BMS\resource[/b]’, with a text-editor (Notepad++ or anything similiar [preferably with line-counting]).
To spot the CVars, look for these two variables on both the left and right side:
"fieldName" ""
"cvar" ""
You could bind up an autoexec.cfg to be run every time you start the game which will add those parameters every time you want to play.
BMS forgets rollangle parameter after every loading, even the first one after BMS start. Is it known issue?
Yep. It’s on the list.
Yes, it is known.
There is a (possible) workaround for it, though (if you want it to be persistent, before the update is released):
rollangle "<VALUE>"
Note: Replace with any (valid) value between 0 and 3.5 (don’t forget the quotation marks “”).
How to proceed:
exec config.cfg
//exec threading.cfg
exec <FILENAME>.cfg
Note: Replace with the name of the file you’ve previously edited (and renamed).
Lastly:
This is not guaranteed to work, but it is worth a try, I guess.
It works for me, let’s hope it does for you, as well.
If it does work and you want to adjust or change the value, you have to open the file with the rollangle “” line and edit said value inside the quotation marks, then save and close the file.
Since autoexec.cfg is automatically executed on startup, changing the value in-game, then saving and closing the game would not adjust it permanently - the next time you’d start the game, it would be overwritten by the value specified in the cfg file (the one autoexec automatically executes).
Doesn’t game take params from autoexec.cfg itself every loading time?
It does, I should have mentioned that the mini-guide above is just one way - not the only one.
So, yes - you could just add rollangle “XX” to autoexec.cfg itself.
I just posted the ‘complicated’ way, since it looks ‘cleaner’ (to me, at least).
EDIT (10:53 AM): Now that I think about it, just adding the command to the autoexec.cfg could be the cleaner way, just to avoid (possible) “file not found” or “file: access denied” errors, ecetera.
Who knows, use whichever you like best and are most comfortable with.
As long as it does work (properly), either one of the two should be ok.
BMS doesn’t set variables from autoexec even after BMS start.
Just to be clear on this one, “View Roll” is this …:
View Roll (Reference Screenshot)
Size: 174 x 56
View Roll (Reference Code)
rollangle "<VALUE>"
Note: Replace with any valid value between 0 (disabled) and 3.5 (maximum).
… and “View Bob” is this:
View Bob (Reference Screenshot)
Size: 122 x 18
View Bob (Reference Code)
cl_bob_disable "<VALUE>"
Note: Replace with either 0 (disable the “Disable View Bob” flag) or 1 (enable the “Disable View Bob” flag).
Make sure to add both rollangle “” and cl_bob_disable “” to the “autoexec.cfg”!
Report back with your results, please.
EDIT (04:42 PM): This is an example of a (working) autoexec.cfg file:
exec config.cfg
//exec threading.cfg
rollangle "2.1"
cl_bob_disable "1"
Note: Just tested this in-game and it definitely overwrites the existing parameters, on startup.
Also, if you want to make sure if autoexec.cfg is (properly) executed, add this to Black Mesa’s launch options:
-dev -console
Then, start the game; there should be a window (the console) on the right side of the screen.
Do you see anything close to this / does it read the same?:
If you do, autoexec has been read and executed, if you see something like “exec: couldn’t exec autoexec.cfg”, the file has not been executed.
For those so inclined, I fixed the Auto Aim check box always being checked (without an autoexec workaround). From what I can tell, the value of “cvar_name” for “EnableAutoAimCheckBox” inside resources/OptionsSubBlackMesa.res was labeled incorrectly, and causing the issue. Simply open it in notepad, and change the value of “cvar_name” from “sk_allow_autoaim” to “sk_autoaim_mode”. That fixed it for me.
Founded in 2004, Leakfree.org became one of the first online communities dedicated to Valve’s Source engine development. It is more famously known for the formation of Black Mesa: Source under the 'Leakfree Modification Team' handle in September 2004.