pak1 & pak2 verification on every startup

[Американский Шпион]

latest windows builds

[Frank Sapone]

Does it say it failed? If not, is your config files read-only?

[Frank Sapone]

You can test if your config file is readonly by muting the game or changing your video mode (i.e. windowed to fullscreen) then re-launching the game to see if it remembered these settings.

[Frank Sapone]

Also, send me your autoexec.cfg, curcfg.cfg and current.cfg.

[Американский Шпион]

I have found the root of an issue. I had saved a custom config (that I use for multiplayer) and every time game launched it used that cfg. but the game does not save any changes to it on it's own, unless you press a save button. I set my current config as current.cfg and that fixed the problem

[Frank Sapone]

Are you having a specific problem of the game not saving this to your custom config? Because that may be a separate related issue I should investigate. Most people don't save their config under a different name and simply use autoexec.cfg for any special settings and let current.cfg take care of the rest.

[Frank Sapone]

Current.cfg was always being written to when you quit the game or left the main menu instead of the "currentconfig" CVAR in the curcfg.cfg file. Fixed this behaviour.