con_filter_text bypass for VPhysics and FileSystem logging

Short answer: in both Source 2007 and Source 2013 builds, VPhysics and the file system logger do not route their output through the con_filter_text path. They consult their own internal verbosity controls, so the filter can be enabled, correctly matched, and still let those messages through. The bypass also does not collapse when you lower developer, because these subsystems track verbosity independently of the developer console variable.

Which branches behave this way

The behavior is consistent across the mainline branches rather than being a quirk of one game:

• Source 2007 (Half-Life 2 era, Portal) — VPhysics and FileSystem logging bypass the filter.
• Source 2013 (TF2, CS:GO-era builds) — the same bypass appears in the logging implementation.
• Custom forks — some forks add their own subsystem-level filtering cvars, but the stock behavior is inherited unless deliberately patched.

One caveat worth flagging: GoldSrc derivatives and heavily modified forks may reimplement logging entirely, so treat this as a mainline-Source claim, not a universal one.

Why developer level doesn't help

developer gates general-purpose diagnostic spam, but the bypassing subsystems keep their own verbosity tiers. FileSystem noise is steered by file logging configuration (e.g. filesystem_log_level-style controls and the fs_log family), and VPhysics chatter by physics-side verbosity settings. Lowering developer to 0 reduces the messages that respect it, but the filter-avoiding output continues at whatever level its own tier is set to.

Practical quieting strategy

Since one cvar can't do the job, layer the controls:

1. Keep con_filter_enable 1 with con_filter_text for the subsystems that do respect it — it still removes a large share of console spam.
2. Suppress VPhysics noise at its source using the physics verbosity cvars rather than the console filter.
3. For FileSystem noise, disable or narrow file logging instead of filtering: the bypass primarily affects .log file output, while VPhysics noise hits the in-game console, so the two need separate handling.
4. Set developer 0 for the remaining high-level spam.

Verifying on your build

Because forks differ, confirm rather than assume. On a listen or dedicated server:

con_filter_enable 1
con_filter_text "VPhysics"
developer 0

Then trigger physics activity and watch the console. If VPhysics lines still appear while other matching text is suppressed, your branch has the bypass. Repeat with developer 1; unchanged VPhysics output confirms the independent tier. Check which subsystem cvars exist with:

find phys_
find fs_

If your fork exposes a subsystem-aware filter cvar, prefer it over the stock filter for these two loggers.

The one detail that would change this recommendation is whether you're on a stock branch or a custom fork — fork-specific filter cvars can make the workaround unnecessary.