Loading video...

Video Failed to Load

Go Home

This has been analysed to death and yet generally very poorly (O’Hara included). Guehi makes a failed challenge (fails to connect with the ball) that then turns into an attempted block. In doing so, he stands on Solanke’s standing foot before anything else occurs (which ends up costing Solanke...

155,187 views • 8 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

A number of you have asked about the call at the end of the 1st Half of the Bethel Football game at NCC Football in which there was a potential fumble/TD wiped off the board for Bethel that eventually led to no score by the Royals. The full play and a breakdown of issues with the call are in the video below. To be clear, though: 1) It appears that the receiver did not possess the ball at or past the NCC 8, which was needed for the 1st Down (the officials gave the ball to Bethel at the 8 after the overturn, awarding a 1st down). 2) It seems like the wing official was marking forward progress but may not have blown his whistle. It is unclear how he affected the overturn decision in the first place. What is clear is that the officials on the field awarded a fumble and TD, meaning they did not rule forward progress had been stopped. As a result, this aspect of the play is NOT reviewable by rule, as it is a judgment call in real time. 3) No TD should have been awarded before the review in the first place, as the ball clearly was fumbled to the lineman, and fumbles on 4th down in college football can only be advanced by the fumbling player. The ball would have been marked at the spot of the fumble in that case. 4) The officials missed a clear Roughing the Passer call, as the NCC defender went for the Bethel QB's legs while he was in his passing stance. This would have been a half-the-distance and automatic-first-down foul. If this play was called correctly in the first place, it should have been called dead with forward progress stopped at the 8 1/2 yard line and the Roughing foul pushing the ball to the 4 1/4 yard line, 1st & Goal Bethel, with the clock stopped due to penalty. No matter what, though, the Roughing penalty would have ensured Bethel had the ball closer to the goal with 16 seconds left (when forward progress stoppage should have been called). In The (D3FB) Huddle #d3fb

Frank Rossi

28,468 views • 9 months ago

I've been asked to review and provide thoughts on the question of a potential targeting call in the Hardin-Simmons Cowboy Football / UMHB Football🏈 #d3fb game Saturday. I have synced up two videos -- one from UMHB's broadcast and one posted by In The (D3FB) Huddle contributor Riley Conlee (Riley Conlee) (if he could provide credit to the videographer of it, I'd appreciate it). There is a full-speed view and a 20% speed view of the central action included in the video. To evaluate targeting, we have to review both aspects of the rule to see what, if anything, qualifies. I want to provide the entire set of rules (9-1-3 & 9-1-4): "Targeting and Making Forcible Contact With the Crown of the Helmet ARTICLE 3. No player shall target and make forcible contact against an opponent with the crown of their helmet. The crown of the helmet is the top segment of the helmet; namely, the circular area defined by a 6-inch radius from the apex (top) of the helmet. This foul requires that there be at least one indicator of targeting (See Note 1 below). When in question, it is a foul. (Rule 9-6) (A.R. 9-1-3-I) Targeting and Making Forcible Contact to Head or Neck Area of a Defenseless Player ARTICLE 4. No player shall target and make forcible contact to the head or neck area of a defenseless opponent (See Note 2 below) with the helmet, forearm, hand, fist, elbow or shoulder. This foul requires that there be at least one indicator of targeting (See Note 1 below). When in question, it is a foul (Rules 2-27-14 and 9-6). (A.R. 9-1-4-I-VI) Note 1: “Targeting” means that a player takes aim at an opponent for purposes of attacking with forcible contact that goes beyond making a legal tackle or a legal block or playing the ball. Some indicators of targeting include but are not limited to: - Launch. A player leaving their feet to attack an opponent by an upward and forward thrust of the body to make forcible contact in the head or neck area. - A crouch followed by an upward and forward thrust to attack with forcible contact at the head or neck area, even though one or both feet are still on the ground. - Leading with helmet, shoulder, forearm, fist, hand or elbow to attack with forcible contact at the head or neck area. - Lowering the head before attacking by initiating forcible contact with the crown of the helmet. Note 2: Defenseless player (Rule 2-27-14). When in question, a player is defenseless. Examples of defenseless players include but are not limited to: - A player in the act of or just after throwing a pass. This includes an offensive player in a passing posture with focus downfield. - A receiver attempting to catch a forward pass or in position to receive a backward pass, or one who has completed a catch and has not had time to protect themselves or has not clearly become a ball carrier. - A kicker in the act of or just after kicking a ball, or during the kick or the return. - A kick returner attempting to catch or recover a kick, or one who has completed a catch or recovery and has not had time to protect themselves or has not clearly become a ball carrier. - A player on the ground. - A player obviously out of the play. - A player who receives a blind-side block. - A ball carrier already in the grasp of an opponent and whose forward progress has been stopped. - A quarterback any time after a change of possession - A ball carrier who has obviously given themselves up and is sliding feet- first. - A player attempting to recover a loose ball." We need to start at Note 2 to see if Kyle Brown qualified here as a "defenseless player." If not, then 9-1-4 would not apply to him here. Kyle was not a receiver or a passer per se here -- he was clearly a runner downfield and was not in the grasp of any player. As a result, he was not "defenseless" by definition. That means that the only way targeting can be called here is if the provisions of Rule 9-1-3 were violated. Rule 9-1-3 is VERY specific about the initial requirement before we can go to the question of a required indicator: "No player shall target and make forcible contact against an opponent with the crown of their helmet." The crown of the helmet is "the top segment of the helmet, specifically the circular area with a 6-inch radius from the apex (top) of the helmet." In the videos, we see a couple of telling signs. First, Kyle appeared to actually lower HIS helmet as the contact became imminent, which is something coaches advise against for a variety of reasons, including self-preservation. But what is telling is that the UMHB defender attempted to peel off as he saw the angle of the contact he was heading toward with Brown. Specifically, he appeared to end up perpendicular to Brown, perhaps catching Brown's facemask enough to cause the helmet to fly. Yet, that contact was NOT with the defender's crown. As a result, since Brown was not defenseless by rule and because the crown of the helmet was not used for forcible contact to the head/neck area, the picking up of the flag by the officials was appropriate. That said, I spoke with an official who reviewed the videos without commentary and who landed in the same spot as I did concerning the above. They stated that if immediate replay review was available, crews will generally throw the flag and go to review (here, it likely would have been overturned by review, preserving the defender's eligibility). Since the ASC is not providing the on-field replay review yet, the officials' decision would have impacted the game by ejecting a player for the last 6 minutes of the first half until a Halftime review would have been available. For those wondering about how replay is impacting the game, I think this is a good reminder of the nuances it can impact.

Frank Rossi

10,688 views • 10 months ago

Inside the disaster sequence by the Jets at the end of regulation: Jets could have and should have called timeout at 1:01 left and the Packers facing 4th and 5 at the +45. By doing so, the Jets force the Packers to make a decision with 1:01 left, which almost certainly would have been to punt. The average starting field position after a punt from that field position is roughly the 12 yard line. A touchback occurs ~16% of the time which would put you at the 20. For simplicity, assume the Jets have the ball from their own 12 with 51 seconds left and a timeout. One key point here is the Packers only had 2 timeouts remaining, which makes a big difference. The Jets could have run the ball on 1st down and seen what they got. If it went nowhere, they would have the ability to take the clock to 0:00 if needed because the Packers could only stop the clock twice. By not calling timeout, the Jets allowed the Packers to run the clock all the way down to 21 seconds before a delay of game. The clock decay helps one team or the other here, and in this case it clearly helps the Packers. Now comes the next clear mistake by the Jets. Once the delay of game occurred, the Jets could have and should have stopped the clock. By not electing to do so, Green Bay was able to run the clock down to 2 seconds to get a free chance at a Hail Mary. The Jets needed to stop the clock at 21 seconds to force the punt and then take it to overtime. Green Bay would not have been able to run that Hail Mary with 21 seconds. The situation was so chaotic I actually think the Packers missed an opportunity here too. Packers could have called timeout with ~8-9 seconds, tried to get the first down on 4th and 10, and if so called timeout and attempted a game winning field goal. The Packers have had a great long yardage pass offense with Love. If they failed, the Packers would have to defend one play from the ~50. Another Packers option is Trey Smack attempting a ~68 yard field goal with 2 seconds left. For some teams that would have clearly been the best option. Ultimately, this game management by the Jets was objectively incorrect in both of these instances, and the fact it sounds like they did not even talk about it on the headset is beyond alarming.

Ryan Paganetti

499,969 views • 10 days ago

⚽ Day 42 of building my football/soccer game solo in Unreal Engine 5. Tonight, I rebuilt how the ball and the player's feet actually talk to each other while remaining separate meshes. I wanted to get pretty technical with y'all on a Saturday, so enjoy the read if you enjoy this stuff. Otherwise, just watch the video 👍 - Normal dribbling is impulse-based now. The foot arrives, knocks the ball on, the ball is genuinely loose between touches. Stop running and the ball keeps going without you. - We enabled Motion Warping on all 10 turn animations so the montages will now bend the player's path mid-turn so the boot arrives at the ball, instead of the ball being dragged to wherever the animator drew it previously. - Every contact is authored on the animation itself. I track which frame, which foot, which part of the boot, and whether it CARRIES the ball (sole on a drag-back) or STRIKES it (inside-of-the-foot on a 90) - Each contact declares how close the player needs to be. A sole on top of the ball, an inside-foot redirect and an outside-foot push all reach differently — 75 / 63 / 53 units - Touches are credited only to the foot the animation is actually dribbling with - Sideways and forward correction are capped separately. Pushing the ball across your line keeps it. Pushing it forward is how you lose it - Touch strength scales with your speed. The ball has to leave the foot ~1.27× faster than you're running just to stay ahead. This was an annoying bug I kept running into where I overran the ball and left it behind. Have a great weekend. #indiedev #gamedev #soccer #football #unrealengine

Josh

18,077 views • 2 months ago