Ive installed the first 3 of 4 sections of the expansion, and it froze when I put in the second CD. I tried the first 3 that I installed and they worked just fine.
Any tips?
Ive installed the first 3 of 4 sections of the expansion, and it froze when I put in the second CD. I tried the first 3 that I installed and they worked just fine.
Any tips?
I did that, it worked. Now I'm having trouble with actually running the mod. It seems to crash during the loading time when I chose which faction I want to play the Grand Campaign.
Only way to find out is through the log file (if it wasn't the 'unexpected error' CTD). The default log file is set to 'trace', to change that, copy the following into your cfg file:
You should then get a more comprehensible file in the logs folder.Code:[log] to = logs/PDER.system.log.txt level = * error
Yes, although I didn't do anything with it. Just read it, but it doesn't apply because Im playing english versions.
According to the second quote are not playing the English version (or it has been modded with German text files). Try the remedy or re-install completely (clean install). I know it is a b...h, but it's the only way.I bought the game and the expansion in New York City. Why in the hell is it in German/Dutch?
I think Mikel is having the same problem as me loading PDER Kingdoms. I installed the Stainless Steel v.5 mod which has a bug with some texts in German.
Could this be causing PDER not to run ?
There s a patch for SS 5 any day now. I ll try n reinstall PDER when that comes out.
Last edited by Jihada; November 07, 2007 at 10:56 PM.
By the looks of it I would say that SS is installing some files into the M2TW\data folder like the strat and tooltips text files. These should be in the \mods\ss\data folder. The modders need to sort that out, it is the left over from the pre-kings era which they didn't port.
And that will most likely be the reason for the mess.
Well I installed the SS Mod v5.0 after I stopped tyring to play the PDER Mod.
Im going to uninstall SS now and see what happens with PDER.
Tried it. Didn't work. Don't like SS Mod. Bought Kingdoms for nothing...![]()
Tried the link for the sound files, it didn't work..should I post my log file for PDER?
Mikel, you have been doing such a lot of things with your installation that I would think a complete uninstall (even delete the left overs manually after the regular uninstall) is the only solution to sort out the mess.
Then re-install as follows:
- M2TW
- Kingdoms
- PDER Kingdoms
Please follow the instructions that come with PDER Kingdoms exactly as they are written.
At any other moment, I'd agree with you 100%, but I already did that when I deleted everything manually and used a saved fresh install from my external HD. Unless that copy was corrupted as well, I have no idea what the hell is going on.
Saved fresh install from external HD? Does that mean you copy the installation from the external drive and do not use the installation program?
You might be asking for problems as the installation program writes to your registry, which will not happen with a simple copying.
Simply humor me and do a complete uninstall and fresh install as mentioned in my previous post.
If you want, post the log file, provided you changed the logging to error (see the other post of mine).
By the way, you are double\cross posting with this problem, making it difficult to give coherent advice. Stick to one thread - best this one.
Yeah, I was.
And Im currently re-installing M2TW. I'll save installing Kingdoms for tonight after I'm finished with my day.
And what exactly is the posting the log file supposed to do?
The default log file is designed to give developers a closer and more detailed look at possible mistakes. It is called a trace log.
For our purposes this is way to convoluted, all we need are the errors that cause the crash. For that you reduce the details of the log aptly to 'error' level. Add the following lines to your cfg file:
The first line indicates the 'chapter' of your cfg file. Other are [video] and so on.Code:[log] to = logs/PDER.system.log.txt level = * error
The second line indicates the name (PDER.system.log.txt) of the file and the location (M2TW\data).
The third line indicates the report level. Error = minimal, critical errors only. Trace = all errors.
A little tip: the game will reset the cfg file every time you play, it might therefore be a good idea to make it readonly after the above addition.
As long as you don't have a CTD with our favorite little error message (unspecified error) we should be able to take a good guess what was wrong. The error messages can range from the obvious (file missing) to the obscure (cannot create settlement). Without this logfile a lot of modders would already have committed suicide, that's how important it is.
Thanks bro, its working now.
+Rep this man!