It is possible that the P bind is lost due to own scripts or demos (since they record all commands you use). So please rebind the key using the console by typing bind p startrecording
and it should work fine.
You should
or if you use http://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html you can right-click X:\Path\To\Target\Folder (target) folder and select “Pick Link Source” and then go to tf dir and right-click to select “Drop As…” -> “Symbolic Link”
Try the following until it’s fixed:
mat_queue_mode 1
in your console (fixes multithreading issues)recording.cfg
file inside Lawena folder before running the game. Crashes might be related to graphic configuration set by that cfg file.lawena.log
file that the tool created and we’ll figure it out together.AccessDeniedException
in the log! What’s wrong?When replacing files, sometimes the tool encounters a process that is blocking a folder (like tf/cfg
or tf/custom
) from being moved, failing to put lawena’s files into TF2. Most of the time it’s explorer.exe, in which case you could try killing/relaunching it from the Task Manager. If that does not help, try relogging or restarting. Sorry for this inconvenience while I work on a definitive fix.
Just open the tool once again and then close it. That should restore your cfg, hud and sounds to normal. If it doesn’t check the Troubleshooting section under Instructions and follow those steps.
Don’t ever delete folders named ‘lwrtcfg’ or ‘lwrtcustom’. They contain YOUR files!
Yes, it’s the only way to ensure that you recover your previous DirectX level on TF2. Otherwise, you’ll be stuck at dxlevel 98. (the key is HKEY_CURRENT_USER\Software\Valve\Source\tf\Settings\DXLevel_V1
)
Yes, it’s the same script running over and over to check if your TF2 is still running, don’t worry.