 |
Though these are cvars, they also appear in darkmod/def/tdm_player_thief.def: // movement settings "pm_bobroll" "0.0015" //side to side roll "pm_bobpitch" "0.001" //forward roll "pm_bobup" "0.03" //upward bounce "pm_runroll" "0.003" //running side roll "pm_runpitch" "0.001" //run forward pitch "pm_runbob" "0.35" //speed of run bob "pm_walkbob" "0.3" //speed of walk bob "pm_crouchbob" "0.2" //speed of crouch bob What's happening is that TDM reads Darkmod.cfg, processes the "seta" commands there to set certain cvars, then later reads autocommands.cfg and processes any "seta" commands there to set certain cvars, then loads the map and spawns the player, giving him the values set in the above *.def file. So there's nothing we can do in the code to change the values of these things on the fly. The player can either: a - set up hot key bindings as discussed in the thread, and hit the appropriate key at the start of each mission or b - extract the def/tdm_player_thief.def file from tdm_defs01.pk4, change the values in that file, and place the file in the darkmod/def folder. This would need to be kept up to date as each TDM rev comes out, in case we make changes to that file |
 |
I suggested in the thread the player could assign a hot key to execute autocommands.cfg after the mission loads, but he'll have to do it every load more than likely. So far he's the ONLY person to request it. I'll let him know about your findings, he might want to do your B suggestion. |
 |
Just a note, regardless of the "why does headbob not stick" issue: autocommands.cfg was added to allow automatic dmap after the game DLL has been loaded and usually contains "quit" at the end. It wasn't really meant for adding commands that should be stored and executed permanently. "default.cfg" is what should be used for this, as it is executed before the game DLL is loaded. |
 |
The default cvar values were added to the source and given archive flags in 2.07 The pm bob and other pm args were removed from tdm_player_thief.def in 2.11 |
- Anonymous
