For anyone who has added units to 3.0 and Barons

[orclover]

Is there anything specific I need to do to the campaign script when I add a unit, i have added tons of units in the past but I get a CTD when entering isengard in battle every time with a new unit. Vanilla units are fine. The error points me to the campaign script. The new units are fine everywhere else on the map, just seems Isengard poses some problems. Thanks

[Mhaedros]

Adding units has nothing to do with campaign_script. Have you messed with anything else? I've added units to Barons submod myself without any CTD:s

[orclover]

Mhaedros, can you attempt to siege Isengard with one of your new units for me, see if there is a CTD? Thanks

[Mhaedros]

Sure, I'll try

EDIT: I tried, and everything worked fine

[Louis Lux]

A ctd before entering battle normally points to the game not finding the model or textures, you have to make sure the files are there and that you pointed them out correctly in the modeldb.

[orclover]

thanks... the units that are causing the CTD work in field battles and in other sieges of rebel settlements for example... seems exclusively related to Isengard or custom settlements

[Mhaedros]

What kind of problem? Have you added everything in battle_models.modeldb? And counted the letters correctly?

[orclover]

the units work in custom battle and in game, they CTD at isengard, except not all my new ones do. Seems inconsistent to say the least, which is why it is hard to trace. My log doesn't help either... it is blank during the CTD

[Mhaedros]

Sounds wierd

[ajak60]

suggest you make sure both third age and barons mod are fully up to date, and installed in the correct order (third age 3.0 then 3.1 update followed by barons mod + barons update) if you dont do it in that order, wierd errors occur