RE: Potential issue with M2M coverage (Full Version)

All Forums >> [Current Games From Matrix.] >> [Sports] >> Maximum-Football 2.0 >> Play Development System (PDS)



Message

Marauders -> RE: Potential issue with M2M coverage (1/24/2008 5:42:58 AM)

What is the speed of the Birmingham quarterback?

Milwaukee QB?

Toronto QB?

Vegas QB?



Yngvai -> RE: Potential issue with M2M coverage (1/24/2008 5:43:03 AM)

OK, then I repeated this test with Chicago in the same league. The speeds are:

HB1 91
FB1 80
3B1 82
R1 97
R2 96

This time, TWO backs (FB1 and 3B1) are left uncovered. The screen shot is attached.

[image]local://upfiles/27800/B7F50528526B47A0B07FBD64979F92CD.jpg[/image]



David Winter -> RE: Potential issue with M2M coverage (1/24/2008 5:47:54 AM)

Is this reproduceable at all with the stock US MFBL league?



Marauders -> RE: Potential issue with M2M coverage (1/24/2008 5:48:02 AM)

I wonder if every player lower than the QB skill rating is being excluded as well as the QB.

Do you have the QB speed ratings for those teams?



Yngvai -> RE: Potential issue with M2M coverage (1/24/2008 5:48:10 AM)


quote:

ORIGINAL: Marauders

What is the speed of the Birmingham quarterback?

Milwaukee QB?

Toronto QB?

Vegas QB?



Birmingham QB = 75
Las Vegas QB = 58
Milwaukee QB = 56
SF QB = 62
Chicago QB = 80
Toronto QB = 79


Based on my tests, the problem is not isolated to the MLF. It occurred in Gary's league as well. It's possible it could happen in the US NFL league that comes with the game, but I only tested 2 teams and it didn't happen with those two teams.



Yngvai -> RE: Potential issue with M2M coverage (1/24/2008 5:50:05 AM)


quote:

ORIGINAL: David Winter

Is this reproduceable at all with the stock US MFBL league?



I've only tested two teams in this league and it hasn't happened. Let me try more teams.

In the mean time, you can download Gary's NCFL league from here:

http://www.geocities.com/gary_l_sorrell/

That will give you a chance to look at what's going on.



David Winter -> RE: Potential issue with M2M coverage (1/24/2008 5:51:33 AM)

quote:

ORIGINAL: Marauders

I wonder if every player lower than the QB skill rating is being excluded as well as the QB.

Do you have the QB speed ratings for those teams?



Well.. I'm not sure that's 100% the reason.. but it's possible that something further down the process, after the exclusion takes place, might be resetting the defenders commands.

It's the only thing I can think of, and it's what I'm tracing through.



Yngvai -> RE: Potential issue with M2M coverage (1/24/2008 5:51:57 AM)


quote:

ORIGINAL: Marauders

I wonder if every player lower than the QB skill rating is being excluded as well as the QB.

Do you have the QB speed ratings for those teams?


That sounds like maybe what's happening. It appears that every player that is slower than the QB gets excluded.

Let me see if I can reproduce the problem with one of the stock leagues. I'll find a team that has a really fast QB.



Yngvai -> RE: Potential issue with M2M coverage (1/24/2008 6:05:46 AM)


quote:

ORIGINAL: David Winter

Is this reproduceable at all with the stock US MFBL league?


YES! I was able to reproduce it with a stock league. The U.S. rules stock leage, using Tampa.

But first I made a roster adjustment. I put C. Ren, speed 75 (the fastest QB on the team) as the starter. Then I made Bredehoff (speed 75) as 3B1. When I did this, the problem occurred. Here's a screen shot:



[image]local://upfiles/27800/876A3D8556B2453C95D79972421BD021.jpg[/image]



Marauders -> RE: Potential issue with M2M coverage (1/24/2008 6:06:13 AM)

I did the above test with Milwaukee in the same league. Again, everything was fine (no screen shot shown). The speeds of the eligible receivers were:

HB1 82
FB1 81
3B1 82
R1 85
R2 89
Milwaukee QB = 56

I then switched to the NCFL, Gary's league. I did the same tests with Las Vegas. Again, everything was fine. The speeds of the eligible receivers were:

HB1 87
FB1 83
3B1 77
R1 89
R2 89
Las Vegas QB = 58

I then ran the same tests with Birmingham. Suddenly, the problem happened. Thus, the problem is NOT isolated to the MLF. Here are the speeds:

HB1 90
FB1 85
R1 88
R2 88
Birmingham QB = 75
3B1 72 = EXCLUDED

OK, then I switched over to the MLF. I first used Toronto as the team. The speeds are:

HB1 93
FB1 84
R1 98
R2 98
Toronto QB = 79
3B1 77 = EXCLUDED

OK, then I repeated this test with Chicago in the same league. The speeds are:

HB1 91
R1 97
R2 96
Chicago QB = 80
FB1 80 = EXCLUDED
3B1 82 =EXCLUDED? Is this number right? It may kick out 2 because of the QB being the same as the FB1.



Yngvai -> RE: Potential issue with M2M coverage (1/24/2008 6:07:45 AM)

Now, when I keep C. Ren (speed 75) as the starting QB, but then move Acree (speed 83) into the 3B1 position, the problem disappears. So Marauders is onto something. The problem seems to happen whenever someone has an equal or lower speed rating than the QB. Here's a screen shot with Acree now in the 3B1 position.



[image]local://upfiles/27800/C606CC1B8E7245B783789D6F2202D082.jpg[/image]



Yngvai -> RE: Potential issue with M2M coverage (1/24/2008 6:09:35 AM)

That's right. 2 were being kicked out in the case of Chicago. The problem happens whenever an eligible receiver has a speed rating equal to or lower than the QB. If two receivers have an equal or lower speed rating, then both those receivers will be uncovered.



Yngvai -> RE: Potential issue with M2M coverage (1/24/2008 6:10:28 AM)

I have to head to the gf's house now so I can't work on this anymore tonight. But hopefully I've given you guys enough information to work with and reproduce this problem.



David Winter -> RE: Potential issue with M2M coverage (1/24/2008 6:12:20 AM)

Okay.. so it looks like there is a problem with the QB being thrown back into the mix after he was removed.

I set up my 8 man league (need to check more than just 11 man football) and set the QB speed to 99. The CB moved to cover him instead of the WR he would normally have.

I've traced through the code at the point the QB is being excluded and he's definately being removed. I just haven't found the place where he's being put back..



Marauders -> RE: Potential issue with M2M coverage (1/24/2008 6:25:45 AM)

Yngvai, sthchaseer, Scott, Deft, Shaggy, Gary ...

Thank you all for your help trouble shooting this.

United community action!



David Winter -> RE: Potential issue with M2M coverage (1/24/2008 7:05:20 AM)

Okay.. so I've made changes to the way the exclusion of players works when running through these routines.

I've assembled a build and passed it to the private testers. Hopefully they'll be able to go through these known problem steps over the few days and verify that the problem has been fixed. It should be part of the bug fixes for version 2.2 along with the new stats features.

Thanks for everyone help on this
David



Deft -> RE: Potential issue with M2M coverage (1/24/2008 7:30:29 AM)

Hmmm, those 3B sets look like my Flex Bone Pro offense.  [;)]

Glad it was found and David had a quick fix.

Thanks for the quick response.



Shaggyra -> RE: Potential issue with M2M coverage (1/24/2008 8:32:51 AM)


quote:

ORIGINAL: David Winter

Okay.. so I've made changes to the way the exclusion of players works when running through these routines.

I've assembled a build and passed it to the private testers. Hopefully they'll be able to go through these known problem steps over the few days and verify that the problem has been fixed. It should be part of the bug fixes for version 2.2 along with the new stats features.

Thanks for everyone help on this
David


Aw, man I was all ready to scout the fastest QBs I could find. [;)]



Marauders -> RE: Potential issue with M2M coverage (1/24/2008 9:13:51 AM)

quote:

Aw, man I was all ready to scout the fastest QBs I could find. [;)]


Actually, commissioners of active non-sim leagues may want use JD's utility to reduce the speed of all quarterbacks temporarily.




Yngvai -> RE: Potential issue with M2M coverage (1/25/2008 8:38:07 AM)


quote:

ORIGINAL: Marauders

quote:

Aw, man I was all ready to scout the fastest QBs I could find. [;)]


Actually, commissioners of active non-sim leagues may want use JD's utility to reduce the speed of all quarterbacks temporarily.




Looks like that solution doesn't work. Deft discovered that even after reducing the speed of all QB's, the problem still occurs unless you do a league reset. Wonder why that would be the case?



Deft -> RE: Potential issue with M2M coverage (1/25/2008 3:44:06 PM)

To Yngvai's point. Here is the example of reduced QB speed (pre-reset) and the reseting the league (post-reset). You will notice the TE on the right is not covered in the pre-reset image.
[image]http://i230.photobucket.com/albums/ee178/BCW5/SS1114043.jpg[/image]



Page: <<   < prev  1 2 [3]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
1.984375