AGEOD Forums

No more CTD's, but I noticed that the processing of the turn is not being paused when the Battle Report Screen appears. Files attached.

Also noticed that in Ice March when you use engagement points to get a new Red general, he appears outside the active playing area and is immediately destroyed for lack of transport.

This is also still a problem in WiA.

Cheers, Chris

OK, engine problem then. Thanks.

Scipio wrote:OK, engine problem then. Thanks.

Mentioned this in 1.02b thread a while ago. Annoying as anything, cos it really messes with the battle report logs too. Missed some important engagements because of this bug.

Noticed in the WIA forum that people were blaming Windows 7, but I'm using XP. I assume this is being addressed by the Powers That Be.

I bought this on release (probably a mistake, but the subject interested me and I wanted to support the concept of outside developers taking on less popular topics) and I'd really like to play it.

I got the problem once too, but in Seven... Now if it happens also in XP, it can mean the code changed, which is weird for this part.

I'll fetch a copy of RUS from Seb and see if I get the same bug.

Thanks for taking a look at this.

Pocus wrote:I got the problem once too, but in Seven... Now if it happens also in XP, it can mean the code changed, which is weird for this part.

I'll fetch a copy of RUS from Seb and see if I get the same bug.

I see it only about once in every 10 turns or so in WiA.

Cheers, Chris

Did a clean install with the latest patch. Still seeing a failure to pause the turn execution with the battle screen. I'm getting it just about every turn.

There also seems to be a more fundamental problem. I've attached the files for my latest try at Ice March. In the message box there are battles reported for 9/36 and 11/36, one for Novocherkassk and another for Ekaterinodar. But I think both battle reports must be for Novocherkassk. Look at the commanders and the number of armored trains. I can't tell whether this is just a reporting problem or whether it's having an effect on the battle resolution itself.

Pocus wrote:I got the problem once too, but in Seven... Now if it happens also in XP, it can mean the code changed, which is weird for this part.

Scipio wrote:Did a clean install with the latest patch. Still seeing a failure to pause the turn execution with the battle screen. I'm getting it just about every turn.

There also seems to be a more fundamental problem. I've attached the files for my latest try at Ice March. In the message box there are battles reported for 9/36 and 11/36, one for Novocherkassk and another for Ekaterinodar. But I think both battle reports must be for Novocherkassk. Look at the commanders and the number of armored trains. I can't tell whether this is just a reporting problem or whether it's having an effect on the battle resolution itself.

I have win 7 but it wasnt a problem in ROP.
Especially when playing reds it becomes more of a problem in Rus while fighting multiple fronts. All the battle reports in that turn getting mixed up.

I tried changing all settings in agesettings etc..borderless, with border,full screen but didnt help

Scipio wrote:Did a clean install with the latest patch. Still seeing a failure to pause the turn execution with the battle screen. I'm getting it just about every turn.

There also seems to be a more fundamental problem. I've attached the files for my latest try at Ice March. In the message box there are battles reported for 9/36 and 11/36, one for Novocherkassk and another for Ekaterinodar. But I think both battle reports must be for Novocherkassk. Look at the commanders and the number of armored trains. I can't tell whether this is just a reporting problem or whether it's having an effect on the battle resolution itself.

Yes the reports also get confused when this happens.
Cheers, Chris

This affect others games, and this is so weird as this code worked for years, so something has changed it seems. I would prefer to get a report from an official Ageod game, and not an AGE engine game, as I can work on the code much more easily.

I think deselecting "pause after battle" could help for now.

NY Rangers wrote:I think deselecting "pause after battle" could help for now.

That is, it helps following the turn without messy battle reports. I just played one turn and it certainly does so.

NY Rangers wrote:That is, it helps following the turn without messy battle reports. I just played one turn and it certainly does so.

Thanks for pointing this out. I'd forgotten about this option.

I was worried that the problem might be corrupting the battle resolution routine and affecting subsequent turns. Maybe I'll try a campaign now.

Pocus wrote:This affect others games, and this is so weird as this code worked for years, so something has changed it seems. I would prefer to get a report from an official Ageod game, and not an AGE engine game, as I can work on the code much more easily.

Testing KWW I see this just about every turn now. Do you not see the problem when you try a turn Philippe?
Maybe I see it more now testing against the AI than I did playing v myself.

Cheers, Chris