[Official] NFL 2010


Recommended Posts

He was completely down, though. He maintained position through the catch, to the ground, and when he was getting back up, he let the ball go. It was a very bad call and some ref should be on the brink of losing his job.

I'm over the moon about that Cowboys loss though. The Redskins still suck, but apparently the Cowboys are even worse. :laugh:

Also, I hate Vick (because I hate what he did and I also hate his alma mater, Virginia Tech [which had an absolutely hilarious loss to JMU, an FCS team, this weekend :D]), but he really should be starting for Philly. Kolb was complete ****.

i don't agree with that, to me it looked like he "dropped" the ball when he hit the ground

and you guys wouldn't beleive the looks i get when i'm wearing any of my vick jerseys (got 4, 3 ATL, one philly) when i'm walking my dog :rofl:

That is not, by rule, an incomplete pass. The ground can't cause a fumble, just like it can't cause an incomplete pass when you have control of the ball when hitting the ground. What happened after he hit the ground is relevant to the situation unless you argue he didn't have control, and it seems pretty clear to me that he did, in fact, have control. Just because he had the ball in one hand doesn't mean he didn't have control. He was down, the ball was controlled securely in his hand.

To quote the rule, "if the regains control of the ball prior to the ball touching the ground, the pass is complete." His legs were clearly down, he clearly had control of the ball, and then it came out after making the catch. This isn't like the other instances where the receivers lost control of the ball or weren't properly handling it. He doesn't need two hands on the ball to have control.

But the ground can cause an incomplete pass if it causes the ball to shift. This video should help with whatever is getting lost in translation in our discussion because we both agree that he really did have control prior to him putting the ball on the ground. He didn't "maintain control" after the ball hit the ground because his rolling and setting his right arm down with ball in hand was part of the process of going to the ground, not separate. I agree that it should have been a touchdown, but I'm also pointing out why it wasn't based on the rule.

I don't know how else I can try to explain it without repeating myself. It's unfortunate for the Lions, but a five or ten second play doesn't play the sole factor of a game's outcome, which Jim Schwartz acknowledged in his post game interview.

But the ground can cause an incomplete pass if it causes the ball to shift. This video should help with whatever is getting lost in translation in our discussion because we both agree that he really did have control prior to him putting the ball on the ground. He didn't "maintain control" after the ball hit the ground because his rolling and setting his right arm down with ball in hand was part of the process of going to the ground, not separate. I agree that it should have been a touchdown, but I'm also pointing out why it wasn't based on the rule.

I don't know how else I can try to explain it without repeating myself. It's unfortunate for the Lions, but a five or ten second play doesn't play the sole factor of a game's outcome, which Jim Schwartz acknowledged in his post game interview.

and that's the key. I think it's a good rule, they have to keep it that way, they just can't change it for an endzone. You have to have possesion of the ball during all instances of the catch.

But the ground can cause an incomplete pass if it causes the ball to shift. This video should help with whatever is getting lost in translation in our discussion because we both agree that he really did have control prior to him putting the ball on the ground. He didn't "maintain control" after the ball hit the ground because his rolling and setting his right arm down with ball in hand was part of the process of going to the ground, not separate. I agree that it should have been a touchdown, but I'm also pointing out why it wasn't based on the rule.

I don't know how else I can try to explain it without repeating myself. It's unfortunate for the Lions, but a five or ten second play doesn't play the sole factor of a game's outcome, which Jim Schwartz acknowledged in his post game interview.

The video explains nothing. All it does is restate the rule. When the NFL released clarification, they didn't explain why the pass was incomplete, they just restated the rule. And of course the network it owns isn't going to say they're not addressing the issue, and Jim Schwartz isn't going to risk getting fined for criticizing the officials.

The ground can cause an incompletion, but not when you area already down with control of the ball. The only way the ground can cause an incompletion is if you do not have control of the football. Let me repeat the rule again: "if the player regains control of the ball prior to the ball touching the ground, the pass is complete." Please note the very end of the quotation -- "the pass is complete." It does not matter what happened AFTER the ball touched the ground! PRIOR to the ball touching the ground, he had control of the football, which the very rule says is a completion. They even quote that portion of the rule in the video you posted.

So, let me repeat my main points again: it doesn't matter what happens AFTER the ball hits the ground as long as you have control WHEN it hits the ground, as the rule clearly states. It should have been a touchdown, even by the rule. The only reason people think it's not is because they're buying into the fact that just because the NFL restates the rule that it somehow changes what happened. Let me put it this way: read the rule thoroughly yourself. Block out what everyone else says -- me, the media, the NFL -- and tell me whether or not you think he had control of the football when it hit the ground. Because according to the rule, what happens after the ball makes contact with the ground does not matter as long as he had control prior to it hitting the ground.

Hell, even the official closest to the play called it a touchdown as it happened. I don't know what else is necessary.

You really think the players and coaches are worried about being fined for saying something negative? Fines for comments almost always comes with an explicit laden rant, not for saying someone made a ball calls. As for the analysts and commentators, sure, they're employed by the NFL but they're not yes men, and you'd be foolish thinking they all were (because there's plenty that proves otherwise).

And I've done all I can making the case of the rule. If this video doesn't help you understand why, then nothing will. It's the most exhaustive source available on the rule.

Man, you all can really find anything in the world to argue about huh? :laugh:

Anyway, my team Big Blue won their first game of the year, but I am pretty confident they will fall apart in the end of the season like they did last year.

Watching Gang Green right now, Baltimore just went up by 1, thanks in part to a whole lot of penalties.

You really think the players and coaches are worried about being fined for saying something negative? Fines for comments almost always comes with an explicit laden rant, not for saying someone made a ball calls. As for the analysts and commentators, sure, they're employed by the NFL but they're not yes men, and you'd be foolish thinking they all were (because there's plenty that proves otherwise).

And I've done all I can making the case of the rule. If this video doesn't help you understand why, then nothing will. It's the most exhaustive source available on the rule.

Um, not sure what sports you watch, but in every major American sport league (NFL, MLB, NHL, NBA), if you criticize the officiating, you get fined. It doesn't matter if your rant is "explicit laden," if you criticize the officiating, you get fined.

You still have not explained how you agree with the fact that Johnson had control when he hit the ground (and before the ball came out), but think the ruling was correct. Because the two contradict one another. The official definition -- the very definition stated in the video you keep quoting -- says that if you have control of the ball when coming down, it's a catch. It literally says that it's a catch. If that can't tell you why the ruling is wrong, then nothing will. :p

Um, not sure what sports you watch, but in every major American sport league (NFL, MLB, NHL, NBA), if you criticize the officiating, you get fined. It doesn't matter if your rant is "explicit laden," if you criticize the officiating, you get fined.

You're right, I was mistaken.

You still have not explained how you agree with the fact that Johnson had control when he hit the ground (and before the ball came out), but think the ruling was correct. Because the two contradict one another. The official definition -- the very definition stated in the video you keep quoting -- says that if you have control of the ball when coming down, it's a catch. It literally says that it's a catch. If that can't tell you why the ruling is wrong, then nothing will. :p

I'm explaining why I understand how it was ruled while disagreeing with it by saying it should have been a touchdown, so no contradiction :p It's a rare case showing the rule as inadequate.

Simply touching the ground doesn't end the player's motion of landing, rather the entire process of landing and if there is one, finishing a roll, is considered. To me, the process stopped when he caught himself using the ball with his right hand.

Yeah he is, but the Jets offense were absolutely terrible. Utterly awful. 6 first downs. Sanchez was 10 of 21 for 74 yards (many bad throws), IIRC no third down conversions; the only highlight for the Jets offense was LT's rushing, which was a only 62 total yards on 11 carries. It was a good defensive game, but Sanchez looked uncomfortable and was far too eager to throw a quick pass. It's only the first game, so there's room for improvement, but a strong defense can only carry a terrible offense so far.

Rivers 22 completions for 298 yards and two touchdowns and yet he's going to get saddled with the loss.

Cassel (10 completions for 68 yards and a single touchdown) will get the win.

It's crazy out there.

Edit:

Rivers did fumble twice so there's your explanation. KC also benefited from special teams (punt return TD).

Rivers 22 completions for 298 yards and two touchdowns and yet he's going to get saddled with the loss.

Cassel (10 completions for 68 yards and a single touchdown) will get the win.

It's crazy out there.

Edit:

Rivers did fumble twice so there's your explanation. KC also benefited from special teams (punt return TD).

Kansas City wasn't focused too much on throwing a slippery ball, they wanted to eliminate turnovers which the Chargers for some reason weren't worried about. That's just being smart about your play calling and relying on the talents of your team (specifically their special teams players). Don't take away from the Chief's win that they deserved.

falcons are going to murder that defense. Can't wait to see Vick play again too!

I hope they kill Arizona, need that confidence back, quick.

told you!

vick had an awesome game today too (love having sunday ticket, watched both games).

cowboys losing makes me happy, hate them. now all i need is the saints to die tomorrow while thomas gettig 4 tds for my pool and it'll be a perfect week-end.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Nobody is buying a PS5 only for playing Until Dawn 2. Their loss.
    • If you actually used it instead of responding like a petulant child you might be surprised. I switched from Google some time ago and have been very satisfied.
    • I am one of the first people to use the DXVK technology. In the channel below you can see some videos that I have made using this technology, including Assassin's Creed Odyssey. https://www.youtube.com/@nahum7995/videos Assassin's Creed Odyssey experienced several bugs and technical issues during its first months after release. It launched with its own fair share of funny but frustrating glitches. I ran it on DXVK 9 days after its release and I played it for many hours but didn't see a single significant bug on Linux. Assassin's Creed Odyssey is widely celebrated for pushing the franchise in bold new directions and specifically for nailing several elements better than any other title in the AC series: Player Choice & Branching Narrative, The Mercenary & Cultist System, Mythological Integration, Overpowered Combat Abilities, Open World Exploration But what I'm trying to point out is that this game wasn't quite playable on most windows systems, until a few months after its release when most of the bugs were fixed. However, on Linux it ran completely flawless from day one, although DXVK had seen little development and refinement at the time. What do you think the situation will be in 2026 now that most bugs and glitches of DXVK have been completely eliminated? This is information from Google about these situations that I am quoting. In many cases, using DXVK (a translation layer that converts DirectX 9, 10, or 11 into Vulkan) can result in more stable frame times and higher performance than native Windows rendering. This happens primarily by bypassing driver overhead and multithreading draw calls that were previously restricted to a single CPU core. Older APIs (like DirectX 9 and 11) are largely single-threaded on the CPU side. DXVK translates these calls to Vulkan, which is highly multi-threaded. This reduces CPU-bound stuttering on weaker processors. In certain cases, GPU manufacturers (especially AMD) have significantly better and more modern Vulkan drivers than they do for legacy DirectX. Vulkan gives developers—and in this case, the translation layer—closer control over how resources are held in VRAM. This can prevent micro-stutters and sudden frame drops during chaotic gameplay. Yes, certain games, particularly older DirectX 9 to 11 titles, can run with fewer crashes on DXVK than on native Windows. By intercepting DirectX draw calls and translating them into the modern, highly efficient Vulkan API, DXVK bypasses the limitations and poor driver support that cause instability in aging game engines. PlayStation 1, PlayStation 2 and PlayStation 3 can be easily and perfectly emulated on Linux. In fact, modern Linux emulators offer high-performance upscaling, widescreen patches, and automatic controller mapping out of the box.                                                                                                                                                                                                                                                                                                                                 PlayStation 1/2/3 games look drastically better on Linux thanks to resolution upscaling. Furthermore, it is also a fact that you cannot play many fun games on Windows either, isn't it? - The Nintendo Switch has an extensive library of exclusive games. - PlayStation has an extensive library of exclusive games - Android has "mobile-exclusive" games, meaning they are exclusive to mobile devices (iOS and Android) and aren't available on PC or consoles. And finally, it is also the case that in the next five years there will be games that millions of people will say you absolutely must play and that they want to play this specific game that released a few days ago. However, the other side of this story is that currently, absolutely no one cares that they cannot play these upcoming games right now.
    • Flameshot 14.0 RC3 by Razvan Serea Flameshot is a free and open-source, cross-platform tool to take screenshots with many built-in features to save you time. Using Flameshot is as simple as launching, dragging the selection box to cover the area you want to capture, making annotations as needed in on-screen and saving the shot to your computer, all with a very simple and straightforward interface. Flameshot allows users to simply upload their screenshots directly to the cloud in order to easily share it with others. You can upload your image directly to Imgur with a single click and share the URL with others. In-app screenshot editing - You can choose to add an arrow mark, highlight text, blur a section (blur or pixelate an area), add a text, draw something, add a rectangular/circular shaped border, add an incrementing counter number, and add a solid color box with Flameshot's built-in editing tools. Command-line interface (CLI) - Flameshot has several commands you can use in the terminal without launching the GUI via a command line interface. The command line interface lets you script Flameshot and use it as the subject of key binds. Flameshot 14.0 RC3 changelog: Translations update from Hosted Weblate by @weblate in #4612 Translations update from Hosted Weblate by @weblate in #4619 Fix pin position on Windows for scaled screen by @ElTh0r0 in #4614 Cmake Analyzers by @ElTh0r0 in #4613 Translations update from Hosted Weblate by @weblate in #4632 fix(macos): prevent config tab content from rendering behind tab bar by @Mitnitsky in #4627 fix(macos): use CGRequestScreenCaptureAccess instead of grabWindow for permission request by @Mitnitsky in #4617 Fix KDE Plasma keyboard shortcut config file by @ElTh0r0 in #4637 fix(macos): fix clipboard copy failing from tray and GUI by @Mitnitsky in #4629 feature(macos): show dock icon when config window is open by @Mitnitsky in #4628 Option to disable tray icon on Windows by @ElTh0r0 in #4634 Translations update from Hosted Weblate by @weblate in #4642 fix(macos): make fullscreen capture overlay configurable by @Mitnitsky in #4622 Update GH actions using Node.js 24 by @ElTh0r0 in #4660 fix issue with screen selection in non interactive mode by @borgmanJeremy in #4667 Uniformize both spec files + ninja build openSUSE by @QuentiumYT in #4658 screengrabber: pass non-empty parent_window to xdg-desktop-portal by @artefaktor93 in #4664 Allow multiple flameshot GUI instances (fix for #3177) by @ElTh0r0 in #4680 Unify Linux ARM CI into Linux CI (also drop QEMU) by @theofficialgman in #4702 respect system proxy settings by @borgmanJeremy in #4674 Replace ifdef LINUX with UNIX to include BSD systems by @ElTh0r0 in #4700 Download: Flameshot 14.0 RC3 | 18.1 MB (Open Source) Download: Flameshot Portable | 53.0 MB Links: Flameshot Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
  • Popular Contributors

    1. 1
      +primortal
      490
    2. 2
      PsYcHoKiLLa
      233
    3. 3
      Skyfrog
      78
    4. 4
      FloatingFatMan
      68
    5. 5
      Michael Scrip
      58
  • Tell a friend

    Love Neowin? Tell a friend!