• Welcome to OGBoards 10.0, keep in mind that we will be making LOTS of changes to smooth out the experience here and make it as close as possible functionally to the old software, but feel free to drop suggestions or requests in the Tech Support subforum!

duke Game Thread (Thursday, 7:30, ESPN)

He also takes off way too early (but still slowly) and doesn't get the first down.
It's very obvious live that he looks at one receiver and if that dude isn't open then he runs. I suspect the coaches told him to do this to avoid sacks since he has no pocket presence and can't progress through reads.
 
It's very obvious live that he looks at one receiver and if that dude isn't open then he runs. I suspect the coaches told him to do this to avoid sacks since he has no pocket presence and can't progress through reads.
I agree.
 
Duke's 10 4th quarter points came on drives of 54 yards for a TD and 48 yards and a FG. The FG drive was embarrassing, but the offense gave Duke a short field on both of those drives.

What about Duke's 3 play 60 yard TD drive or the 14 play 75 yard TD drive in the 2nd quarter?

Sure the offense gave Duke a short field in the 4th but this defense once again failed to get key stops against a one dimensional offense when the game is on the line
 
My favorite play from last night, FWIW, was on 4th and short running our slowest back parallel to the LOS. I refuse to believe that was the actual play call and think that the OL just buckled and forced him to run that way, but a few F bombs may have been yelled about that call.
It sure looked like a designed play.
 
What about Duke's 3 play 60 yard TD drive or the 14 play 75 yard TD drive in the 2nd quarter?

Sure the offense gave Duke a short field in the 4th but this defense once again failed to get key stops against a one dimensional offense when the game is on the line

Yeah, we got worked on those two first half drives but the defense was good in the second half until we gave them the ball at midfield twice.

The defense also forced a three and out to start the second half, which was great for our momentum. We got the ball at the 34, put together a nice drive, and then missed a 39 year field goal.

Duke's first three drives of the second half resulted in 12 plays, 22 yards, and 3 punts.
 
I would disagree that Wake got beat in all three phases of the game. Special Teams absolutely. We outgained them 400-257 and 6 to 4.5 yards a play, had a more successful 3rd down rate, had a higher red zone success rate (this was basically a tossup though) and lost the turnover battle. The two turnovers, the two missed field goals, and the idiotic penalties on their last two scoring drives were the difference.

It doesn't matter at all since we lost but I'd imagine on the "how badly did we lose" chart and post game win expectancy charts that we "did not lose badly at all" and "should have won" based on how the game played out. Of course this gets into why did we lose and I think you don't have to look much beyond ill timed Mitch Griffis, bad kicking, dumb defensive plays, and somem questionable coaching decisions.

do those metrics consider red zone inefficiency and turnovers to be random events? In WF's case, I don't consider either to be random.
 
Not sure getting rid of the only coordinator with a track record of success is the way to go here.

A better question would be why our 3rd defensive coordinator hire in a row continues to allow struggling offenses to miraculously "get right" when playing against Wake
Well. Let's put it another way. If I'm Clawson, NO job is safe in December. This team is putrid.
 
Defense forced 7 punts and their QB had 86 yards passing. I don't think we stacked the box enough on first and second down, will agree with that.

But, we had several QB hits that results in incompletions on passing plays, and several sacks. Duke QB made three good passes that I can remember - the one drop along the sideline, the TD, and the 3rd-and-13 pass interference. Duke had less than 300 yards of offense. We also gave them short fields several times because of turnovers.

We lost because our QB has 0 ball security, and we missed two very makeable FGs. If we win 24-21, is anyone talking about the defense at all?
 
Nice chip shot field goal to put us up 10-0.

That's awful.

Un-clutch FG kicker and phantom passes/self fumbles is very Caldwell era LOWF.
 
Last edited:
What about Duke's 3 play 60 yard TD drive or the 14 play 75 yard TD drive in the 2nd quarter?

Sure the offense gave Duke a short field in the 4th but this defense once again failed to get key stops against a one dimensional offense when the game is on the line
The D has been fine. They also clearly know that the weight of being in the game falls on them. Can you imagine the mental toll it takes to keep stopping decent teams and then immediately give the ball back to them? Or knowing that if you give up one touchdown at all you may be out of the game?
 
Griffis: Last night we finally saw a few glimpses of what he was supposed to be. Low ceiling/high floor. I don't think any of us really saw him being a record setter, but expected solid and efficient. For 75% of the game, that's what we got. Then some of the things we've seen all season popped back up. The interception on the pump fake might be up there with the Mark Sanchez's butt fumble and the Garo Yepremian's fumble as the worst thing I've seen and then I remember Cam Hite from earlier this season and think this team is just the Little Giants all grown up.

Special Teams: WTF? Short line drive punts and a shank out of bounds. 0-2 field goals from short range. Short kickoffs. Bad returns. Just Bad.

Defense: 75% good. It is like they have 2 or 3 drives every game where it looks like they don't even try. The second duke TD where they just ran for 8 yards a clip and the defense looked like they had never played football before was really strange. The dumb penalties by young guys was frustrating. Jones is such a boom or bust player right now. I really think he will end up as a great player. Obviously, last night he got beat on the TD and had the two bad penalties on the last drive. This was a game where you expected a good defense to step up and hold an undermanned offense to 10 points or less. They weren't always put in good positions, but they didn't play that well considering the opponent.

I am a huge Clawson apologist. Love the guy and I don't think we can do better. Some complaints are Wake never seems to have a foot on the neck mentality and offensive game plan. It seems like these 3 backs and the o-line can run the ball down teams throat if they would let them and be intentional about it. That would take a little pressure off Mitch and help sell the mesh. We saw a few flashes of that last night and then it would just go away.
 
Before last night, the offense was 77th in the country in the SP+ ratings, 11th-best in the ACC, with UVA as the only ACC offense clearly worse than WF. (there is a virtual six-way tie for 2nd worst ACC offense among Pitt/Cuse/BC/WF/NCSU/VT)

Before last night the WF defense was 57th in the country in the same SP+ ratings, 10th-best in the ACC, clearly better than GT and BC and in a virtual 5-way tie including Pitt/Cuse/WF/UNC/UVA
 
All we have to do is get up 2 scores and we win that game.

Instead we get middle school field goal kicking and Griffis' fumbles.

State game should be another "sell out."
 
Our offense is last in scoring in the ACC.

If Lobo were OC, what would we be saying? Can him.

Seems like fans were riding Lobo's ass for several years before he got canned, though.

That having been said, I don't think it's a coincidence that Griffis looked most competent last night on the plays that were not the slow-as-fuck mesh. Of course, if you fumble the ball twice just from having it go back in a throwing motion, well that problem extends beyond the offensive playcalling, which is enough of a problem as it is. Ruggiero is getting a triple whammy with bad playcalling executed by a bad QB with a bad OL.
 
Back
Top