Results 1 to 4 of 4

Thread: CTD when starting siege battles

  1. #1

    Default CTD when starting siege battles

    On Linux, the game crashes whenever I try to fight a siege battle manually, with error code 361. It has happened as both the attacker and defender. As the attacker I had a full stack, and the defenders had ~7-8 units (it was early game Alexandria Exchate, and I was on Hard campaign difficulty, if that helps narrow it down). As the defender both armies had about 10 units. It doesn't happen with field battles, which I confirmed both in the Bactrian campaign where the aforementioned crashes happened, and by quickly loading in a fresh Roman campaign and getting into a fight.

  2. #2

    Default Re: CTD when starting siege battles

    I did some more testing (read: playing other campaigns), and I think it's either a problem with stone walls or maybe a greek unit? I was able to fight a siege battle as the Celtiberians, but the walls were only a pallisade, and a siege battle I tried to fight as the Greek League crashed.

  3. #3

    Default Re: CTD when starting siege battles

    Did you remove the custom settlements like the installation guide says to do? Yeah, it's the buildings. You end up having to play with vanilla settlements, so your buildings look Aztec, but at least no CTD :/

  4. #4

    Default Re: CTD when starting siege battles

    That worked, thank you. I only skimmed the install instructions, so I guess I missed the OS specific section.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Single Sign On provided by vBSSO