Total War: MEDIEVAL II - Definitive Edition

Total War: MEDIEVAL II - Definitive Edition

Kel'Thuzad Feb 26, 2017 @ 12:18pm
Unpacker error..?
When I attempt to unpack the game files for editing and whatnot, it fails with a prompt that a file called "MSVC71.dll is missing. Please re-install blah blah"..

I certainly don't want to re-download a 10GB game when it may not even resolve the issue.

Is there any way around this? If not I may as well go back to using my CD version... FU Steam.
< >
Showing 1-15 of 29 comments
HazardHawk Feb 26, 2017 @ 4:14pm 
Unless you are planning on modding, why are you unpacking? THEN, if you are planning on modding, if you have Windows 10, it will not allow a full unpack due to permissions errors even if you are running the unpacker as administrator.

I just went through the trouble of installing XP X64 and personally writing all the drivers I needed just to be able to work on my own mod because of that.
MSVC71.dll that will be added by steam would be my guess,and probably not needed
Kel'Thuzad Feb 26, 2017 @ 4:39pm 
I found a solution online to copy the files from the base M2TW folder into the unpacker folder, but now the unpacker just crashes after hitting "Y" (yes) to the initial warnings.

I dont really intent to do any modding beyond fixing the bug that prevents occupying settlements from giving you the appropriate boost to reputation.

If it's a Win 10 issue then I guess going back to the CD's won't work either.
HazardHawk Feb 26, 2017 @ 5:04pm 
You can try moving your Medieval folder complete to another location on the same hard drive. Leave the file structure intact. Run the unpacker as administrator. Once unpacked, drag and drop it back where it is supposed to be. Another hard drive is even better. An old PC with windows XP best.

With Microsoft's war on Steam and Steam games and then adding in drivers no longer really support directX 9 along with most computers anymore are coming with Intel CPUs with onboard HD and AMD APUs Medieval 2 is going to die in the next few years because it wont be playable without going through hoops. Rome just barely made it through to Windows 10 and was slated to be blacklisted.
Gigantus Feb 26, 2017 @ 6:25pm 
Use the method from my tutorial - it provides batch files that will pause once they have finished so you can analyze\see what error happened: http://www.twcenter.net/forums/showthread.php?t=550619

You do need to press Y three times, if it still fails then provide the full error message.
Last edited by Gigantus; Feb 26, 2017 @ 6:31pm
Gigantus Feb 26, 2017 @ 7:16pm 
Something went wrong with the copying of the link, it actually uses those dots instead of the full address: albums/k2...ackerError.png

In your photbucket album click the picture and then from the three links on the right side select the 'direct' one - simply click on it to copy the link then paste it here.
Kel'Thuzad Feb 26, 2017 @ 7:47pm 
My bad

http://s91.photobucket.com/user/Manu_Forti/media/UnpackerError_1.png.html

It looks like theres more if I could scroll down, but it closes a millisecond after I hit "Y". I was lucky to screenshot even that much.
But it does say FAILED right at the very beginning
Last edited by Kel'Thuzad; Feb 26, 2017 @ 7:53pm
Gigantus Feb 26, 2017 @ 7:57pm 
Yup - that doesn't help. Use the batch files from my tutorial I linked in post #5. They will pause before exiting. And will unpack outside the game's installation. Please read the info and follow the instructions given.

Tip: when copying links do not highlight and 'simple copy' - right click the link and choose 'copy link location'

Originally posted by HazardHawk:
Unless you are planning on modding, why are you unpacking? THEN, if you are planning on modding, if you have Windows 10, it will not allow a full unpack due to permissions errors even if you are running the unpacker as administrator.

I just went through the trouble of installing XP X64 and personally writing all the drivers I needed just to be able to work on my own mod because of that.

I just successfully unpacked the americas campaign in win10 using my method. The success may have to do with unpacking OUTSIDE the game's folder:
Extracting file 8401 of 8401 Source: blabla/descr_faction_movies.xml Destination: blabla/descr_faction_movies.xml Size 2282 Successfully extracted all pack files Ok. Press any key to continue...
Last edited by Gigantus; Feb 26, 2017 @ 8:09pm
HazardHawk Feb 26, 2017 @ 8:24pm 
Cool. Just finished getting my beast reassembled. Windows 10 gave me a scare because it would not allow me to reactivate, google was useless, Microsoft doesnt work 24/7 anymore, so I got crazy and tried changing my key to my original Windows 8 key and it was suddenly activated. Ha!

Then I discover my R290x is useless in Ubuntu and steam wont run without the Catalyst driver... Been a weekend it has...
As Gigantus basically said, running the unpacker does nothing. You need to shove some text into the unpacker to get it to do anything; you can either write these yourself (not hard at all) or download Giganto bat files; which is unreliable as they are off the internet but the nice thing about batch files is you can right-click EDIT them to see everything that they do before running them.

Spot the Latin pun
Kel'Thuzad Feb 26, 2017 @ 9:10pm 
Your tutorial is honestly pretty confusing :steamsad:

1/ I don't want it to unpack to C drive (lack of space). Will it do that automatically?
2/ I tried to save it under D: drive but it downloaded itself into the 'data' folder of my M2TW directory on D: .. Your guide seems to suggest it should be in the unpacker folder(?)
3/ Do I unzip the download?.. Do I unzip the zip within that zip?.. And to where? Should these replace the default files in M2TW unpacker folder?
4/ You talk about editing the BAT files.. but edit them how?
Last edited by Kel'Thuzad; Feb 26, 2017 @ 9:18pm
Gigantus Feb 26, 2017 @ 9:29pm 
1. My batch files will automatically unpack to C:\Unpack, you can change that by replacing that part with a designation of your own. The default path extension starts with data, eg it would unpack into C:\Unpack\data for the main game. C:\Unpack\mods\[campaign name]\data for the campaigns.
2. Did you actually save your changes?
3. The instruction says to unpack the download into the tools\unpacker directory - I will change the download to a simple zip affair, although it would be logical to unzip the batch zip file into there as well. Probably forgot to alter the instruction after adding the PDF file.
4. there is a bold section titled: "editing of BAT files' in my tutorial


Edit: I edited my download to make it a one time unzip. Still has to be unpacked into the tools\unpacker directory.
Last edited by Gigantus; Feb 26, 2017 @ 9:44pm
Kel'Thuzad Feb 26, 2017 @ 9:46pm 
Originally posted by Gigantus:
1. My batch files will automatically unpack to C:\Unpack, you can change that by replacing that part with a designation of your own. The default path extensionstarts with data, eg it would unpack into C:\Unpack\data for the main game. C:\Unpack\mods\[campaign name\data for the campaigns.
2. Did you actually save your changes?
3. the instruction says to unpack the download into the tools\unpacker directory - I will change the download to a simple zip affair, although it would be logical to unzip the batch zip file into there as well. Probably forgot to alter the instruction after adding the PDF file.
4. there is a bold section titled: "editing of BAT files' in my tutorial


Edit: I edited my download to make it a one time unzip. Still has to be unpacked into the tools\unpacker directory.
So the BAT files go directly into the tools/unpacker folder? Or stay in your 'unpacker files' subfolder? (so as not to conflict with the default unpacker files.

I've edited the unpack_all one to direct the files to D:/Unpack
Gigantus Feb 26, 2017 @ 9:52pm 
They go into the unpacker directory and will not interfere as they are differently named, they have got a 'Unpack' suffix (the new download will now unpack all files directly into the folder)

To unpack to D simply edit (rightclick, edit - remember?) the unpack_all_Unpack batch file. This is the original main entry in there:
unpacker.exe --source=..\..\packs\*.pack --destination=C:\Unpack --verbosity=1

Change it to:
unpacker.exe --source=..\..\packs\*.pack --destination=D:\Unpack --verbosity=1

I just ran a test by unpacking into my F drive and had no problems.
Last edited by Gigantus; Feb 26, 2017 @ 9:55pm
< >
Showing 1-15 of 29 comments
Per page: 1530 50

Date Posted: Feb 26, 2017 @ 12:18pm
Posts: 29