You must change, in BUG options, the draw method for the plot list from BUG to Vanilla.The icon for the first unit is overlapping with the active unit box in the bottom corner, so I'm unable to select the Stone Thrower in the screenshot:
You must change, in BUG options, the draw method for the plot list from BUG to Vanilla.
Please provide a save so I can properly debug the raw text that is being processed behind the scenes in that tooltip.The hover text over a city gives errors concerning the font when certain units are present, e.g. Police Dogs, it could also depend on the upgrades those units have.
View attachment 491052
Well done!PPIO v0.5.9.4.9.5.9
- Fixed tooltip bug reported by Snofru1 above. A real "4 hour" head twister that debug process was, but I got it fixed in the end.
Thanks, what really threw me off was that "</font" part as it isn't in the raw text python gets from the dll, and python didn't add it there either under the text format post-processing code I've written.Well done!
Are you saying that the city screen doesn't work when playing the game in french? That's utterly strange...Your mod doesn't work in French, look at the problem on the pictures.
Do you get any python errors in the pythonErr.log file?Yes exactly, in French i'm not building in the city screen but in English everything works well.
Thanks !
To get pop-ups about python errors in-game you can in your %USER%\Documents\My Games\Beyond the Sword\CivilizationIV.ini
change this setting from 1 to 0 .
HidePythonExceptions = 0
The pop-ups will tell you what the error was whenever something is written into the PythonErr.log.
In BUG options, under the system tab, you can find an option for the level of python logging to the pythonDbg.log file.
Set it to the "Debug" level.
The pythonDbg.log file can help me understand what happened in code at the time the error occured.
But it is important that you alt+tab out of the game whenever you get a python error message and secure the pythonDbg.log (make a copy of it) file before doing anything else in your game, that way the last lines in the pythonDbg.log file is what happened in code right before the error message popped up.
The screen logging level is not important, I have it set at "Info". It shows python debugging info in the message window right below your research bar.