| 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 | |
beastieThe graphical settings I set on the app don't actually save. Is there a way to create a .cfg or something to be loaded like the modules.cfg from the previous version?
Did you click apply? Also make sure you don't have any old mastercomfig VPKs in your custom folder.
And all the old files are compatible. modules.cfg and custom.cfg will override the app's settings.
Wackyfireball
See if 7.0.0a2 fixes the first two issues.
As for the next one, there's something wrong with your VPK or config in that case, as client_precache.txt and the user cvars work fine for other people.
WackyfireballWhy does it still run in process even after I close it? Also I can't change or the changes doesn't show up to a new config after I made one config.
It should not be still running, how are you closing the window?
And could you explain your other issue in more detail? Not sure I understand.
Brimstoneso it appears it simply creates one mastercoms.vpk in your custom folder, should we then delete all the old vkps we used to have?
Yes.
A fix has just been deployed to fix a critical issue in the config. Just click apply in the app to get it!
Wackyfireballwhat do we need to download for it to work.
Just download the installer for your operating system. If you're on Windows, that would be the exe.
asianb0yhany updates on mastercomfig 7? really looking forward to it
I'm still working on polishing it. It'll come out as a beta soon though.
pancake_stacksHaven't downloaded in a while, but what happen to the heavily commented files? Anywhere to still see updated versions with commented lines?
On GitHub, you can look in the config folder for everything.
morwannegAlready unusable, message windows blink and then disappear and can't be reopened from a specific person on my friends list. Super annoying when I'm actually trying to actively talk to that person. Guess I'll remain on the old client until it's actually fixed.
https://steamcommunity.com/groups/SteamClientBeta/announcements/detail/2780291848385033126
Try rate 75000. That should be good for your speeds.
Also your speeds don't support that sort of packet rate, use
cl_cmdrate 64
cl_updaterate 64And to mitigate the effects of packet loss, increase your interp. I would recommend using interp ratio 2, so with cl_updaterate 64, set these
cl_interp_ratio 2
cl_interp 0.03125cebolinhadoclimehello, I would like to get the last drop of fps in the game (yes I have a horrible computer) I'm already using cfg very low I would like to know if there is anything that can increase my fps and sorry my english is awful ;-;
mastercomfig very low already does everything possible to increase fps
knsumeIf they're really going for the "discord but on steam" route they really need to make their voice codec better cuz that shit draws twice as many resources as discord does.
Do you mean the new one? Or the old one? Because they updated it:
Valve
- Voice chat updated to new WebRTC-based backend
- Voice chat uses high quality Opus encoding
oblaPossible end to Steam skinning if this guy speaks the truth?
https://steamcommunity.com/groups/metroforsteam#announcements/detail/1645384648842466293
I don't see how that's an end. It's obviously not supported at this time, but I would expect Valve to add official support for customizing CSS so that it isn't replaced at a later point.
sibbydoes anyone have screenshots of what it looks like? id rather not remove my skin to see what the changes are
it's on the website that was linked in the OP
rmi didn't manage to play with b3 bc you already released b4.
i was using preset_very_low.
It's helpful to know what version introduced these issues so if you could test other versions of the beta to see which one first caused the problem, that would be great!