con_filter_text doesn't affect what gets logged, only what's shown in-game.

I could make it less likely for random things to get logged by putting all the save commands (~60 lines) into a single giant alias instead of executing them line by line, but that would kill all readability.

Over the past year or so I've been using it no random stuff made it's way there. Even if it did, the chance of it being something disruptive is extremely small imo.

B

I've refactored and optimized it a bit. All alias names changed so comments above don't apply anymore (but README should be more readable now). Functionality is still the same, so if you're already using it you don't need to update. Also packaged it into a VPK for easier installation and faster load.

bump bc big update, lots of improvements - faster, less crashes
trdr: custom shader that shows world and depth in split screen, so you just rec that

If anyone is doing it the old way, I suggest you read the new version:
https://github.com/jooonior/tf2-how-to-record-depth/

the old version still exists for the cavemen out there:
https://github.com/jooonior/tf2-how-to-record-depth/tree/v1

https://open.spotify.com/playlist/6c6Ra1iI1JjhADV2gnT7p6
weekly playlist with mostly less known indie/lo-fi stuff, can recommend if that's what you like

https://raw.githubusercontent.com/ldesgoui/tf2-custom/master/optimal-respawn-bind/cfg/orb.cfg

UPDATE 2020-12-01

ReShade disables depth effects when it detects network traffic to prevent ppl from using cheaty effects in multiplayer games (and game devs banning reshade bc of it). If you see the recording going black for no reason, this is what causes it.

An easy workaround is to unplug your Ethernet cable when recording, but that's kinda dumb. A better solution is to build ReShade from source yourself with the network check disabled (or dm me for it). This version can be considered a cheat, so you shouldn't use it when playing.

They updated the game and now TF2 will crash on launch if Steam isn't running (thanks guys), so you can't just close Steam as I say in the guide.
According to this article (section 1a) the solution appears to be to have Steam in offline mode. This is more of a temporary workaround until I find a better way to do it.

The issue could be with how Lawena launches HLAE. What happens when you start TF2 through HLAE yourself?

Some maps have what is called a 3D skybox that adds some distant scenery. When you change the skybox texture, the 3D skybox stays the same. This can look ugly if you're using a texture that has a different color palette then the original (like night theme or the lawena orange ones).

Random example from the fragvid tread...
EDIT: Looks like timestamps don't work with embedded videos, skip to 0:43.

https://youtu.be/NAUCufzU0QE?t=44

Solution? Turn the 3D skybox off. This is the command.

r_3dsky 0

basically: not mentioned = stock

2020-10-02

Halloween 2020 hotfix

• fixed crash when opening matchmaking menu

https://github.com/jooonior/tf2-hud/tree/hotfix

How would I go about editing the casual end of the match scoreboard? Is there a way to force it to appear or do I have to sit through the entire game every time?

So that doesn't cause the issues mat_antialias does and should be what is used to remove DashboardDimmer?

Also, does mat_aaquality actually change anything? It's not in mastercomfig and I didn't notice any differences between values. No difference would mean I don't have to restore it, which would save one reload:

wait 5; showconsole; toggle mat_aaquality 0 1; hideconsole

Is there a reason for blocking mat_antialias, other than it slowing down launch? Your implementation can still be bypassed with toggle mat_antialias 0 or by editing valve.rc. The only thing it prevents is using incrementvar, which means I can't just toggle it back and forth and have to use fixed values, which only hurts the user.

Not a real answer, just that I've been using mastercomfig ultra for recording and if there's a difference, I didn't notice.