OOS seems to occur more recent in the svns in the past 2 weeks. Used to have stretches where we'd never run into oos, past 2 weeks oos pretty much 10-20 turns in.
Seems essentially oos only when one comp stalls while processing things, though not all momentary freezes cause oos, pretty much every oos will follow a momentary freeze. Seems from the oos logs the comp that doesn't freeze is just processing things during the duration when the other comp's...
Yea, was thinking about booting up a third computer for bit more control group but he didn't want to. Just wasn't sure why svn 8580 and prior we couldn't just quit and rejoin nor use an save after the oos. It would just instantly oos when we tried either. Only one that wouldn't instantly oos...
Yea, threading was reduced to one, read around were rumours that it didn't matter but does seem to help. There are rare oos that'll always happen on certain turns, have encountered them 2 or 3 times. Was unable to resume matches from an oos save in earlier svns for whatever reason, worked last...
multiple barbarian units with swapped ids.
other ones just additional building built for one player while not for the other, and units in different locations.
Keep up the good work, remember doing rom years ago, was great cept think we ultimately stopped cause of eventual repeated oos errors. Re'ing civ these days tried c2c but that eventually oos pretty soon as well. Now doing kmod since that's ton more stable but it's also practically vanilla and...
insta OOS building wonder as player on the same team. Occasional OOS with unit naming enabled, units show up as not having the additional naming schemes when playing on the same team as well.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.