Thunderbrd
C2C War Dog
i got error that bother me many games..
then i select unit (all types (from hunter\clubman to workboat)) and then select other unit that i want to attack (hold right mouse button) i got:
Traceback (most recent call last):
File "CvScreensInterface", line 1371, in forceScreenRedraw
File "CvMainInterface", line 1535, in redraw
File "CvMainInterface", line 6349, in updateHelpStrings
RuntimeError: unidentifiable C++ exception
ERR: Python function forceScreenRedraw failed, module CvScreensInterface
but game run fine - so i think it is only ODDS calculation and showing to player.
Update:
In second city i got lawyer...in 23650BC....
Apparently python's not liking something there. A few points to consider:
1) Stack attack is detrimentally bugged and will be for a while before it can be repaired. If you're using stack attack you could have some issues.
2) There is also a known bug lurking somewhere in the unit attack evaluations that can send a much less optimal attack in than the one it's displaying. It may just be that a selected stack may have some units that target particular unit types and for them they have a great odds but they aren't selected to attack the actual stack by the same criteria so you get the best of some worse options you didn't see. Anyhow, it's advised not to select multiple units for attack evaluations. Do them singularly for accuracy - and perhaps you won't have this problem doing so either.
It's known these are issues to address but they aren't the highest priority due to there being workarounds available to the player and due to the complexity of the bugs themselves.
Now... I cannot say for sure there isn't something ELSE going on in python that's negatively reacting to something about some of the changes in the combat help hover but I haven't seen them myself so it must be an unusual condition to my test environments causing it. The evaluation to track it down should come from the python end first since that's where the error report is coming from - from there, identifying the problem spot might let me know what disharmony is taking place between py and dll.