strange unit bug at start

[gourmat]

GnK v2.6 Beta2
gk enhanced mod v1_13_4 & v1_v14_beta2 both versions got same bug
perfect world got bug with and withouh enabled mod pw

hey guys, after half a year I was eager to see how the mod has improved yet, so I installed the lastest version and tried to start a game, then a strange bug occured which made the game unplayable:

the starting unit seems to have like a dozen promotions, on a few starts it had no sight at all, on one start it had like unlimited moves, on several starts it just vanished after moving it to unexplored territory, so I thought maybe the next unit is ok, but I was never able to reach the end of the production line as game seems to crash after a few turns completely. Also when trying to resign - crash.

Is this a known bug because its mayor, or just my machine? but last time gk worked perfect vor me, but it was v1_7_9

 

[mystikx21]

I can think of two possibilities to check.
1) Make sure your mod folder is clear of other copies of the mods. Steam Workshop can be pretty unreliable about parking outdated copies in the folder and requiring some cleanup to make sure there's no conflicts.

2) What version of Civ5 GK (unmodded) are you running? This sort of issue has usually been a version conflict in the past. Current version is : 1.0.2.44. Should at least be 1.0.2.21

There may be an issue with the walls fix in the beta from the new official patch fix but that shouldn't be not causing fog of war type errors (most likely city HP errors). That issue shouldn't appear in the stable version.

If it's not fixed by addressing one of those two, please post a lua.log file. . That may help track it further.

 

[gourmat]

may gk version was the problem as it was like 1.0.1.7 or so haha, thx for the help!!! could have thought about this myself, but as it was working before, so I didn't

 

[mystikx21]

There was a big update in the fall official patch that added a few things to the game... and then caused problems with the mod for people who didn't or couldn't update.

It's not an obvious issue to cause a serious glitch, but it's on the checklist as it happens a lot. No big deal.