Tight ends in auto generated classes- what gives?

[DaynNite]

Why do all but 2 TEs run a 5 second 40 every year? And your other options are like 4.8 ish guys except for your occasional 6'8 87 speed freak.

I have no idea how they screw up classes so much, they seem to not even consider that the point should be to add a realistic amount and types of talent to keep the league fairly consistent. And do not even get me started on the absurd amount of ///early round/// skill players with like 82 acceleration. And check out the freaks thread for an issue with WRs with exactly 99 mid route running and 96 catch. I know they added edited draft classes but I don't want to know everything and there doesn't seem to be realistic fake draft classes for the PS4 out yet.

[rallew]

Re: Tight ends in auto generated classes- what gives?

The generated draft classes are very unbalanced. I get that some classes have a bigger amount of talent in some positions, but sometimes it gets absurd. In my second year, 11 QBs are projected to go in the first round.

[saybur]

Re: Tight ends in auto generated classes- what gives?

There's a serious lack of speed at CB and RB as well. This has been a problem for a while now. Draft classes don't seem to have been tweaked at all.

[rallew]

Re: Tight ends in auto generated classes- what gives?

I can usually find CBs with pretty good speed. RBs I agree, are difficult to find. Once I find someone with 90+ speed, he’s usually bad at everything else.

[SilverBullet19]

Re: Tight ends in auto generated classes- what gives?

For sake of argument, how many tight ends should be speedsters in each draft class?

I drafted one that had 87 speed, so I got one of the freaks, but for the record his 40 time was 4.8 if I recall correctly. 4.8 is not slow at all, especially for a tight end. I had another on my board that would be right around the same based on 40 time. There were I think 3 in my draft that had over 85 speed. That's actually a good amount. Those are usually the highly touted TE's coming out of college. Those freak athlete's are fairly rare to come by, especially in one year.

Not trying to discount your argument of unbalanced classes, that's true. Just wondering how fast you expect the average tight end to be.

[quickson]

Re: Tight ends in auto generated classes- what gives?

For sake of argument, how many tight ends should be speedsters in each draft class?

I drafted one that had 87 speed, so I got one of the freaks, but for the record his 40 time was 4.8 if I recall correctly. 4.8 is not slow at all, especially for a tight end. I had another on my board that would be right around the same based on 40 time. There were I think 3 in my draft that had over 85 speed. That's actually a good amount. Those are usually the highly touted TE's coming out of college. Those freak athlete's are fairly rare to come by, especially in one year.

Not trying to discount your argument of unbalanced classes, that's true. Just wondering how fast you expect the average tight end to be.

I don't think a 4.8 translates to a 87 in Madden.

4.8 would've gotten you 9th out of 17 TEs at this year's Combine (9th out of the 13 guys who actually ran).

Over the last 3 years, a 4.80 / 40 time would put you at 32 out of 42 TEs who ran at the Combine, so essentially at the bottom 3rd. The vast majority of TEs coming out these days run 4.6s to 4.7s or so.

The acceleration is a real problem, though, because it doesn't track at all to what the rosters default players show (ACC > SPD, generally speaking). You get a bunch of players with 87 SPD, 82 ACC.

[Bkola12]

Re: Tight ends in auto generated classes- what gives?

I had a draft last night that the average speed on corners was like 84.

Sent from my HTC6545LVW using Operation Sports mobile app

[MMurda]

Re: Tight ends in auto generated classes- what gives?

the only reason i havent got too upset about it or worried is because as youre upgrading skill points im noticing accel and speed coming up often at diff positions. keep that in mind. if they have the speeds too high there'd be nowhere for it to go when u upgrade. but yea im still not trying to draft a 84 speed cb. I'd probably edit a guy like that to 86 or 87

[Bkola12]

Re: Tight ends in auto generated classes- what gives?

the only reason i havent got too upset about it or worried is because as youre upgrading skill points im noticing accel and speed coming up often at diff positions. keep that in mind. if they have the speeds too high there'd be nowhere for it to go when u upgrade. but yea im still not trying to draft a 84 speed cb. I'd probably edit a guy like that to 86 or 87

Yeah I was just tinkering with some things in the draft I did last night. I would probably edit all the corner speed to at least 86 or so. Corners need speed to contend.

Sent from my HTC6545LVW using Operation Sports mobile app

[Kentaurus]

Re: Tight ends in auto generated classes- what gives?

For sake of argument, how many tight ends should be speedsters in each draft class?

I drafted one that had 87 speed, so I got one of the freaks, but for the record his 40 time was 4.8 if I recall correctly. 4.8 is not slow at all, especially for a tight end. I had another on my board that would be right around the same based on 40 time. There were I think 3 in my draft that had over 85 speed. That's actually a good amount. Those are usually the highly touted TE's coming out of college. Those freak athlete's are fairly rare to come by, especially in one year.

Not trying to discount your argument of unbalanced classes, that's true. Just wondering how fast you expect the average tight end to be.

For the sake of arguement, there is no way you drafted a 4.8 40time TE who was 87spd. Madden requires a 40 time in the 4.5-4.6 range to get mid-upper 80s spd. This forum page for reference.

That said, there are normally a couple of these guys in the draft classes, which is fine, the problem is that after the couple 85+ spd guys, the rest suddenly fall off to sub-75spd and the complete lack of TEs in this high 70s low 80s range where the vast majority of real NFL TE prospects should be placed. (Futher note, FBs also suffer horribly from this).

So just to test, I quickly ran a season. From this the results were bad.
The #1 TE ran a 4.57, which roughly equals 87 speed. The next best was a 4.82 which is about 78 speed. The average speed of the 19 TE prospects with draft round grades (no undrafted grades) is 72.947.

Compare this to reality, where there are a total of 3 Tight Ends in Madden (not including the Long Snappers) with a Speed value below the average of this draft class. (Lee Smith, David Morgan II and Nick Boyle which all have a 72 speed) As an additional note the rookie TEs in madden on rosters have an average speed of 79.667.

[SilverBullet19]

Re: Tight ends in auto generated classes- what gives?

For the sake of arguement, there is no way you drafted a 4.8 40time TE who was 87spd. Madden requires a 40 time in the 4.5-4.6 range to get mid-upper 80s spd. This forum page for reference.

That said, there are normally a couple of these guys in the draft classes, which is fine, the problem is that after the couple 85+ spd guys, the rest suddenly fall off to sub-75spd and the complete lack of TEs in this high 70s low 80s range where the vast majority of real NFL TE prospects should be placed. (Futher note, FBs also suffer horribly from this).

So just to test, I quickly ran a season. From this the results were bad.
The #1 TE ran a 4.57, which roughly equals 87 speed. The next best was a 4.82 which is about 78 speed. The average speed of the 19 TE prospects with draft round grades (no undrafted grades) is 72.947.

Compare this to reality, where there are a total of 3 Tight Ends in Madden (not including the Long Snappers) with a Speed value below the average of this draft class. (Lee Smith, David Morgan II and Nick Boyle which all have a 72 speed) As an additional note the rookie TEs in madden on rosters have an average speed of 79.667.

Yeah I looked back at that chart, he must have been faster than 4.8, but that's why I said I think that's what it was. Maybe it was 4.6x.

Good info compiling the average speeds. That's actually useful to prove the point that they're too slow.