Ok i guess it fixed itself. Don't know why it was not working in the first place. I guess i thought it didn't work because using cl_interp in console during a game causes an error message in the console saying that you gotta leave your game before you can change it.

With net_graph set to 1, it doesn't show any lerp changes if you switch from scout (0.030) to demo (0.01515) during a game.

Isn't it not possible to change your interp while in-game? How does snapshot_buffer auto work?

How does the match HUD degrade performance as much as it does? I checked the docs on the feature for mastercomfig and didn't believe it could be that bad of an influence on CPU usage as to deserve the "HIGH" catagory. But after testing it in-game, it's not that far from the truth; my fps dropped by 30 or so from 140 average while idle.

yes and i've left the config.cfg file in the steam cloud folder in userdata blank (not deleted) and read-only. Sometimes tf2 settings just randomly turn off when i turned them on last time. the resolution thing was fixed by removing dxlevel commands from launch options, but not the settings stuff

Is there a reason why my tf2 settings get reset sometimes? I try to change my in-game resolution in the video tab but the changes don't save when i relaunch. Many commands and binds won't save unless i hit "Ok" after I change each individual bind or setting. Technically yes I could just go through the long process of setting everything individually and adding width and height to the launch options but i'd like the problem to just be fixed so that i won't have to worry about it coming back in the future

Do textures use vram? What's the performance impact of high texture settings vs. low texture settings in tf2?

How do I reload the hud once at startup like it worked by default in older mastercomfig versions?

After updating from version 8.3.5 to 8.3.8, the console was disabled (con_enable was set to 0). Is this a new feature or something overlooked?

Is the zoom_sensitivity_ratio in the flat mouse addon affected by aspect ratio, m_yaw, or both?

Does DirectX 8 support mat_queue_mode 2 or multicore/quadcore in general?

Changelogs in a nutshell:

We've improved the code.
New code sucks, going back to old code.

Frames dip when a cloaking/decloaking spy is on screen. Is this a config issue or an issue with hardware? Can this problem only be solved by upgrading specs?

Playing in directx 98, low preset with a few things set to very_low,. The bug seems to happen in that part of the spawn area. When I walk away, the lighting seems to return to normal, and back to dark when I return. Switching to dx8 fixed the problem.

Any reason why the lighting bugs out like this? https://imgur.com/a/o1oGP1m