Page 1 of 1

Not Able to play WarPlan-error message

Posted: Mon Mar 01, 2021 5:07 pm
by baloo7777
Went to start up my WarPlan game and got the following screen for about 5 seconds then it crashes to desktop.
1. What happens to any PBEM games started and going using the beta 10u3?
2. Do I have to delete the game from my hard drive and download a fresh copy with the latest
official version (1.091)?
3. Is there a new beta coming out? Or is there a new official version?

I don't know if any of my pbem opponents know this as it's my turn in both the games using the beta 10u3.



Image

RE: Not Able to play WarPlan-error message

Posted: Mon Mar 01, 2021 7:14 pm
by ncc1701e

RE: Not Able to play WarPlan-error message

Posted: Mon Mar 01, 2021 8:25 pm
by AlvaroSousa
You will be fine just get the new one.

RE: Not Able to play WarPlan-error message

Posted: Mon Mar 01, 2021 8:28 pm
by baloo7777

Never saw that so I didn't get it. Still can't use my WarPlan on that computer. What happens to games with opponents in PBEM with the beta 10u3 (did not use 10u10)

If I try doing a turn with 1.091 that was being played with beta 10, what will happen?

RE: Not Able to play WarPlan-error message

Posted: Mon Mar 01, 2021 11:24 pm
by AlvaroSousa
That message is only for Beta. It was set to expire 3/1 because I was going to have a patch ready. but there were some bugs to be fixed so I delayed it a week.

Just get the beta and override the files on the beta folder. The different from old beta isn't game breaking. It is much more A.I. and UI stuff.

RE: Not Able to play WarPlan-error message

Posted: Tue Mar 02, 2021 1:57 am
by baloo7777
ORIGINAL: AlvaroSousa

Just get the beta and override the files on the beta folder. The different from old beta isn't game breaking. It is much more A.I. and UI stuff.

Isn't the newest beta the one with supply trucks changed? Is that change in the next official version (1.10 I think)?

RE: Not Able to play WarPlan-error message

Posted: Tue Mar 02, 2021 11:03 am
by AlvaroSousa
It is somewhere in the change log when that happened.