The first and longer game actually had various extra mods on (R.E.D - Tree Growth - Active Defence) while the other only had the mods you supplied.
Well, this mod is not compatible with R.E.D., and I don't know what'll happen if you try using both. At the moment it probably wouldn't be too bad, since both about have the same number of entries (only crashing once you got to the Labor Mech), but in the near future the two will be COMPLETELY incompatible as I start adding more unit model definitions.
I have no idea about those other two. If they've got any Lua components, there might be conflicts.
As for the rest, there are several separate issues.
First, there's something wrong with Civ5 itself. If you make an "empty" mod, one that does absoutely nothing, you'd get crashes. To me this implies switching to a less optimized engine when playing with mods, and it's not hard to believe that there'd be something wrong there. More on this below.
Second, there's a general graphical issue. On my computer, the DX9 executable is far more stable than the DX11, and part of it might just be that it can't handle the same high graphical settings it had in vanilla. The graphics often slow down just before a crash, and the three most common times for a crash:
1> When replacing an old improvement with a new one, especially if the hex contained a newly-revealed strategic resource that the new improvement would harvest.
2> When performing "recon", especially with an air or naval unit, where the game would try to update the improvement/terrain graphics on dozens of hexes at once. (Things like the forest spreading mod, or the terraforming I add, might make this worse.)
3> AI combats. According to several people's logfiles, the game sometimes crashed when it tried doing two combat animations at the same time to the same unit, starting a second combat before the first had finished. This might be tied to the unoptimized issue above, where the game has some sort of lockout timer to prevent conflicts like this but simply doesn't lock out for long enough when running with mods.
Most crashes I've had occurred at one of the above three times, and all of the above would apply to any large-scale mod. But, there also are several potential crash issues in the mod itself. I say "potential" because they MIGHT be responsible for crashes, but I have no way to be absolutely sure. These include:
1> For units, I use placeholder models. When the game attempts to animate a model in a way it wasn't designed for, you get crashes. (This is known.) I previously had this problem when I'd do things like use an infantry unit model for an air unit; the moment it would try to rebase, it'd crash. So presumably, any mismatch in what a unit model is built for and what a unit can do might cause issues.
I've tried picking better placeholders, but it's still possible that this is happening. On the bright side, this should go away once the new models are added, but only if I can find ways to add all of the appropriate animations as needed for each unit.
2> For resources/improvements, there's a conflict. Take Dilithium as an example: Uranium graphic, Offshore Platform improvement. Obviously, the game has no idea how to combine those two together, and so it'd blank out the hex. I've partially fixed this in the version I'm using now; I added improvement art defines allowing the Offshore Platform to pair with Uranium, and so on for the other strategic/improvement combinations.
It still doesn't quite work, because the game doesn't know how to find the Offshore Platform artwork when you're not working out of the core game's file structure. (I'm checking to see if changes to the core game's base defines files fix this. It's not how I'd prefer to do things, but if it works I won't complain.) But on the bright side, it no longer blanks the hex; you'll still see the resource, at least.
I'm still running tests to see if this was responsible for any crashes. It's possible that the AI was trying to improve, say, Omnicyte tiles during the interturn, which'd screw up the graphics, and the AI had no idea how to deal with this when it had to alter the graphics for twenty hexes at once.
I'd love to say that this one would be fixed with custom graphics, but it doesn't seem like that's possible at present.
3> Many early-era buildings added a certain graphic to the terrain, to where you could see that the city had each. This was especially common with wonders, but several non-wonder buildings had this as well.
My buildings don't have custom graphics, but it's possible that the game is trying to draw something for some of them anyway, and crashing as a result. Or, that it's got hard-set thresholds for how developed a city has to be for each stage of graphical sprawl, and that the addition of all of these buildings and such is screwing up the math.
Again, I can't add custom graphics for this one, but I can try to ensure it doesn't use an unset variable.
So I nuked them (see next pic), and cleaned up the survivors with bombers, fighters, and arty. The really interesting thing happened a couple turns afterwards when I found Munich to be starving. I pulled up the tile management screen and found that all the aquatic tiles were still considered as blockaded, even though all the attackers had been dead several turns. Is this a bug, or this the game's way of expressing fallout in water tiles (i.e. the tiles are unworkable because of fallout)? If it is fallout in water, then how do I clean it up?
Your right. I slid a fighter over into that area and found a sub hanging around. After the sub was gone the water tiles became accessible again.
I was thinking of paradox games and how steam messes up beta patches.
.
