Page 1 of 1
Yet more problems..
Posted: Thu Jan 22, 2009 1:57 pm
by gbs
Attached is a a zip of my saved game Nov Dec 1914 as CP in the Diplomatic phase. I am finished and wish to move on to the next phase. The message I get says "not allowed. already notified now must wait for other players (human or AI)." ......nothing happens and I'm ashamed to say I sat there for 10 minutes. FRom ther the game hangs up when I try to quit and I have to end the game through the Task Manager.
I want Calvinus to try to move past the diplomatic phase and if he comes back and says he had no problem then I just give up.
Norton is turned off. Everythig is disabled in Configure Game. Sound Maps, everything
Do I sound FRUSTRATED?
Posted: Thu Jan 22, 2009 2:31 pm
by calvinus
Incredible bug!

I reproduced it, and I'm working on it with max priority.
Posted: Thu Jan 22, 2009 3:31 pm
by calvinus
This bug is linked to the advanced play mode only. So, waiting for my fix, please do as follows:
1) load the savegame
2) disable the "Strictly turn-based" mode, so going back to the WEGO mode
3) un-pause the AI and let her finishes her job
4) click the "End turn/phase" button
You will enter the new phase. Once there go back to the advanced play mode.
Thanks,
Calvinus.
Posted: Thu Jan 22, 2009 4:07 pm
by gbs
Thanks. Glad to hear it's not just me.
Posted: Thu Jan 22, 2009 7:08 pm
by calvinus
Bug generated by the beta-patch 1.05G! Fixed!

Posted: Thu Jan 22, 2009 7:16 pm
by tagwyn
Luca: You mean you are correcting the organization/spelling of all the HUN army? LOL

apy:
Posted: Thu Jan 22, 2009 8:08 pm
by calvinus
Tomorrow I will ask Philippe to publish a preview of 1.05H, in order to let you continue your game.

Posted: Thu Jan 22, 2009 8:13 pm
by Rafiki
tagwyn wrote:Luca: You mean you are correcting the organization/spelling of all the HUN army? LOL

apy:
[color="Blue"]Tagwyn, this has nothing to do with what is being discussed. What's the point?[/color]
Posted: Fri Jan 23, 2009 12:22 pm
by calvinus
Diplomacy phase hang fixed with 1.05H, downloadable. It was a regression bug introduced by the beta-patch 1.05G.