I'm pretty sure the latest version of mastercomfig (since 8.103.0) fixes the issue where mods get reverted after a few loads.
Account Details | |
---|---|
SteamID64 | 76561198046110893 |
SteamID3 | [U:1:85845165] |
SteamID32 | STEAM_0:1:42922582 |
Country | United States |
Signed Up | August 8, 2017 |
Last Posted | May 29, 2025 at 11:21 PM |
Posts | 1557 (0.5 per day) |
Game Settings | |
---|---|
In-game Sensitivity | |
Windows Sensitivity | |
Raw Input | 1 |
DPI |
|
Resolution |
|
Refresh Rate |
Hardware Peripherals | |
---|---|
Mouse | |
Keyboard | |
Mousepad | |
Headphones | |
Monitor |
Yeah keeping -dxlevel will reset the resolution, and change all sorts of other graphics settings.
What are your launch options? And what config do you use?
Try messing with m_limitedcapture_workaround 0 or 1.
You use -dxlevel once to set it, and after that first launch, remove it. Nothing else is needed. Don't use mat_dxlevel.
And yes, there's no reason to use those window parameters. Resolution only gets reset by using -dxlevel.
Remove -dxlevel 91 -full -w 1920 -h 1080
Personally, I have been using the NVIDIA Studio Driver, which is much more stable, and only is inferior to the game ready driver in terms of launch day optimizations, which I rarely, if ever, will use.
mastercomfig 8.104.0a3 released in early access:
Could you share your launch options so people can take a look at what may be causing it?
Try setting your resolution in video settings rather than using launch options.
what are your launch options and also try dxlevel 100
Only thing related to this that I know is replay_cache_client_ragdolls 1 but it may cause crashes.
mastercomfig 8.104.0a2 released in early access:
https://ko-fi.com/Blog/Post/mastercomfig-8-104-0a2-M4M51W26C
mastercomfig 8.104.0a1 released in early access: