Once and for All
Thread: Once and for All
-
Ordnance said:
September 26, 2011 02:27 AM
Once and for All
Ok, I'm sure you all are tired to death with these endless questions on how to make your varies additions to this wonderful mod work. I, unfortunatly am in need of assistance as well.
Here it is. I have been trying to get this working for the better part of three days and have combed both this site and many others tracking down varies bugs and potential fixes but my own limited knowledge of modding doesn't allow me to do much more than follow the fixes I find here and there. Basically I am running into a few problems.
1. Even after a completely clean wipe and re-install of the game and mod if I run 1.4 (The last version I got this to work on) I get the "Cannot find Kingdoms.exe". Although not my main problem it prevents me from seeing a workable version of this and working forward.
2. using Gigantus' installer I correctly installed the game via the guidlines provided but still managed to encounter the "fatal Error" message. In addition, after installing CoW none of my Kingdoms mods were working (Americas, Teutonic etc). You could enter the game but when it came time for the main menu I would either get the "fatal error" or simply a ctd blank box and button.
I made sure that everything I installed was pointed at C:\ProgramFiles(x86)\Steam\SteamApps\common\medieval ii total war. Verified that any and all references too mod/Call_of_Warhammer were properly underscored and one file name; got Kingdoms installer app, varified that that had everything correctly spelled and was pointing at the right .EXEs. Doubled checked by completely wiping all data from my comp (a fairly meticulous wipe) and re-installing it all several times. I both disabled UAC and for redundancy, made all files involved run as admin.
I have proporly installed, updated, patched my steam version of MTW and MTWK. I made sure to test them before initiating the modding, they worked perfectly fine. I am really at a lose as to how to proceed.
Im hoping to get a step by step from a clean, working MTW and MTWK to a completly installed and up to date CoW (Including Gigantus' installer and subsequent patches).
I mean if we got it to work on my comp, this thread could get it to work on anybodies'.
-
Gigantus said:
September 26, 2011 08:14 AM
Re: Once and for All
One last step: How To Fix UAC and VirtualStore Problems start at step 3 and don't forget to delete the virtualstore for m2tw
Summary
- Execute VirtualStore Fix
- Delete present CoW installation
- Restart computer to clear memory (registry entries)
- Install my version as per recommendation of the Creating a World - Mod Install for Steam instructions
- Update the language installer (link in first post)
- Install the patches in the second post
- Cross fingers and start
-
Ordnance said:
September 26, 2011 01:09 PM
Re: Once and for All
Well I followed all the instructions listed and I still received the fatal error under the cab lib window, if that means anything. But there was a bit of progress I guess in that it did not break my Kingdoms game this time. If you guys think of anything else that could be messing with my install I am will to spend as much time getting this working as is necessary.
Edit #1. For giggles I repeated the same steps above on a brand new install from steam on my friend's computer. he has no previous versions of this nor any mods in general and got the same exact error. And I took it step by step according to the list above.
Edit #2. I also went ahead and tried TATW 2.1 and received the same exact error. I would assume that means that it is a result of my steam version of the game. I have Kingdoms launcher app current version. so if there is any other work-arounds for the steam version I would be very interested in knowing them.
Last edited by Ordnance; September 26, 2011 at 09:11 PM.
-
Gigantus said:
September 27, 2011 12:00 AM
Re: Once and for All
Please take a screenshot of your browser with the Call_of_Warhammer directory open (example pic attached). The ad_lib error is usually indicating a wrong install of the mod.