Bug reports and technical issues

Okay.
 
Got this python exception popup (SVN 506):
Spoiler :
attachment.php
 
I'm not sure if I've already committed it, but I've fixed this error (can't check because I'm on the wrong OS atm). Maybe try another update.
 
Turns out I haven't committed it, but it's online now.
 
If the old world discovers the new world by a unit encounter outside of the new world civs' core areas, the conquerors do not trigger. This happens often enough. Not a bug.

Wasn't this changed a bit some time ago, so the conquerors were harder to avoid? I seem to remember something about it, but can't recall the specifics.
 
The mechanism for cancelling the conquerors if first contact is outside of the native civ's basic area still applies. I have used it variously as Aztec/Maya/Inca successfully in recent times.
 
I can't play the 600 map.
It keeps crashing at the "Choose your civ" phase, giving out appcompat.txt errors.
The 3000 map works OK, though.
I'm playing it on a pretty weak PC, so what could be the reason???
HELP!!!
 
The errors you're getting don't sound like they come from the game, but your operating system, so I think your guess that it is because of your PC's technical limitations could be right.

If you could go into more detail what the error messages say I might be able to give a more definite answer.
 
I am having a problem when playing the Aztecs.
When I run a game on 600 AD I don't get any units in Mexico, only one catapult in Antarctica.
On a 3000 BC start the game stops at "1 turn left", it doesn't crash, it just doesn't continue loading.
 
Antartic Catapult for 600AD Aztec bug is already existed since RFC Vanilla iirc.. and been mentioned here twice or thrice.
 
Leoreth, can you do something with the Baibars leaderhead? It has an annoying manner to take long to load and sometimes crash the game. It's the only leaderhead to do so in a really notable way.
 
Never had this experience. Can anyone confirm?
 
Back
Top Bottom