turn 3 / error / game crash

[iberunivers]

every turn 3 i clic ok to start to play my turn and the game stop with this message: <<error getting type 'id=sovietguard_1' from type Upgrade.>> [&:]

[Ronald Wendt]

Hello,

please provide the following information:

Which map/campaign do you refer to ?

Which version do you use ?

Can you attach a savegame ?

Regards,

[iberunivers]

scenario :zitadelle, i buy this game today, how can i attach a savegame ?

[Ronald Wendt]

Hello,

first you need to locate the folder with your savegames. Its at:

C:\Users\YourName\Saved Games\Germany at War

You then can send the xxxx.save.xml.gz file to wendt@anvil-soft.com or unpack the .gz and change it into a .zip to attach it here in the forum (it does not allow .gz attachments).

Anyway the error sounds like you should update to 1.00.65 Hotfix as there was a bug in the Soviet reinforcements that appear if you cross the Donets. It should already be resolved.

Regards,

[iberunivers]

windows 7, i5, install update 10055. (1.00.65 Hot.fix isn't found)

scénario : zitadelle try 4 time same bug

savegame it is coming ... 01 sept.

[Erik2]

ORIGINAL: Ronald Wendt
.....
Anyway the error sounds like you should update to 1.00.65 Hotfix as there was a bug in the Soviet reinforcements that appear if you cross the Donets. It should already be resolved.

Regards,

Have you got a link to the 1.00.65 hotfix?
I cannot find it under registered games downloads or member's downloads.
The only updates I find are:
GermanyAtWarBarbarossa1941-Update-v1055
GermanyAtWarBarbarossa1941-Update-v101beta

Thanks
Erik

[Ronald Wendt]

Hello,

@iberunivers: I got a mail from you if you wrote the french one. The link does not work.

@Erik: I am surprised that it was named 1.00.55. here and in the download as it actually is 1.00.65 and this should also be displayed in the lower left corner while running the game. It does in my test version. I checked everything - all my docs and files show this version number. Maybe something got mixed up.

Edit: Its seems 1.00.65. was not released - my bad. It was then replaced by 1.01. as our updates are cumulative. In 1.01. the bug is fixed and the version is doing fine as far as we can see.

Regards,