Problem

[Brockleigh]

Hey folks...

Okay, I've run into a problem trying to get my expanded CFL league going.

I've played several quick games to check how the new teams and downloaded stadiums look, but tonight I tried to start the first week of the league schedule. So when I tried to move to the schedule screen, I got this error:

Subscript out of range in procedure modGame.ScreenDataLeagueBottom4
Press F9 to attempt Continue

When I hit F9, it brings me back to the League's Main Menu screen. I tried to move to the schedule screen again, and got the same error. When I tried using the other arrow to flip to the schedule screen, I got

Could not Continue
Press Esc to Quit

So, ummm... help?

[Tbird]

Check the stadium for the home team make sure no images are missing including the p1.bmp file

[Brockleigh]

There's no home team involved, Tbird. I can't even get to the schedule screen to select a game. The error I posted prevents the schedule from coming up.

However, in answer to your question, I've tested all the stadiums I have, and they all work just fine.

[Tbird]

It could be the very first game on the schedule as soon as you click to get to the schedule because it highlights the first game and tries to display the picture of the stadium.  I think it's the p1.bmp file check all you stadium folders, I just took it out from one of stadiums and got that exact error message.

[David Winter]

Before you do anything else, please zip up and send the league *.mdb file to support@wintervalley.com
 
This is the second reported bug that involved downloaded stadiums so I need to replicate the problem and see if I can deal with it from the game side.

[David Winter]

Brockleigh sent me his league file and I've been able to correct this problem.

[MitchG]

I had this issue last night. I just purchased a new computer and was installing MAXFB on it. When I installed the April build, I got the same error that you described. After I installed Release 3, everything cleared up and seems ot be running fine.

[Marauders]

Thank you for posting that, Mitch.
 
With beta builds, it is often just as important to post what has been fixed as it is to post what has not.