I have been asked how I stumbled on this fix (and also how exactly it broke the game), so I quote myself from before:Īttached a debugger.
Some have reported that it has resolved some delays occurring during gameplay itself too. The fix has been tested by a dozen or so people already and it appears that it solves most cases where the game hangs during loading when many mods/DLCs had been installed. Or you can just share patched executables to your pals. In the coming week, I will create a DLL that will automatically patch this limit during runtime for various different executables without having to modify the executable itself, but if you want to fix it right away (also I'm not entirely sure when I'll get to it), you can just follow the above guide. In case none of the addresses apply, you can search for the "BA C0 00 00 00 48 8D 4B" pattern in the hex editor, which should presumably be somewhere between B94000 and B98000. See the tl dr above to find the position it is at in your executable. The position in the executable to modify depends on the specific game version you have (there are around 5 different executables among 1.31-1.32 versions). It was limited to 192, which apparently was just about enough for the vanilla game, but will be hit very quickly once you start adding mods.įixing it involves just increasing that limit in the executable itself.
The actual thing limited by that number seems to be the number of file handles, one of which was used by each bundle, thus causing bundles from mods and DLCs to both cause that limit to be reached, and eventually fail to properly load after the limit was reached. The fix involves changing a hardcoded limit (just a single number) in the executable itself. I have found a proper fix for the mod limit issue.
(will replace with a link to mod once I have made one which automatically applies the fix)
0 kommentar(er)
