Battle CTD Reports ONLY

[Cheexsta]

Ok, I'll give that a go. Just quickly, I tried another test to see if my "spear" hunch was right. I reset everything to "standard" EB 0.73 settings (might also be noteworthy that I'm not using the hotfix...) and changed the skeletons so that the fs_javelinmen was the primary skeleton and swapped the primary and secondary attack stats around. The Hypaspists changed to their secondary weapon just before the charge (like in all previous tests) and then swapped back once they were engaged. As soon as they swapped back to their primary weapon, the game CTDed. I'm once again convinced that it's a model/anim problem ~:D

So yes, I'll give the 0.72 anims a go. It might take a while since I'll have to reinstall EB over another copy of Rome (or even to a temporary folder, that might work).

I'm so confused as to what the problem is. It just doesn't make sense: it could be the animations, but then why would said animations work perfectly on all other units? And then why did only the fs_swordsman_barb skeleton work with the spears? It's definately not a EDU problem, otherwise the latter would not have worked, either.

You might have to get one of your modelers to look into this. I think it's over my head...

Edit: ok, there's a few too many new skeletons in the patch to try to use the 0.72 anims, it would require editing quite a bit of DMB. I might give it a go later on when I have the patience to edit all of that

[QwertyMIDX]

Many other units have the same spear/sword combination, a combination which has always made RTW a little unhappy. Try testing the Arverni Arjos, the Soldorus, the Gastiz, etc.

[Kull]

OK guys, this bug is solved....no further testing is necessary (at least on this one).

It's a problem with the new sword/spear animation. Evidence:

Cheexsta tested the Hypaspistai, a unit using that animation. Result = CTD.
QM tested Arjos, a unit using that animation. Result = CTD.
Numerous individuals haave reported problems with the "Sweboz General". It turns out that his bodyguard uses that animation. Result = CTD.

I'll keep you posted.

[Dooz]

*sniff sniff*

I smell hotfix. Mmmmmm.

[Kull]

*sniff sniff*

I smell hotfix. Mmmmmm.

Shhhh. Don't tell anyone, but I think I just found the pre-battle CTD too.....

[Teleklos Archelaou]

-At least some pre-battle sprite problems fixed that caused CTDs
-One animation or skeleton that was causing a CTD in some battles
-Placement of a port building by scripts that wasn't showing up on maps and later caused CTDs
-A trait problem that may have been causing CTDs

All of the first three could be fixed with a hotfix and still be save-game compatible. I don't know if the last one would be. But a hotfix with these issues would remedy a lot of the problems and probably be save game compatible too.

[khelvan]

The only thing that won't be saved-game compatible is the ports issue; it turns out the script placement doesn't actually solve the problem, which is why we had it in 0.7.2 as well (hence all the frustration with later-game CTDs with that version). This is unfortunate, because every single player WILL run into this problem at some point, unless they immediately take Kypros.

The 0.7.3x versions have been very buggy and we realize this. We introduced some new bugs that weren't caught in initial testing, but with your help we have found all of them, we think, and while I've posted some temporary solutions, a new patch version should be out in a few days.

0.7.4 will be the stable version we all thought it would be. Assuming the 0.7.2 nasty CTD bug was the port problem, and I firmly believe it was, all of the 0.7.2 known CTDs will have been fixed in 0.7.4.

I can't promise there will be none at all, but it will be what 0.7.3 was supposed to be, and more.

Also, see my latest edit here for how to fix that port problem without losing your current campaigns. The power is yours, if you are a good player.