Can this error possibly be looked into, and maybe even fixed by this mod?
Sunconure11 opened this issue · 10 comments
https://user-images.githubusercontent.com/5614902/266851142-f75fea21-7b85-4ccc-b6c8-d76cc9e2ad5b.png
There are multiple conflicting statements as to what causes this, ranging from packet stuff, to statistics. Maybe this mod could fix it?
There has since been far more info @embeddedt obtained. I suggest looking over those two issues.
The most likely culprit I can think of is the registry being too large... possibly due to the number of mods installed. I don't think this is being caused by ModernFix. You could try enabling debugPrintMessages in the Connectivity config and see if it shows anything more useful in the log.
I wasn't saying this was caused by ModernFix, I was asking if this is a thing that can be fixed by it.
There isn't enough information for me to fix anything at the moment; networking errors are very difficult to debug.
Well, I've also been discussing it over at PacketFixer, just in case it can be fixed there.
It is not clear exactly what fix (if any) would resolve this issue, and at this moment I don't have time to debug the network subsystem further. As this is not a ModernFix bug, I'll close this for now.
It is not clear exactly what fix (if any) would resolve this issue, and at this moment I don't have time to debug the network subsystem further. As this is not a ModernFix bug, I'll close this for now.
Don't worry, I've already fixed this in Packet Fixer.