-
April 19, 2014, 05:30 AM
#1
Foederatus
6.4 still CTD on start up even after doing multiple "fixes".
So I decided to give Medieval 2 a go again recently since I have not played it in many years and I have never used any mods for it. I install it and Kingdoms through Steam. I find the SS6.3 and SS6.4 download links here on TWCenter forums and start to download. While waiting on download to finish I play Medieval 2 a bit, so it should be noted that Medieval 2 worked fine, even though UAC was not disabled and I have Windows 7.
-
April 19, 2014, 05:31 AM
#2
Foederatus
Re: 6.4 still CTD on start up even after doing multiple "fixes".
I installed SS6.3, running the setup as administrator. It launched just fine after the setup, so I exited it and started the SS6.4 setup as administrator. SS6.4 also installed fine and started up fine. It played absolutely wonderfully and had no problem during multiple launches.
Well I decided to give Late Era a try. I made the mistake of misreading and I did the entire 6.4 install again instead of just running ss_setup. Not a big deal since installing over itself really should have caused no issues, especially since it automatically runs ss_setup afterwards. Well SS6.4 keeps CTDing after being at the title screen for about 1 second.
So after reading a few threads I uninstalled Medieval 2 and Kingdoms completely, then disabled UAC and restarted my computer. I installed Medieval 2 and Kingdoms again and tested it to make sure it was working fine, and it was, perfectly. So then I ran SS6.3 as administrator which installed perfectly and also launched and ran perfectly. Then installed SS6.4 as administrator and then was back at CTDing at the title screen.
I also tried doing the fix and reinstall suggested in the "Solving-problems-with-Steam-Vista-or-Windows-7" thread for Steam users. It just does the same thing, CTD at title screen.
What I do not understand is why SS6.4 worked perfectly before, even with having UAC enabled and not running the setups as administrator, then CTDing at the title screen after running SS6.4 install again to change to Late Era (mistakenly, I now realize that only running ss_setup is sufficient). Also I don't understand why I can not get SS6.4 to run again at all, even with these multiple fixes, when not only Medieval 2 still runs perfectly, but Kingdoms, and SS6.3 as well.
I really love Stainless Steel, I think it is the best complete overhaul mod I have ever played for TW game, and I have played and own just about every TW title extensively including the two most recent Shogun 2 and Rome 2. I thank everyone for their hard work, now I just ask for help to get this wonderful mod running again 
I had to post this in two seperate post because the forums was telling me that I contained "too many URLs" or "censored words" ??
-
April 19, 2014, 08:14 AM
#3
Re: 6.4 still CTD on start up even after doing multiple "fixes".
The UAC wont be a problem for vanilla M2, the issue is exclusive to mods and specially those with swaping file programs like the SS_setup.exe.
IMO the best course of action is just installing M2+kingdoms somewhere else outside of "Program Files", then I think you don't even need to worry if UAC its disabled or not.
If all that fails then is most likely that your 6.4 installer got corrupted, just download it again.
-
April 19, 2014, 08:34 AM
#4
Foederatus
Re: 6.4 still CTD on start up even after doing multiple "fixes".
It seems I am an idiot.
After trying for the third time I realized that the instal directory of the mods was going to C:\Program Files (x86)\SEGA\Medieval II Total War\mods\SS6.3 instead of the Steam directory.
Having a photographic memory allows me to see things in just a glance, but this also caused me to glance at the beginning of the directory and see: C:\Program Files (x86)\S......... and glance at the end and see ...........mods\SS6.3 and think it was okay. 
After reinstalling the mods to correct directory it worked perfectly fine. Now I am going to test to see if it will still work fine with UAC enabled. No need to clog up the board with this thread any longer so if a mod could delete (or close and archive if you don't delete) this thread.
I am glad I did not waste a bunch of people's time, figuring this out. Thanks to Melooo182 for responding.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules