Results 1 to 15 of 15

Thread: CTD's on sieges (Steam)

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default CTD's on sieges (Steam)

    I installed Broken Crescent and followed your instructions. (In terms of the files to delete, and put those various .txt files in their proper places, etc.)

    The thing is, whenever I have a siege battle - either in the campaign or with a custom battle - the game crashes to the desktop. It does so about halfway through the loading screen.

    Should I uninstall BC and reinstall it? What other options do I have?

    Thanks.

  2. #2
    wudang_clown's Avatar Fire Is Inspirational
    Join Date
    Jan 2009
    Location
    Poland
    Posts
    7,357

    Default Re: CTD's on sieges (Steam)

    Few fans have had this problem before. Reinstalling M2TW (including correct patching!) and BC helped for some of them. So try this in the first place.

    Under the patronage of m_1512

  3. #3

    Default Re: CTD's on sieges (Steam)

    I've modded MTW2 pretty extensively; it would be a real chore to have to undo/redo everything in MTW2 vanilla. Is there another way that wouldn't require me having to touch MTW2, and only BC?

  4. #4
    wudang_clown's Avatar Fire Is Inspirational
    Join Date
    Jan 2009
    Location
    Poland
    Posts
    7,357

    Default Re: CTD's on sieges (Steam)

    If you have modified your M2TW, then I can't help you, but advice a total reinstall. I don't know what changes have you made and how could they influence BC. And you can always make copies of those modified files. If re-install doesn't help, you will be able to re-load your modifications.

    As last thing before re-installing the game - check the BC log from the moment you try to enter a siege battle; maybe there is a clue of the error.

    Under the patronage of m_1512

  5. #5

    Default Re: CTD's on sieges (Steam)

    Yeah, the log just said "unspecified error" at the very end. I'm sure it has something to do with the buildings, since I've done control tests. The CTD's have nothing to do with units (since battles load just fine with all units, in both custom and campaign.

  6. #6

    Default Re: CTD's on sieges (Steam)

    Ok, I've tried replacing all my MTW2 files with the vanilla files. I have not modified any of the Broken crescent files.

    Still an issue. In fact, when I'm on the menu for custom battles, the game CTD's when I just select a type of settlement.

    For example, I'll select "Grassy plain" as the terrain for the fight. But the moment that I click on the settlement menu and select "large town" for example, the game crashes to the desktop.

    Any reason why that could be? Should I just delete all my Broken Crescent files and re-install?

  7. #7
    wudang_clown's Avatar Fire Is Inspirational
    Join Date
    Jan 2009
    Location
    Poland
    Posts
    7,357

    Default Re: CTD's on sieges (Steam)

    Quote Originally Posted by Naja View Post
    Ok, I've tried replacing all my MTW2 files with the vanilla files.
    What do you mean?

    Under the patronage of m_1512

  8. #8

    Default Re: CTD's on sieges (Steam)

    Quote Originally Posted by wudang_clown View Post
    What do you mean?
    It means that before I started modding MTW2, I saved all the vanilla files in the "Data" folder and placed them in a separate folder on my desktop. To make sure that none of my modding was affecting Broken Crescent, I deleted my modded MTW2 "Data" folder and replaced it with the original "Data" folder.

  9. #9

    Default Re: CTD's on sieges (Steam)

    try this: select grassy plain and select settlement type "fort".

  10. #10

    Default Re: CTD's on sieges (Steam)

    Quote Originally Posted by megalitho View Post
    try this: select grassy plain and select settlement type "fort".
    I can't select any settlements on "grassy plain."

    In fact, when I select "fort" on any of the other maps, it does this weird thing where the "settlements" tab shows "none." Then the only two factions I can use are the Turkish Sultanate and the Mongols.

  11. #11

    Default Re: CTD's on sieges (Steam)

    Ok -- you´re right.
    at first select a map without the crossed swords
    then select settlement: "fort"
    then select culture: "northern europe"
    then select era/period: "all"
    then select your settlement

    That is the way it should work -- hopefully

  12. #12

    Default Re: CTD's on sieges (Steam)

    Quote Originally Posted by megalitho View Post
    Ok -- you´re right.
    at first select a map without the crossed swords
    then select settlement: "fort"
    then select culture: "northern europe"
    then select era/period: "all"
    then select your settlement

    That is the way it should work -- hopefully
    OK, fort battles work when I follow your instructions.

    And I was able to select a settlement after I selected "fort." But the game crashed to desktop during the loading screen. Why can't Broken Crescent process settlements? I put the vanilla MTW2 files back.

  13. #13
    wudang_clown's Avatar Fire Is Inspirational
    Join Date
    Jan 2009
    Location
    Poland
    Posts
    7,357

    Default Re: CTD's on sieges (Steam)

    Quote Originally Posted by Naja View Post
    But the game crashed to desktop during the loading screen. Why can't Broken Crescent process settlements? I put the vanilla MTW2 files back.
    Workaround posted by megalitho works for me too. This was a problem in Third Age too, and I know Invasio Barbarorum II suffers it as well, so I think you must have done something else that disallows you to start custom siege battle.

    Under the patronage of m_1512

  14. #14

    Default Re: CTD's on sieges (Steam)

    Quote Originally Posted by wudang_clown View Post
    Workaround posted by megalitho works for me too. This was a problem in Third Age too, and I know Invasio Barbarorum II suffers it as well, so I think you must have done something else that disallows you to start custom siege battle.
    Well, the problem is that it's sieges in the campaign, too. Not just custom maps. All sieges in BC lead to CTD's for me.

    What's weird is that seiges in the campaign work fine when I don't attack. When I besiege a settlement, then wait several turns for the AI to sally out, the battle takes place just fine.

    But when I actually attack a settlement on the campaign map (like with catapults or seige equipment), I get a CTD on the battle loading screen.

  15. #15
    wudang_clown's Avatar Fire Is Inspirational
    Join Date
    Jan 2009
    Location
    Poland
    Posts
    7,357

    Default Re: CTD's on sieges (Steam)

    I can't confirm this as general problem - I've just checked sieges, attacked Muscat with an army equipped with catapults and it worked fine.

    I think your problem has its source in your modification of M2TW. You could easily miss a file here or there.

    But post content of your M2TW system.log. There should be a trace of the error.

    Under the patronage of m_1512

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •