Results 1 to 19 of 19

Thread: CTD on start of battle

Hybrid View

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

    Default CTD on start of battle

    I am running Windows 7 and have Steam. I disabled UAC, I installed 6.3 and 6.4 into the correct folder (the main MTW2 folder under the Steam directory), I don't have the automatic DST enabled on my system clock, I made sure that the battle screen resolution is equal to my desktop resolution and I am running the game as Administrator. I have no other mods or sub-mods installed.

    Everything about the game runs fine except when I try to start a battle. As soon as it starts loading the battle screen, I get a CTD. My system.log file only contains the following info:

    15:53:41.753 [system.rpt] [always] CPU: SSE2
    15:53:41.753 [system.rpt] [always] ==== system log start, build date: Feb 25 2008 version development ===
    15:53:41.757 [system.io] [always] mounted pack packs/data_0.pack
    15:53:41.757 [system.io] [always] mounted pack packs/data_1.pack
    15:53:41.758 [system.io] [always] mounted pack packs/data_2.pack
    15:53:41.759 [system.io] [always] mounted pack packs/data_3.pack
    15:53:41.759 [system.io] [always] mounted pack packs/data_4.pack
    15:53:41.759 [system.io] [always] mounted pack packs/localized.pack
    15:55:05.491 [system.rpt] [error] Medieval 2: Total War encountered an unspecified error and will now exit.

    Thanks

  2. #2

    Default Re: CTD on start of battle

    I have Kingdoms 1.5

  3. #3
    Navajo Joe's Avatar SS Forum Moderator
    Join Date
    May 2008
    Location
    England
    Posts
    4,182

    Default Re: CTD on start of battle

    You might want to go to Sub Mods, d/l and install Germanicu5 RBAI, should fix your problem





    'Proud to be patronised by cedric37(My Father and My Guardian)

  4. #4

    Default Re: CTD on start of battle

    I keep trying to reply to you with a question about where to install the mod, but I keep getting a message that my post is denied but I have no idea why, I've reworded this reply in the hopes it will somehow magically fix the problem.

  5. #5

    Default Re: CTD on start of battle

    I think I got it figured out. I installed the Germanicu5 RBAI sub-mod into the main M2TW folder, ran the setup for the sub-mod and clicked the check box for Stainless Steel then re-ran the Stainless Steel setp program and checked the box for "G5 Emergency Battle CTD Fix". I ran M2TW again, but the same crash still happened. This time the system.log file only contained one line:

    19:04:35.283 [system.rpt] [always] CPU: SSE2

  6. #6
    Tiro
    Join Date
    May 2007
    Location
    England/Hungary
    Posts
    202

    Default Re: CTD on start of battle

    Quote Originally Posted by vbidez View Post
    I think I got it figured out. I installed the Germanicu5 RBAI sub-mod into the main M2TW folder, ran the setup for the sub-mod and clicked the check box for Stainless Steel then re-ran the Stainless Steel setp program and checked the box for "G5 Emergency Battle CTD Fix". I ran M2TW again, but the same crash still happened. This time the system.log file only contained one line:

    19:04:35.283 [system.rpt] [always] CPU: SSE2
    I get exactly the same as this now also, have tried reinstalling and everything!! Curse you windows 8!!!!

  7. #7
    Navajo Joe's Avatar SS Forum Moderator
    Join Date
    May 2008
    Location
    England
    Posts
    4,182

    Default Re: CTD on start of battle

    Is this your first battle or not?





    'Proud to be patronised by cedric37(My Father and My Guardian)

  8. #8

    Default Re: CTD on start of battle

    Quote Originally Posted by Navajo Joe View Post
    Is this your first battle or not?
    Yes, it is the first time I try to enter a battle in a game.

  9. #9

    Default Re: CTD on start of battle

    im having same problems??

    Spoiler Alert, click show to read: 
    16:41:58.685 [system.rpt] [always] CPU: SSE2
    16:41:58.685 [system.rpt] [always] ==== system log start, build date: Aug 3 2007 version bld-medieval2-kingdoms-104 (45562) ===
    16:41:58.763 [system.io] [always] mounted pack packs/data_0.pack
    16:41:58.779 [system.io] [always] mounted pack packs/data_1.pack
    16:41:58.810 [system.io] [always] mounted pack packs/data_2.pack
    16:41:58.857 [system.io] [always] mounted pack packs/data_3.pack
    16:41:58.904 [system.io] [always] mounted pack packs/data_4.pack
    16:41:58.951 [system.io] [always] mounted pack packs/localized.pack
    16:43:55.753 [game.script] [error] Trigger processing error in <SizeSet1End>
    : PercentageUnitAttribute needs a living character with an army.

  10. #10
    Navajo Joe's Avatar SS Forum Moderator
    Join Date
    May 2008
    Location
    England
    Posts
    4,182

    Default Re: CTD on start of battle

    That sadly looks like a bad install, I would recommend delete SS, re-install, make sure your UAC is disabled





    'Proud to be patronised by cedric37(My Father and My Guardian)

  11. #11

    Default Re: CTD on start of battle

    I uninstalled everything, including M2TW and Kingdoms. I double checked that UAC was off, which it was. I did a full re-install of M2TW and Kingdoms.

    I then ran the 6.3 setup program as Administrator and pointed it to the main M2TW directory "C:\Program Files (x86)\Steam\SteamApps\common\Medieval II Total War". The install program automatically added a 6.3 sub-folder onto the end of that install path. I waited for the install to be completed, I clicked "Early Era Campaign", checked the boxes for "Savage AI", "Longer Assimilation" and "Permanent Watchtowers" then hit OK. When it was done, the install program again asked me to point it to the M2TW folder. I pointed it back to "C:\Program Files (x86)\Steam\SteamApps\common\Medieval II Total War". A message popped up about Steam being detected, I hit OK. Stainless Steel 6.3 then launched and loaded normally. I then exited the program.

    I then ran the 6.4 install program as Administrator. I pointed it to the 6.3 install path "C:\Program Files (x86)\Steam\SteamApps\common\Medieval II Total War\6.3". It finished and took me to the setup program. I clicked the "Campaigns" button and the "Early Era Campaign" button, I checked the boxes for "Savage AI", "Longer Assimilation" and "Permanent Watchtowers" and clicked OK. I then clicked the button "Start and Exit". Again, I got a pop-up box saying that Steam was detected, I clicked the "Yes" button saying that I had the Steam version of Kingdoms. I then got a pop-up message saying that the launcher could not locate kingdoms.exe and that I should run the launcher again to point it to the right path. I clicked "OK" and then ran the 6.4 launcher as Administrator. It asked me to point it to the M2TW folder, so I pointed it again to "C:\Program Files (x86)\Steam\SteamApps\common\Medieval II Total War" Stainless Steel 6.4 then launched normally. I went to the video settings and made sure that the resolution for the battle screen is the same as my desktop resolution and then exited the program.

    I then ran the install program for the RBAI sub-mod as Administrator. I checked the box for "RBAI for Stainless Steel" and clicked "Next". I pointed the install path to "C:\Program Files (x86)\Steam\SteamApps\common\Medieval II Total War". I got a pop-up box about Stainless Steel being detected and I clicked "OK" I then clicked the "Finish" button, and the RBAI setup program ran bringing up a G5 setup screen. I clicked the Stainless Steel 6.3 button and clicked the box for "Use Stainless Steel Setup" and clicked "OK". I then exited the G5 setup screen.

    I then ran the Stainless Steel Setup program, clicked the "Campaigns" button and the "Early Era Campaign" button. I checked the boxes for "Savage AI", "Longer Assimilation", "Permanent Watchtowers" and "G5 Emergency Battle CTD Fix". I clicked "OK" and then "Start and Exit". Stainless Steel 6.4 loaded normally, I started a campaign game, it loaded normally, I started a battle and when the battle map was loading, it crashed. However this time, the crash was slightly different, I didn't get the "unspecified error" message like before and this time the system.log file only contained the one line "16:45:53.421 [system.rpt] [always] CPU: SSE2".

    So what am I doing wrong?

    Thanks

  12. #12
    Navajo Joe's Avatar SS Forum Moderator
    Join Date
    May 2008
    Location
    England
    Posts
    4,182

    Default Re: CTD on start of battle

    How many Steam Directories do you have?





    'Proud to be patronised by cedric37(My Father and My Guardian)

  13. #13

    Default Re: CTD on start of battle

    Just the one, ""C:\Program Files (x86)\Steam". Now I'm wondering if maybe I should delete the 6.3 sub-path that is automatically added by the Stainless Steel install program and install it directly into the main M2TW directory.

  14. #14

    Default Re: CTD on start of battle

    Quote Originally Posted by vbidez View Post
    Just the one, ""C:\Program Files (x86)\Steam". Now I'm wondering if maybe I should delete the 6.3 sub-path that is automatically added by the Stainless Steel install program and install it directly into the main M2TW directory.
    I tried not using the sub-folder, it didn't work, it just caused the mod not to run at all.

  15. #15

    Default Re: CTD on start of battle

    Do you think it would fix the problem if I just downloaded ISOs for the original SEGA versions of the games instead of installing the Steam versions of the games?

  16. #16
    Tiro
    Join Date
    May 2007
    Location
    England/Hungary
    Posts
    202

    Default Re: CTD on start of battle

    Quote Originally Posted by vbidez View Post
    Do you think it would fix the problem if I just downloaded ISOs for the original SEGA versions of the games instead of installing the Steam versions of the games?
    I don't think Steam is the issue, I have the same problem as you and I have the CD's for the game.

  17. #17
    valky's Avatar Ducenarius
    Join Date
    Dec 2009
    Location
    Germany
    Posts
    967

    Default Re: CTD on start of battle

    Seems quite popular to crash while loading the battle after some time or several battles. Tried Germanicu5 RBAI too, but it didn't really help. (still the BAI is slightly better..)
    Though I checked the memory, which the game uses and it is only limited to 32bit range (or it won't use more than ~1GB RAM). Had the same problem with DAO:ultimate specially if modded. Good ol' total war games usually crash, if no memory can further addressed

    Yet there is a tiny lil' program, which can fix that problem - and at least for me the crashes went down. Just in case: http://www.ntcore.com/exsuite.php

    Install & open kingdom.exe and/or medieval2.exe (make a backup ^^) .. navigate to 'NT Headers' / ' File Header' click on 'click here' (d00h) at characteristics. Check 'App can handle >2GB adress space' .. save.
    Worked for me as I usually got a CTD after 2-3 battles (including reloades)...
    Maybe it helps, can't imagine a fresh install or anything else is at fault. In my case it is a fresh install with only Stainless Steel.
    I'm Commander Shepard and this is my favourite store on the Citadel!
    I'm Garrus Vakarian and this is now my favourite spot on the Citadel!

    Better ingame Encyclopedia for Shogun 2 (reworked) - RotS - FotS (new map) + web-based version

  18. #18

    Default Re: CTD on start of battle

    Thanks for the suggestion, I tried it out and the CTD still happens. But thanks again for the help.

  19. #19
    Tiro
    Join Date
    May 2007
    Location
    England/Hungary
    Posts
    202

    Default Re: CTD on start of battle

    Quote Originally Posted by vbidez View Post
    Thanks for the suggestion, I tried it out and the CTD still happens. But thanks again for the help.
    Just wondering what patch version you are running on MTWII? I had exactly the same problem then realised my vanilla game was unpatched. I patched it to version 1.3 and the crash no longer happens!

Posting Permissions

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