head bobbing

[trioptimumscapes]

Sorry if this is the wrong place to post this topic but I have a problem

If I open the console while playing the dark mod and type,

seta pm_bobroll "0"

seta pm_bobpitch "0"

seta pm_bobup "0"

It disables the head bobbing in the dark mod and feels more like original thief to me .This works great .

My problem is I just cant get it to work in the dark mods cfg file , so I dont have to open the console every time I play.Ive tried creating autoexec.cfg files as is suggested in the darkmod wiki but still cant get it to work .

Any step by step help would be appreiciated. Cheers.

 

[peter_spy]

Autoexec.cfg is mostly for commands to be used before the engine starts loading, for everything else use autocommands.cfg

[trioptimumscapes]

cheers I'll try that.

I also notice that the fov option in the new update only changes the fov when u pick an object up?

[BuckleBean]

In addition to populating the autocommands.cfg with the values you listed, I also had to bind it to a key to get it to load. My Darkmod.cfg has this:

 

bind "F11" "exec autocommands.cfg"

 

You should be able to choose a different keybind if you want. I have to press this every time I load a save. Not a big deal, but something to keep in mind.

[trioptimumscapes]

ah ok , thanks

[peter_spy]

You shouldn't need to load autocommands.cfg, its content is executed after the main menu loads. You can see that in the console messages. But if you need to bind that commands to keys, you don't have to reload the whole file, you can just have something like: bind "F1" "pm_bobroll 0"

[BuckleBean]

You shouldn't need to load autocommands.cfg, its content is executed after the main menu loads. You can see that in the console messages. But if you need to bind that commands to keys, you don't have to reload the whole file, you can just have something like: bind "F1" "pm_bobroll 0"

 

Yes, I've seen that stated before. Nevertheless, the head bobbing is ever-present until I press F11. In all likelihood, this is something on my end. User error, misunderstanding, or other such mistakes are totally plausible. Whatever the case may be, it's working well enough.