Bug Reporting

[ruff_hi]

It seems you didn't translate ALL of BUG (at least to french):

Are you pointing out that they said 'quitter' instead of 'sorte'?

 

[EmperorFool]

It seems you didn't translate ALL of BUG (at least to french):

Yes, we are still missing some French translations. If you'd be willing to help, we'd gladly accept missing translations.

 

[EmperorFool]

Are you pointing out that they said 'quitter' instead of 'sorte'?

I think mystyfly is pointing out "Worst Enemy" at the top.

 

[ruff_hi]

I think mystyfly is pointing out "Worst Enemy" at the top.

no-one understands my humour

 

[EmperorFool]

no-one understands my humour

Dunno, try some of it on us!

 

[mystyfly]

I'm definitely not gonna sign up for translating to french altough I probabely could do some german translations. I'm currently playing in french because I have to learn that freaking language at school and the lessons there never helped me much so why not have civ help me?
Yes I was referring to worst enemy, in french "pire ennemi"

 

[Caesium]

As reported earlier there is a bug in the MainInterface, when pointing on an air unit:

I get python exceptions when selecting air units (Airships at least).

Something about airCurrCombatStr being called with different C++ signature (in CvMainInterface.py).

This has to do with the unit info pane... I found the call, in line 1835

fCurrStrength = float(pUnit.airCurrCombatStr()*0.01)

if you change that to

fCurrStrength = float(pUnit.airBaseCombatStr())*float(1.0-pUnit.getDamage()*0.01)

and also replace airMaxCombatStr by airBaseCombatStr in the next line (and remove the *0.01), it should work.

Best Regards,
Ace

So I looked into the normal code that displays strength for air units, and it is using getBaseAirCombat(). I didn't want to switch to the method used for land units without investigating. Therefore, while the above code works, it may differ from the game's display.

I'll copy the code used by the regular game to fix this problem correctly. I have some outstanding changes to my CvMainInterface.py that are causing a small delay, but I hope to do that tonight.

Is Ace Of Spade's code correct or are you going to release another code?


----------

Here's a new one:

File "CvMainInterface", line 1163, in tempMove

ArgumentError: Python argument types in
CyUnit.setXY(CyUnit, int, int)
did not match C++ signature:
setXY(class CyUnit {lvalue}, int, int, bool, bool, bool)
ERR: Python function handleInput failed, module CvScreensInterface

The shown bug's line is the same as in your svn.
Could you please give me a solution for this one?

----------


And another bug, that is still in there:

  File "autologEventManager", line 325, in onEndGameTurn

  File "autologEventManager", line 1025, in checkStuff

IndexError: list index out of range
ERR: Python function onEvent failed, module CvEventInterface

-----

  File "autologEventManager", line 327, in onEndGameTurn

  File "autologEventManager", line 970, in storeStuff

IndexError: list assignment index out of range
ERR: Python function onEvent failed, module CvEventInterface

How can I fix this python error?

 

[Milly]

Um, I'm not quite sure if it this fits, but...

None of the BUG shortcuts, like pushing ctrl+alt+o for the BUG customization menu, actually work for me. Maybe I installed it wrong...?

The thing is that all the other stuff showed up. It's stuff like alerts that aren't working.

 

[jjasio2]

I've run into the bug described by dot in post #2. I think I know what triggered it in my case. The "My Documents" directory path on my account contained a polish specific letter "Ł". After i changed the directory path to one with english font letters only the problem disappeared.

 

[Cammagno]

I just realized that Unit Naming doen't work anymore (at least for me)... I can't say from when, the only thing that I can say is that I'm using the last SVN version of BUG... somebody else using the SVN version has similar problems?

 

[ruff_hi]

unit naming is working for me. do you have it enabled? have you tried running civ with the error logging on? If so - any errors?

 

[Cammagno]

unit naming is working for me. do you have it enabled? have you tried running civ with the error logging on? If so - any errors?

It is enabled, and no error in the log: simply, the units keep the standard name.
But if it is ok for you, maybe I made something wrong locally, so I'll try to delete BUG folders and take them again from SVN.

Edit:
Done, but still not working
The Ctrl+Alt+N test works, but the unit naming in game not.

 

[Milly]

The "sit-rep" option in the military adviser stops working when a permanent alliance is formed.

 

[EmperorFool]

The "sit-rep" option in the military adviser stops working when a permanent alliance is formed.

The version in our Subversion code repository is fixed. Otherwise I'll be releasing a 3.1 version in a few weeks or so. Actually, the bug was with Defensive Pacts, so I hope I fixed the PA situation as well.

Can you please grab the latest version of the CvBUGMilitaryAdvisor.py file from this page and try it out?

Or you can of course update the entire BUG install to the latest using the TortoiseSVN application. Instructions for this are on the Download thread's first post.

 

[Milly]

It doesn't really work, Emperor. :/

 

[EmperorFool]

It doesn't really work, Emperor. :/

Can you please post a save file that has this issue? Do you have the PA with another player, or is it two (or more) other players?

 

[Milly]

Here's the save. I have a permanent alliance with another player (Surya-whatever). You'll need to use the Wolfshanze mod to open it, so I apologize for the trouble.

 

[EmperorFool]

You'll need to use the Wolfshanze mod to open it, so I apologize for the trouble.

Ah, I can do this at a later time perhaps, but if you can post the Python exception you're getting, I might be able to make a quick fix sooner (won't have to install the mod).

1. Turn on the logging system (maybe you already have it) and turn off python exception popups (probably aready off)
2. Run the game and open the Military Advisor
3. Quit the game
4. Open Logs\PythonErr.log (not the one with a "2" in it)
5. Post the entire contents in a [ code ] ... [ /code ] block (# button above post editor)

 

[Dresden]

The Furious red-face icon in GameFont_75.tga is one pixel further left than the other attitude icons which means it doesn't quite line up in the scoreboard. It's real subtle and I doubt many would notice it, but for some reason it was really bugging me; so I went and changed it on my copy. I also darkened up the shadows on the Annoyed and Cautious faces so that they matched the others but that change is almost completely unnoticeable...

Anyhow, here's a before-and-after screen showing just how insanely picky I am and attached is the altered GameFont_75.tga if you all want to use it.

EDIT: Attachment removed; EF merged it into BUG.

 

[EmperorFool]

The Furious red-face icon in GameFont_75.tga is one pixel further left than the other attitude icons which means it doesn't quite line up in the scoreboard.

Hooray!

I can finally scratch this off of my BUG todo list. It has been there since the beginning, and I Just haven't gotten annoyed by it enough to fix yet (probably because I can't see it in the game). Thank you.