Each cas file has a texture assigned to it and if the cas file cannot find this texture in the entry using the cas file it will crash. This can be resolved by checking that the all the textures mentioned in the 'data\descr_model_strat.txt' file are in the 'data\models_strat\textures'.Ģ) The cas file's texture is not present in an entry in the 'data\descr_model_strat.txt' file (such as 'northern_general' or 'islamic_merchant'). The logs say you lack enough vRAM.Ī: There are two possible causes for this.ġ) A texture for a campaign (strategy) map unit cannot be found. Q: When you start the mod you get a black screen and the mod CTDs. The only problem with changing this number is that if it is set to a number higher than the number of units in the mod it will cause a crash.
If the error is in the first 500 entries M2TW will still CTD.īy changing the number it is possible to find the exact entry that is causing the problem (though you'll need to use KnightErrant's checking program to find out which unit this is). If the error is not in the first 500 the mod will load to the splash screen (though it is likely to crash for other reasons). It you change it from 985 to 500 M2TW will only check the first 500 entries before starting the mod. For the remaining errors the easiest way to find them is to edit the number in the battle_models.modeldb highlighted below in red.Ĭode: 22 serialization::archive 3 0 0 0 0 985 0 0This number tells M2TW how many entries there are in this file. The easiest way to check this file is to use the 'formatted_modeldb_version2' by 'KnightErrant' here:įirst format the battle_models.modeldb, then use the checking program. You won't recieve any help in the log for this so you'll have to check your entries manually. Q: When you start the mod you get a black screen and the mod CTDs.Ī: There is an erronous entry in the data\unit_models\battle_models.modeldb, normally a reference to an non-existant mesh or texture, or an entry is incorrect.
If this fixes the problem then you know this file is faulty. If you think a file is causing problem change its name and see if this fixes the problem (if M2TW can't find a file it reverts to the default version). Though some errors are recorded part way through the error log such as a missing skeleton, a missing mount, and a building gap.
The error is usually at the bottom of the error log as they're the last thing it records before it crashes. Level=*script* trace This will give you a log report which contains the most information about the crash, though it's hard to read.Īlways check the error log in the 'Medieval II Total War\logs' folder to find out which file is causing problems (default location 'C:\Program Files\SEGA\Medieval II Total War\logs').
0 kommentar(er)
