CTD problem

[Watchman]

A faulty sprite or similar should cause a CTD in every battle where the sprite or whatever is in use, shouldn't it ? And at least the ones I keep having seem to be entirely indifferent to the exact composition of armies, terrain and weather involved - the only common factor would seem to be that they are after the very first battle of a session.

Army size may be an issue at least in part though. I remember having fought a small series of minor battles with bandits without trouble, then *BAM!* all of sudden a CTD. The longer the game has been running the greater the risk seems to become, which is why I've been assuming it's some sort of "memory overflow" issue. Although whether memory-hogging other programs are running at the same time doesn't seem to affect the CTD rate, merely overall game and loading speed.

[MarcusAureliusAntoninus]

Rise of Persia had a similar CTD when loading battles. You could play one maybe two battles, but on the second or third you would get a CTD. You could then load a game and play another battle or two without problem. They fixed the sprites in a patch and it went away. Since you seem convinced it isn't the sprites, it could be some other new graphics?

[Teleklos Archelaou]

We're not convinced it isn't sprites.

Any idea about what the ROP issue with sprites was exactly? Were they not present? Wrong format? Some other issue?

[Lusted]

Like i said earlier, i had problems in TE with sprites that related to every 2nd battle fought resulting in a ctd after playing the mod for a while. The solution turned out to be copying the cotents from the descr_model_battle.txt into a clean 1.5 dmb overwriting the original content. There were no problems with the sprites or the way i'd coded them, but it was the fact i was using a modified 1.3 dmb in 1.5 that was cusing the problems, as the way the file is coded changed from 1.3 to 1.5

[Teleklos Archelaou]

Sorry Lusted. Thanks mate. We'll look into that.

[Lusted]

I'd also do that with all your files: find clean 1.5 versions of them, copy the code from your modded files into those new ones and then save them, as the coding(when they're saved) seems to have changed for a few 1.5 files.

[Yun Dog]

Interesting...

Ive never encountered this CTD

playing vanilla 0.74 with not sprite pack

[Kull]

Like i said earlier, i had problems in TE with sprites that related to every 2nd battle fought resulting in a ctd after playing the mod for a while. The solution turned out to be copying the cotents from the descr_model_battle.txt into a clean 1.5 dmb overwriting the original content. There were no problems with the sprites or the way i'd coded them, but it was the fact i was using a modified 1.3 dmb in 1.5 that was cusing the problems, as the way the file is coded changed from 1.3 to 1.5

I made the change you suggested and then ran the same campaign that was generating CTDs in 70% of the "First Battles". After 24 turns and 10 battles, there were exactly zero CTDs, so the fix looks promising. Still looking for others on the team to report similar success. Thanks for sharing, man!

[Cheexsta]

A faulty sprite or similar should cause a CTD in every battle where the sprite or whatever is in use, shouldn't it ? And at least the ones I keep having seem to be entirely indifferent to the exact composition of armies, terrain and weather involved - the only common factor would seem to be that they are after the very first battle of a session.

Actually, I find that faulty sprites cause a CTD the first time the battle is loaded, but then the battle loads properly when the savegame is reloaded. When the battle is running, the faulty sprites are shown by a sort of 'sparkly' whiteness/clearness at a distance.

So if that effect occurs, then it's more than likely a faulty sprite. But it seems Lusted's solution is on the right track...

[Lusted]

I made the change you suggested and then ran the same campaign that was generating CTDs in 70% of the "First Battles". After 24 turns and 10 battles, there were exactly zero CTDs, so the fix looks promising. Still looking for others on the team to report similar success. Thanks for sharing, man!

No problem guys, im glad i could help. It's a little known problem that should really be more well known so that mod teams know what to do when it happens. And im glad i've helped make EB 0.8 more bug free!

[Dram]

No problem guys, im glad i could help. It's a little known problem that should really be more well known so that mod teams know what to do when it happens. And im glad i've helped make EB 0.8 more bug free!

good work dude!

*slaps lusted on the back*

[Dumbass]

Whoop!