You got any more of that stuff????Akers back this week with a vengeance!
150 yards rushing and two touchdowns!
That's pretty much what I was just thinking. May be he was just going through the motions and being eaten alive. No desperation or vision to anticipate or switch to an opening in that split second. He just wasn't there.It reminds me of QBs who take a bunch of sacks. After a while, they aren't processing like they need to. On the handful of plays where a lane opens, Akers isn't even looking for it anymore. He's just trying to get a few yards when he isn't getting hit in the backfield.
Time will tell. The one thing we know is he is on the books for another season.He has talent & showed it last season when The Rams won the Superbowl at times.Man, these mixed signals are getting frustrating. First he says its not in his best interest to continue playing for the team. Then he says he misses football. When someone tells him "Then play", he says if it was to him he would. Then McVay says he want to be part of team going forward.
No one knows what to think of this mess. No one knows what caused this mess to happen. All we can do is speculate. Just like the media. They're as much in the dark as we are.
What we do know is Cam has played poorly. He's clearly not the same player he was his rookie year. Is it because of the injury? Was it severe enough to the point he won't be the same player he was pre-injury?
Sometimes it looks like he isn't engaged when he's playing. Ball security problems. No longer the same vision and instincts. Not wanting to take on a pass rusher coming at Stafford. If this is the Cam Akers we now have then I'd rather they just cut him and move on.
And Bettis quit on us also the first year in STL.Akers like Dickerson just quitting. Not a good look.
What in the Crazy Legs Hirsch are you talking about?Why does the RB position always have to be so crazy on this team. Used to be Wide Receivers but on this team it's the RB's.
So it was simmering. Then hit a tipping point. But it was like really nice and nobody was that mad and everyone disagreed but then had a meeting and all is well but he isn't gonna practice.Jourdan Rodrique of the Athletic has a long article today about the Cam situation. I'll copy and paste a couple paragraphs (but not the whole article, since it's a subscription based site-- and well worth it, by the way).
Contrary to rumor, it doesn't at all sound like "Cam called out McVay in front of the team." Rather, it sounds like it was a long simmering issue with no obvious flash point.
Here's Jourdan:
"Multiple people with knowledge of the situation who were not authorized to speak publicly characterized it as an ongoing difference in opinion on several matters, including the overall philosophy and direction of the run game, the frequency of use for the running backs/the frequency of called runs in general, and that Akers and the Rams had simply not been on the same page since late in training camp.
These people did not know of any one particular interaction or event that served as a tipping point for the situation, which they also said did not feel hostile on either side and more so was a mutual disagreement....
....two people with knowledge of the situation who were not authorized to speak publicly said it had been simmering quietly since the middle-to-late portion of training camp."
Yeah, I hear ya, with all that "simmering" it's kinda hard to imagine it didn't boil over at some point.So it was simmering. Then hit a tipping point. But it was like really nice and nobody was that mad and everyone disagreed but then had a meeting and all is well but he isn't gonna practice.
Yeah. Right. We need to all pitch in and buy Jourdan a better bullshit filter.
did we ever hear what McSnead wanted for Akers?...what if the Rams were wanting a second or third for him, probably knowing nobody was going to go there...serving a bit of humble pie as Akers sees all these other backs getting valued....so now, does Akers get a chip on his shoulder to show the league what 31 teams just passed on? Is the damage with McVay and the team too much to overcome? Is Akers even that player that was taken in the second round anymore? Speaking as a Ram fan who knows we need a running game, I hope he does and I hope he is......
At this point, it looks like Akers might be - at least in part - right. No other back is excelling in the current system. Yes, OL, is a huge part of the problem but then we are not making it any easier for them or is it just me who sees our scheme as part of the problem running the ball?Jourdan Rodrique of the Athletic has a long article today about the Cam situation. I'll copy and paste a couple paragraphs (but not the whole article, since it's a subscription based site-- and well worth it, by the way).
Contrary to rumor, it doesn't at all sound like "Cam called out McVay in front of the team." Rather, it sounds like it was a long simmering issue with no obvious flash point.
Here's Jourdan:
"Multiple people with knowledge of the situation who were not authorized to speak publicly characterized it as an ongoing difference in opinion on several matters, including the overall philosophy and direction of the run game, the frequency of use for the running backs/the frequency of called runs in general, and that Akers and the Rams had simply not been on the same page since late in training camp.
These people did not know of any one particular interaction or event that served as a tipping point for the situation, which they also said did not feel hostile on either side and more so was a mutual disagreement....
....two people with knowledge of the situation who were not authorized to speak publicly said it had been simmering quietly since the middle-to-late portion of training camp."