battle_models.modeldb

[Tyre]

Is there a unit limit? Currently I'm at 879 but get a ctd if I ad any more entries, yet I've seen mods with higher.

[Gigantus]

The logical conclusion would be an error in your modeldb. Are you using the modelDB checker?

[Mythic_Commodore]

There is no limit. I am at 1300 and am still adding new models.

[SigniferOne]

I am at 239. It is a good feeling to clean the file of extraneous foreign entries, and populate it exclusively with your own.

[Tyre]

I wonder why I can't add any more. I know it's not a typo because if I copy a unit and simply change one letter in the name and add +1 to the archive I crash. or I've had other strange symptoms like the last unit in my battle_models.modeldb being invisible on the battle map until I remove an entry then they show up again.

I can't run the tester because python is very finicky on Vista and only works with some aps.

[Caesar Clivus]

I wonder why I can't add any more. I know it's not a typo because if I copy a unit and simply change one letter in the name and add +1 to the archive I crash. or I've had other strange symptoms like the last unit in my battle_models.modeldb being invisible on the battle map until I remove an entry then they show up again.

That's a symptom of having an incorrect serialization count. If the serialization number is too low, then the game will not look past that number of model entries, making anything past that invisible to the game which thinks they dont exist. If the serialization number is too high, then the game will crash because it cant find the specified number of model entries.

[absinthia]

I wonder why I can't add any more. I know it's not a typo because if I copy a unit and simply change one letter in the name and add +1 to the archive I crash. or I've had other strange symptoms like the last unit in my battle_models.modeldb being invisible on the battle map until I remove an entry then they show up again.

are you sure you copy the complete entry?

[Gigantus]

The tester doesn't run with python 3.1. Had to uninstall and go back to python 2.6

[Tyre]

That's a symptom of having an incorrect serialization count. If the serialization number is too low, then the game will not look past that number of model entries, making anything past that invisible to the game which thinks they dont exist. If the serialization number is too high, then the game will crash because it cant find the specified number of model entries.

Yeah that's what I figured but everything currently runs fine unless I try to add a unit. If my count is off wouldn't I be having issues?

[Caesar Clivus]

Yeah that's what I figured but everything currently runs fine unless I try to add a unit. If my count is off wouldn't I be having issues?

If your count is already too low, then the game won't crash but the last unit (or units) in the modeldb will be invisible...which is what you described as happening.

[Tyre]

The tester doesn't run with python 3.1. Had to uninstall and go back to python 2.6

It generates a blank text file. Does that mean I have no errors?

[Mythic_Commodore]

I have that error too. Try adding new models into the middle, rather than the end of the file. Be sure to still remember to change the serialization number.

[Tyre]

I have that error too. Try adding new models into the middle, rather than the end of the file. Be sure to still remember to change the serialization number.

Good call! that did the trick. Thanks mate

[Taiji]

I've never had a problem adding units to the end of the list personally

[Augustus Lucifer]

This file is the devil, it's really that simple. I've added something and then had someone else add the same exact thing and it worked for them, and me when they sent me the file(identical in WinMerge), but didn't work for me initially. Lord only knows what it'd be like without the formatted version.

[Taiji]

I agree that it's demonically inspired but I've found that as long as I don't do exactly the same thing I did last time it usually works.

I'm never any the wiser about why it didn't work in the first place though...

[SigniferOne]

Yes -- it only looks demonically inspired when things work or don't work from random causes, and crashes happen on a completely trustful patch of code.

I, however, have not had anything random happen with it for years. Me and the file have become good friends. As long as I do the same things over and over again, as long as I always check it with the syntax-checker afterwards, the file smiles and bequeathes benevolence upon me...

All of which is to say that there is no randomness and bugginess in the way the game processes that file. Any of the random errors all belong merely on the human side.

[Tyre]

I don't have that luxury as python refuses to work on my system

[SigniferOne]

Just uninstall 3.1 and revert back to the 2.6 version, simple as that!

[Tyre]

Tried that already, same nonsense.