Page 1 of 1
Error mesage
Posted: Thu Oct 24, 2013 9:27 am
by Hexagon
Well, i was testing something in the tutorial scen when i have this error
The heli unit shot all it has over enemy tanks, when is low of ammo it retreat (i dont use the emergency resupply rule) all ok until i click over the unit in OOB to see how many time i need to see it again on battlefield them appear this error message.
All is working fine in the save except this.
RE: Error mesage
Posted: Thu Oct 24, 2013 9:46 am
by cbelva
Do you have a saved game that duplicates this error. That would be extremely helpful in tracking in down.
RE: Error mesage
Posted: Thu Oct 24, 2013 10:24 am
by CapnDarwin
Is the error repeatable? Does it happen if you restart the game from scratch? Please post your save game file as Charles pointed out.
RE: Error mesage
Posted: Thu Oct 24, 2013 10:36 am
by Hexagon
Yes, i have the save and everytime i open it same error message even when i close game and start it again.
RE: Error mesage
Posted: Thu Oct 24, 2013 11:21 am
by cbelva
Hexagon, Can you rezip and repost the saved game file. I am getting message that the zip file is invalid. I tried it several times.
RE: Error mesage
Posted: Thu Oct 24, 2013 11:28 am
by Hexagon
No problem, i never use zip, prefer rar but i cant upload rar files in forum.
RE: Error mesage
Posted: Thu Oct 24, 2013 12:19 pm
by cbelva
That did it. I got it thanks.
RE: Error mesage
Posted: Thu Oct 24, 2013 12:25 pm
by cbelva
Ok, this appears to be a bug we have been looking for since the day after the game was released. Unit withdraws from the battle and if you click on its name in the oob window (it is greyed out to show it has withdrawn) it pops this error. We have not been able to duplicate it and the original posted did not have a saved game file. I can duplicate this which means Rob can so hopefully we can put this bug to bed. Thanks Hexagon

RE: Error mesage
Posted: Thu Oct 24, 2013 1:00 pm
by Hexagon
I feel now like a bugbuster [:D]

RE: Error mesage
Posted: Fri Oct 25, 2013 2:11 am
by cbelva
Hexagon, you are a Bugbuster. I got word from Rob tonight that this was the bug we had been looking for and gave up on because we could not duplicate it. It is now officially squashed. It should be in the next patch after 2.01.