John Tiller's Battleground Civil War Error

[Three63]

When the Time Limit is reached and the game attempts to go to the Victory screen a CTD occurs when playing the Antietam scenarios. I'm just running it on a simple XP laptop.

[Three63]

Also, I found that Melee attacking limbered artillery still unflicts 25-50 casualties. In general melee attacking artillery is a pain. Is this a bug? You would think it would be a automatic victory. A question also about the skirmish formation. Is it supposed to depoly a separate Unit like in the Napoleon game and as it says in the manual? Is the way it is now a WAD?

[Bostromi]

I have also the CTD when the time limit is reached. Three times now, all at end of NIR Never too late scenario.Very irritating. Laptop & XP.
Is there a fix?

[Hammer732]

Also,
During Chickamauga, no offensive fire sounds are heard. The video plays but no firing sounds are played. The impact sounds are played however. Does anyone elese know about this on the Chickamauga scenarios?

Thanks!

[lordhoff]

Same happens to me (end crash - Antitam); I have to remember to check status before that last phase. I've also had quite a few crashes. I haven't tried any of the others yet; I already have (original) Gettysburg, Shiloh, and Bull Run but I am hoping that this is an Antitam-only problem as it has never occurred on any of those.

Has anyone given you any insight on this problem?

[Alex777]

Me too.  A CTD at the end of every game in PTW.  Using a laptop and WinXP.
 
I also get some CTDs in the middle of a PTW game.
 

[habakuk]

ORIGINAL: Three63

When the Time Limit is reached and the game attempts to go to the Victory screen a CTD occurs when playing the Antietam scenarios. I'm just running it on a simple XP laptop.

I have the exact same problem, playing the Bull Run scenarios using WinXP. I didn´t try any of the other battles yet.

I recognize, that although many people reported to have these crashes when the time-limit is reached, nobody answered until today.
For me, this problem is very annoying - I don´t like to play one of the longer scenarios, being aware that I´ll never know whether I actually won or lost the game in the end ... [:(]

[tshaw]

I'm having the same problem too.  I use Windows Vista Home Premium on a laptop.  I've been thrown out of Antietam, and Bull Run so far. 

[Setanta]

I've got the same problem. CTD when I OK the end of scenario dialog. Running Windows XP SP2 on PIII processor.

Any word on a possible fix would be appreciated.

[Erik Rutins]

Thanks for the reports everyone, we will investigate this week and I'll post as soon as I have any news of a fix.

[lordhoff]

There is a work around. Either before advancing past the last melee phase (ie, after melee before advance to next phase) or even after the crash (if autosave is active), you can simply check status/victory. Still a PITB though.

[lordhoff]

Way late here but, yes I do. Just started Chick--- (Cherokee spelling and me don't get along) and the same is happening to me. BTW, I use XP on a desk top.

[lordhoff]

Some other items I've noticed with Chickamauga:

It is near impossible to tell when a unit is out of ammo as the low on ammo icon applies to both (unlike the others). Believe this to be an error. The highlite doesn't help either because it lumps them together.

Apparently (not 100% sure yet) units can lose multiple fatigue points in a single turn with the default (ie, not quicker) fatigue rules. For instance, I parked a regiment in the rear at fatigue 8 and the next turn it was at fatigue five. Seems inermittent, though. I thought I'd noticed this before but I scored it as non-attentiveness on my part.

Question for "Staff" (if this is read again): This game is old and it would seem these sorts of bugs would be known. Did Talon Soft just sit on it and now lessons have to be relearned?

[lordhoff]

One last comment: the game is not just marking "out of ammo" as "low on ammo" as I earlier thought. It is actually keeping it at "low ammo" giving a perpetual supply of ammunition. I find this, since it affects game play, to be more serious then the other problems. I guess on this old of a game, though, it probably isn't worth fixing unless it is real simple (which I suspect that it is).

[lordhoff]

After further playing and careful note taking, I must recind my last message. Troops are indeed running out of ammo which is marked as low ammo. The way to tell is the low ammo icon appears during defense fire which would normally be unmarked since low ammo does not restrict defense fire. Sorry for any confusion I may have caused.

[Barca9921]

Erik. Any news on the problem ??

[Barca9921]

Well it's over a month now since Erik was looking into this and still nothing.
It really isn't good enough !!

[lordhoff]

I'm surprised he said he'd look into it at all - it is an elderly game and I don't believe sales have met expectations since its re-release. I'd think these two problems could be fixed though in just a few hours time - the audio problem has been fixed by copying files from the other games and the code from the original game could be compared to the current to see what has changed. Oh well, basically the game is functional.

[Mac59]

I too, have been having an issue with apparently random crashes to desktop, as well as the end-of-game crash.
Whenever my irritation level gets high enough, I check this forum to see if it's been addressed yet.
It's very dissapointing to see that it has not, despite Eriks' promise to look into it back at the beginning of March.
My generally high regard for this company is definately slipping.

Low sales or not, if you're going to sell a product, you ought to support it, or if it's not economically viable to support it, you ought to offer refunds to those who expect that support to be there.

Although I can't offer any advice on the random CTDs, except to say I think they are sound related, I find that re-enabling the background music avoids the end of scenario crash.

[tshaw]

Mac59,

That was an outstanding catch! I re-enabled the background sound on two previously saved scenarios and they both worked fine. Good job and thanks!