crash problem

[KukriKhan]

Hello ucla_vince, welcome to the Org

I once had a similar, but different problem with S:TW; whenever the game went to one of the cut-scenes, crash to desktop. Turned out my Win Media Player had some corrupted files (one of which Shogun apparently needed). I uninstalled, then reinstalled it - on advice from the guys here. Problem fixed.

Your problem sounds different. If no tech-guy pokes his head in here in 24 hours, we'll cross-post your post to the Apothecary (tech forum).

[Tomcat]

A couple of the set battles always crash at the same point but there is a fix for this, see:
http://p223.ezboard.com/fshoguntotal...cID=4994.topic

Otherwise, make sure your video and sound card drivers are up to date as these are usually the problem. Visit the respective hardware manufacturers' sites for these. Windows media player, as already mentioned, can also be a problem.

Please post your full computer specs if none of the above solve the problem for you.

Tomcat

[Kraellin]

i also recall that in mtw there was a problem with corrupted campaigns. once the campaign file was corrupted, it couldnt be fixed and would crash at the same point every time thereafter. i forget if stw had this problem too (it's been a while), but you might try starting a new campaign and see if that works ok.

also, if Red Harvest shows up here to post, i'm sure he'll tell you to never save the game right before the end of your turn and to always save right when your turn comes up to play. i never had this problem, but he swears by it.

K.

[Red Harvest]

Yep, K beat me to it.

One thing I remember happening in STW/MI was a bug with assassins. If I killed a general in battle when he was targeted by an assassin, trying to move the assassin on thefollowing turn would cause an immediate CTD on the strategic map. (Apparently he couldn't accept the dishonor of failing to kill the already dead general, so he terminated the program instead--virtual seppeku.) If I left him alone for a turn, all was fine and his honor was intact. I believe this was fixed in the final patch though. I vaguely recall trying to cause the CTD after the final patch and couldn't get it to do it anymore (whereas it was a 100% repeatable CTD before that.)