Matrix Games Forums

Observations – Beta Patch 1.0.131.

Quick Play game – Custom League – American Rules. CPU vs CPU

Team 1 used College2 v1 game plan (wishbone)
Team 2 used College1 v3 game plan (open offense)

Both game plans set to kick field goal at 35 yard line.

New bad –
1. In 3rd quarter Team1 had ball 4th and long. Game suddenly stopped and the following message appeared., “Object variable or with block variable not set in procedure ModGame.GPunt. Press F9 to try and continue.” I pressed F9 and the game continued and team1 punted.
2. Game was set to allow sudden death overtime. Regulation time ended with score tied 3-3 and the game immediately ended with no overtime.

Old moderately bad –
1. Team2 punted and ball went out of bounds on the 3 yard line. Team1 was given the ball 1 and 10 on 20 instead of the 3.
2. One team kicked off and the ball went out of bounds after crossing into the end zone. Instead of coming out to the 20 the ball was given to the other team on the 40. I don’t think this is correct, at least it was not back when I played football.

Minor old bad
1. This is really minor. Several times the QB threw a pass done the field and it fell incomplete. The narrative read Vietor pass intended for Vietor fell incomplete. (Vietor was the QB)
2. This may not be a bug as it may be by design. - Game plan set to kick FG inside 35. Twice the LOS was at points inside the 35 and the offense punted. If the setting on the game plan means that a FG should be attempted if the LOS is inside the 35, it did not work. If it means that the point where the ball with be placed down is inside the 35 then such was not the case and it worked as designed?

Good-
1. MainData.mdb now has 3 difference setting that effect the QB. I did not change any of them after noting that they were now there.

QB1 2 was1/7 for 41 yards and was sacked 3 times (This was wishbone QB and game play has limited pass plays. He ran 2/41, all designed running plays.

QB2 was 9/20 for 122 yards and was sacked 8 times. He had no opportunity to scramble any of the 8 instances. He ran 2 times for 6 yards, both of which were designed running plays.

The low scoring was attributed by a number of fumbles by both teams. The game was fun to watch and other than the new issues that the two issues in which the ball was misplaced I was pleased with the game.

ORIGINAL: Deltadog
Good-
1. MainData.mdb now has 3 difference setting that effect the QB. I did not change any of them after noting that they were now there.

Thanks for pointing that out. It looks like I will have to make an update to my "DataConstant Utility" on www.fbmax.com with these new QB Threshold values.

I haven't installed the newest beta yet, but it looks like things are really getting much better with each patch.

In 3rd quarter Team1 had ball 4th and long. Game suddenly stopped and the following message appeared., “Object variable or with block variable not set in procedure ModGame.GPunt. Press F9 to try and continue.” I pressed F9 and the game continued and team1 punted.

This happened to me, but I was unsure if it was because I was testing alternative punt and fake punt plays at the time.

Team2 punted and ball went out of bounds on the 3 yard line. Team1 was given the ball 1 and 10 on 20 instead of the 3.

One team kicked off and the ball went out of bounds after crossing into the end zone. Instead of coming out to the 20 the ball was given to the other team on the 40. I don’t think this is correct, at least it was not back when I played football.

These are known issues with this build.

You were really quick at posting these here. Thanks for the feedback.

I ran a second game since installing the new patch.

Game played cpu vs cpu, american rules. Custom league Quick play game. Team 1 used College playbook 2 v 2 and Team 2 used College playbook 1 v 3.

1. Team 2 attempted a field goal from the team 1 12. The kick was good. The narrative states that the kick was good for 62 yards.

.2. Team 2 17 and Team 1 14. 59 seconds to play in the half. Team 2 completed a pass good for a first down at Team 1 47. It would have been to the advantage of Team 1 to allow the clock to run out. In the remaining 59 seconds Team 1 called time out 3 times and enable Team 2 to drive inside the team 1 30 and had the clock not run out, Team 2 could have tried a field goal and padded its lead. Team 1 called 3 times out when it should not have while team 2 failed to stop the clock when they were within field goal range and should have done so.

I SAVED THE GAME AT HALF TIME AND CAME BACK LATER TO RESUME PLAY. - When the game resumed the 3rd period was skipped totally. See below.

1. Instead of team 2 kicking off to begin the 2nd half, they had the ball 1 down 10 at the same spot where the 2nd period had ended. It would have been bad if it had then been the 3rd quarter, but ito make matters worse it was the 4th.

2. When the game resumed all of the first quarter stats were gone.

3. Once the abbreviated game ended, I started the saved game again and the results were the same. Team 2 got the ball in the 4th quarter 1 & 10.

If if will be of any held, I still have the saved game and can provide it.