Performance issue after patch 1.3.1

[Fengxian]

Basically I'm having huge fps drops time to time when I'm playing now amd game is much more laggy. Never had this issue. Blaming on new patch notes. idk, updated windows, verified game files, problem still persists. Is it just me?

[NoDMoD]

I also have way worse perfoamce in sieges and also a very frequent battle crash, 1.3.1 made it unplayable in mid-late game

[Ouroboros]

Same for me. Game ran optimally before but now it's choppy most of the time. Plus it's crashing pretty frequently, I don't know if that's just me, but it NEVER crashed before, after 1.3 hits, it crashes at least once every session.

[Morkonan]

Someone posted a blurb last night in a thread somewhere concerning "Windows Game Mode." Reportedly, that Windows "Creators" addition, part of Micro$oft's unrelenting assault of garbage downloads, causes issues for people who want to use that mode to play "games." I am sure many well-paid scientists and researchers are attempting to understand this problem... And, this is why I don't download Windows Creator/Content/Garbage. But, anyway:

If you have this mode "on" or your computer does it automagically or whatever the crap it is (I don't know, because I don't game on Win10 and don't download such garbage from M$oft) then you may want to do an Internetz search and see if you can disable it so you can test if that is truly the cause.

The reports of bad game performance, lag, stuttering, etc, were pretty wide and extended across a number of different game types. So, it's worth looking into if you can't figure out what the problem could be.

Otherwise, the first thing I'd do is make sure there were no mods loaded and, preferably, all of them uninstalled with their .dll's too. Then, I'd dump everything in Options down to "Low" or lower and then play to see if I could recreate the problem. IF the problem still persists with every option either set to Low, Very Low, or toggled off, then I'd start looking at system issues.

It's not unreasonable to assume this is truly a "patch problem." Mistakes happen. But, I wouldn't fixate on that until I had tested everything else. For instance, the patch could have made an adjustment that is, overall, a good one. But, that change could have revealed a problem with your specific environment. Check that first.