BYU was 0.25 seconds from winning.

http://espn.go.com/ncf/video?gameId=322590254" onclick="window.open(this.href);return false;

Watch Cody Hoffman at 0:34 into the highlight. He has just beaten his man and there is NO safety help. If Riley's arm isn't hit just as he releases it, Hoffman waltzes into the endzone.



But alas, the play was there to be made, and Riley and BYU couldn't get it done.

It's what my friend next to me was saying - "Hoffman in the endzone, we win 28-24."



I can't watch any video of the game. Seeing it once, live, was all I could take.

Yep. Further illustrating the fact that the o line is primarily responsible for the loss.



[ Post made via Mobile Device ] http://cougarcorner.com/images/mobile.png" alt="" loading="lazy" style="max-width:100%">

This all assumes that Riley made a good throw. He pretty much made the throw of his career hitting Hoffman in stride the play before. What are the chances that he makes two perfect throws back-to-back? If it is underthrown the DB would have caught up possibly batting the ball in the air which the clock would have expired even with instant replay.

Riley's flaw got put center stage against Utah. They exposed him. It was not pretty.

Lawboy wrote:
Riley's flaw got put center stage against Utah. They exposed him. It was not pretty.

A bad O-line is the worst flaw any QB can have...

Especially for a QB with a noodle arm, who looks injured, and who also looked glassy eyed and might have hada concussion during the game.

Schmoe wrote:

Riley's flaw got put center stage against Utah. They exposed him. It was not pretty.

A bad O-line is the worst flaw any QB can have...

Regardless. BYU and Riley had a chance to make plays and win the game. They didn't. #noexcuses.



[ Post made via Mobile Device ] http://cougarcorner.com/images/mobile.png" alt="" loading="lazy" style="max-width:100%">

Wickchad84087 wrote:
This all assumes that Riley made a good throw. He pretty much made the throw of his career hitting Hoffman in stride the play before. What are the chances that he makes two perfect throws back-to-back? If it is underthrown the DB would have caught up possibly batting the ball in the air which the clock would have expired even with instant replay.

Two clock questions from the game: Right before the blocked punt, Utah had a delay of game penalty and then had to call timeout to avoid another delay of game. The clock started after the delay of game penalty so they were allowed to run off 25 seconds after the penalty. Can that be right? I can't imagine the clock should run or why ever snap the ball again once you have the lead. Just take a delay of game penalty for 15 minutes and burn the whole 4th quarter.



Another time when this happened was just before the last throw that we're talking about. I think it was after a spiked ball and the ref had to add time back to the clock to get it to 8 seconds. He then said "start the clock on my whistle". Shouldn't the clock start on the snap?



I'm sure the clock ran after the delay of game penalty but it was hard to tell what happened before the last snap with 8 seconds. I was at the game so I couldn't rewind and see what happened.



It doesn't matter to much at this point as the clock operator almost bought us the greatest win ever (off of a fan penalty) but I'd still like to know the rule.

I didn't see the first one but that would be wrong. I don't remember the details on the second but it was the correct call (I think it was a first down and chains were moving.). The 8 sec down to 4 sec was the ute scorekeeper trying to run the clock out.

No, the game clock doesn't start after a delay, but the play clock does. So in order to have a 2nd delay penalty, they called timeout. They wasted 25 seconds of play clock not game clock.

SpiffCoug wrote:
No, the game clock doesn't start after a delay, but the play clock does. So in order to have a 2nd delay penalty, they called timeout. They wasted 25 seconds of play clock not game clock.

The game clock was running after the delay of game penalty.

Schmoe wrote:

No, the game clock doesn't start after a delay, but the play clock does. So in order to have a 2nd delay penalty, they called timeout. They wasted 25 seconds of play clock not game clock.

The game clock was running after the delay of game penalty.

I don't think it should have, I'll go check the rule book.

SpiffCoug wrote:

SpiffCoug wrote:
No, the game clock doesn't start after a delay, but the play clock does. So in order to have a 2nd delay penalty, they called timeout. They wasted 25 seconds of play clock not game clock.

The game clock was running after the delay of game penalty.

I don't think it should have, I'll go check the rule book.

it shouldn't have been, but it absolutely 100% was running. That combined with the early start of the clock on that last play call for an investigation. Not sure why local media isn't picking up on this. Oh, wait, they are all :utard:s



The disease that is infesting that stench pile of a program has apparently made its way to the clock operator.



[ Post made via Mobile Device ] http://cougarcorner.com/images/mobile.png" alt="" loading="lazy" style="max-width:100%">

Wickchad84087 wrote:
This all assumes that Riley made a good throw. He pretty much made the throw of his career hitting Hoffman in stride the play before. What are the chances that he makes two perfect throws back-to-back? If it is underthrown the DB would have caught up possibly batting the ball in the air which the clock would have expired even with instant replay.

When has Riley ever made a bad throw to Hoffman?

http://www.heraldextra.com/sports/blogs/jared-lloyd/byu/lloyd-how-big-were-byu-utah-clock-issues/article_054191c8-011b-11e2-9d67-0019bb2963f4.html" onclick="window.open(this.href);return false;



Clock issues. Why didn't he interview the time official?

Y 4 Ever wrote:

Schmoe wrote:

No, the game clock doesn't start after a delay, but the play clock does. So in order to have a 2nd delay penalty, they called timeout. They wasted 25 seconds of play clock not game clock.

The game clock was running after the delay of game penalty.

I don't think it should have, I'll go check the rule book.

it shouldn't have been, but it absolutely 100% was running. That combined with the early start of the clock on that last play call for an investigation. Not sure why local media isn't picking up on this. Oh, wait, they are all :utard:s



The disease that is infesting that stench pile of a program has apparently made its way to the clock operator.



[ Post made via Mobile Device ] http://cougarcorner.com/images/mobile.png" alt="" loading="lazy" style="max-width:100%">

Maybe Chad Bunn's evil twin brother from the 2010 rivalry game is still in the booth at the U :sick:

Stirfry wrote:

Maybe Chad Bunn's evil twin brother from the 2010 rivalry game is still in the booth at the U :sick:

Funny enough the referee and 2 or 3 other officials from Saturday actually were on the crew who worked that 2010 BYU-SDSU game.

MTM wrote:

Maybe Chad Bunn's evil twin brother from the 2010 rivalry game is still in the booth at the U :sick:

Funny enough the referee and 2 or 3 other officials from Saturday actually were on the crew who worked that 2010 BYU-SDSU game.

We can't put any of this on the officials. No official blocked our first field goal, or missed the second. No official made our center snap the ball retardedly. No official made us false start so often. We make the important plays, we win that game. Simple as that.



Personally, I thought they called a good game. Maybe even a little slanted our way, compared to years past. I thought maybe the play where a Utah WR fumbled but it was ruled incomplete could / should have gone the other way. But both Riley Nelson non-fumbles could have gone the other way, too, so I have no problem with that.

Y 4 Ever wrote:
Yep. Further illustrating the fact that the o line is primarily responsible for the loss.



[ Post made via Mobile Device ] http://cougarcorner.com/images/mobile.png" alt="" loading="lazy" style="max-width:100%">

oline/coaches.