User Pass
Home Sign Up Contact Log In
Page:
 
jdbolick
offline
Link
 
Originally posted by Koncorde
Grow up.

Spare me. You are intentionally being an obstructionist ass in this thread, antagonizing and harassing anyone who discusses this obvious bug. You even went so far as to suggest that it's not a bug at all, proving that your only interest in this thread is to attack and dismiss the people who bring up this obvious flaw in the sim. You're being a troll, which is especially amusing since you're supposed to be a mod. Unfortunately, reporting you to Pallow will achieve nothing.

Originally posted by
Sorry to point it out, but my CB reads screens and has successfully PD's WR screen plays.

Post examples. I have never seen a CB come forward at the snap in reaction to a WR screen. They do come up, but it's movement at the snap that is causing this problem.

Originally posted by
Put a SS, FS, DE or LB into M2M against a man on the LOS and they'll all have the same issues if the player has the faking capabilities or if they fail their read.

Except that they don't, which is why all the many examples people post of this happening are always CBs vs. WRs. You're making up nonsense excuses because you want to undermine legitimate complaints about a bug in the sim.

Originally posted by
Simply preventing forward motion is not a fix.

Yes, it most certainly is. It's not ideal because it doesn't address whatever is causing this in the first place, but it definitely is a fix and would stop the problem. Until you can say that you actually know what is causing the problem, then that type of fix is infinitely preferable to just sitting around with a thumb up your ass doing nothing while this bug continues to cost people games.
 
Koncorde
offline
Link
 
Explain to me why I would want to undermine legitimate complaints? Explain to me how I have harrassed anyone? I have answered every single question asked and given the reasons why a step forward may occur. Explain where exactly I am "trolling"?
 
Sik Wit It
offline
Link
 
Originally posted by Koncorde

Assumption 1. What direction did he fake in?


Even if I'm wrong in the assumption that they can't fake BACKWARDS, that is just means there is an even worse part of the mechanics that is messed up. Seriously? Faking backwards? Now I've heard it all. WRs have 2 fakes...a head fake, and a juke. So either he looked completely behind him...while somehow getting a huge step off the line, or he juked (Juke description: this player quickly moves in one direction, then the other) The WRs clearly aren't juking backward.

Originally posted by Koncorde
Assumption 2. Not really. Even in the examples you provided the "fall for it" counts for a shift to the side, rather than a step forward. Considering every WR does all the time, sooner or later someone is going to fall for it, and it seems to me that they do.


Although some step somewhat to the side, the all involve the WR stepping at least 1 or 2 yards FORWARD at the snap. I don't care if it's forward and to the left slightly...forward and to the right slightly. Forward is what I have a problem with.

Originally posted by Koncorde

No, the big picture is we can't just stop faking in 360 degrees in order to fix an occasional issue at the LOS because it'll muck up the rest of the game.

Identifying other ways of fixing the unrealistic nature of the fake itself is entirely fair game. Think of one.

Of course that requires actually identifying what happened first.


I'm not asking to stop fakes in 360 degrees. Just probably a 90 degree range right at the LOS. That 90 degrees being forward-left, forward, forward-right. As for thinking of a fix...I did think of one. How about the defender actually goes in the direction the fake is pointing? Like I said there's no way these WRs are head faking and juking backwards...so why would the defender run toward the WR?

As for actually identifying what happened first, that's why we're telling Bort, no?

Originally posted by Koncorde

Do they think the pass is being thrown?


At the LOS when the QB is still getting control of the snap? They shouldn't. And if they do, that only goes to further prove my point, the mechanics are messed up.

Originally posted by Koncorde
Would you see it? Only if there is an actual "animation" programmed for it.


You've never seen a Juke? There is an animation for it. It's just like a description...they move quickly in one direction, then go the other.

Originally posted by Koncorde

The big picture isn't that we can't fix it. The big picture is that we can't fix it based on the 3/5ths of nothing that we know about it. Some of the suggestions of how to "fix it" don't actually correct anything because what actually is happening isn't exactly clear.


Again, which is why it should be brought to Bort's attention so he can shed some light on it.
Edited by Sik Wit It on Aug 29, 2009 12:27:55
 
Sik Wit It
offline
Link
 
Originally posted by Koncorde
Originally posted by jdbolick


The "fix" is to code it so that CBs never step forward at the snap. This has already been explained to you, so until you can grasp that extremely simple concept, you should stop posting.


That's not a "fix". That's something that would cause something of an issue on screen plays, or if the LB/SS/FS/DE/CB actually did read the play at the snap- because this is something that in theory effects more than just the CB. Just they're the most noticeable due to their proximity.


The difference is HBs are in the BACKFIELD. WRs are on the LOS or a couple of inches behind.
 
Captain Kaos
offline
Link
 
Originally posted by Sik Wit It
Originally posted by Koncorde


Assumption 1. What direction did he fake in?


Even if I'm wrong in the assumption that they can't fake BACKWARDS, that is just means there is an even worse part of the mechanics that is messed up. Seriously? Faking backwards? Now I've heard it all. WRs have 2 fakes...a head fake, and a juke. So either he looked completely behind him...while somehow getting a huge step off the line, or he juked (Juke description: this player quickly moves in one direction, then the other) The WRs clearly aren't juking backward.

Originally posted by Koncorde


No, the big picture is we can't just stop faking in 360 degrees in order to fix an occasional issue at the LOS because it'll muck up the rest of the game.

Identifying other ways of fixing the unrealistic nature of the fake itself is entirely fair game. Think of one.

Of course that requires actually identifying what happened first.


I'm not asking to stop fakes in 360 degrees. Just probably a 90 degree range right at the LOS. That 90 degrees being forward-left, forward, forward-right. As for thinking of a fix...I did think of one. How about the defender actually goes in the direction the fake is pointing? Like I said there's no way these WRs are head faking and juking backwards...so why would the defender run toward the WR?

As for actually identifying what happened first, that's why we're telling Bort, no?


Just to clarify what Koncorde is saying:

The coding is currently coded in a way to allow fakes to happen at 360°. If Perl is anything like C++, it's almost senseless to change the 360° fakes just for the LOS, because it would more than likely take up close to 50-100 lines of code just to solo that out -- then to work out the bugs of the 360° fakes past the line of scrimmage not firing. Essentially, it'd cause more havok than what it's worth, let alone the time trying to figure out how to solo out the LOS.
 
Sik Wit It
offline
Link
 
Originally posted by cwisler


Just to clarify what Koncorde is saying:

The coding is currently coded in a way to allow fakes to happen at 360°. If Perl is anything like C++, it's almost senseless to change the 360° fakes just for the LOS, because it would more than likely take up close to 50-100 lines of code just to solo that out -- then to work out the bugs of the 360° fakes past the line of scrimmage not firing. Essentially, it'd cause more havok than what it's worth, let alone the time trying to figure out how to solo out the LOS.


So why not limit defenders getting faked out to actually go in the direction the fake is aimed if they fail the vision check? Like I said, no way these WRs are faking or juking BACKWARD.
 
Koncorde
offline
Link
 
Originally posted by Sik Wit It
So why not limit defenders getting faked out to actually go in the direction the fake is aimed if they fail the vision check? Like I said, no way these WRs are faking or juking BACKWARD.


This:

Originally posted by Koncorde
The problem with the Ricky exaple is that he reads a move to the left and moves towards it as if the WR is making a 90 degree turn. He closes the gap because he is set to cover to a short distance. The remainder of his motion is actually his turning circle to recover from the initial fake.

What is the correct movement for a CB if a WR runs 90 degrees to the sideline?

 
Sik Wit It
offline
Link
 
Originally posted by Koncorde
Originally posted by Sik Wit It

So why not limit defenders getting faked out to actually go in the direction the fake is aimed if they fail the vision check? Like I said, no way these WRs are faking or juking BACKWARD.


This:

Originally posted by Koncorde

The problem with the Ricky exaple is that he reads a move to the left and moves towards it as if the WR is making a 90 degree turn. He closes the gap because he is set to cover to a short distance. The remainder of his motion is actually his turning circle to recover from the initial fake.

What is the correct movement for a CB if a WR runs 90 degrees to the sideline?



Ok so ignore the one example that doesn't apply. What about the rest?
 
Captain Kaos
offline
Link
 
Originally posted by Sik Wit It

Ok so ignore the one example that doesn't apply. What about the rest?


From what Koncorde is saying, the sim runs with a 360° fake option, therefore under its current state -- WRs can fake backwards, causing the CB to follow due to his coverage settings.
 
Sik Wit It
offline
Link
 
If that's the case, then that is definitely something that should be looked at as well. Really? A head fake to the backfield as they're running forward? And the CB falls for it?
 
Captain Kaos
offline
Link
 
Originally posted by Sik Wit It
If that's the case, then that is definitely something that should be looked at as well. Really? A head fake to the backfield as they're running forward? And the CB falls for it?


Didn't feel like searching for much, but he's a prime example of a step-back juke http://www.youtube.com/watch?v=oBXPx_tn0Tc

Like I said, to code in C++ a different movement for a very specific spot compared to the rest takes a lot of code. If Perl is anything like it, the hassle isn't worth it with all the kinks that could come in and problems that could arise.

Taking it out completely would eliminate the chance of any step-back juke, or what Koncorde said - it'll muck up the rest of the game.
 
Koncorde
offline
Link
 
Originally posted by Sik Wit It
Ok so ignore the one example that doesn't apply. What about the rest?


The below all follow the same mechanic as explained:
http://goallineblitz.com/game/replay.pl?game_id=720703&pbp_id=4406656 - sideways
http://goallineblitz.com/game/replay.pl?game_id=720703&pbp_id=4406829 - sideways
http://goallineblitz.com/game/replay.pl?game_id=720703&pbp_id=4408426 - Sandstorm is the only one to step forwards, but his motion is to the right.
http://goallineblitz.com/game/replay.pl?game_id=720704&pbp_id=5297722 - motion is to the left.
http://goallineblitz.com/game/replay.pl?game_id=720704&pbp_id=5303682 - sideways
http://goallineblitz.com/game/replay.pl?game_id=714292&pbp_id=7613429 - sideways. Interesting in this one is that both Fart Blossom and Jumper make almost identical "errors" to the extent that if you watch them with an eye on each they're mirroring, which suggests something interesting about their builds or their settings (and/or the build of the WR's opposite them).


These possibly are the result of another mechanic other than Head Fake/Creative such as a critical fail on a vision check:
http://goallineblitz.com/game/replay.pl?game_id=720704&pbp_id=5300453
http://goallineblitz.com/game/replay.pl?game_id=712887&pbp_id=4587822

I don't think they're the same thing to be entirely honest.
 
thunderdoozer
offline
Link
 
When they go sideways, they are following the WR sideways, so that makes sense.

When the CBs step forward, the WR is not moving backward.
 
Koncorde
offline
Link
 
Originally posted by thunderdoozer
When they go sideways, they are following the WR sideways, so that makes sense.

When the CBs step forward, the WR is not moving backward.


No they aren't moving backwards, but they are "faking" that they're moving in a different trajectory which means that the CB "routes" to where the fake is telling him. If it's telling him to go 90 degrees left or right then he will do. And if he's set to hold a 0 yard coverage then he'll also do that.

Part of the issue may well be CB turning circles. Change Direction etc. Their motion is offset from the snap, depending on agility and other factors they'll either change direction on a sixpence, or take a wider angle (and also therefore go further forwards).

In the second set of examples I think there's something else at play though, just to reiterate.
 
thunderdoozer
offline
Link
 
Originally posted by Koncorde
No they aren't moving backwards, but they are "faking" that they're moving in a different trajectory which means that the CB "routes" to where the fake is telling him. If it's telling him to go 90 degrees left or right then he will do. And if he's set to hold a 0 yard coverage then he'll also do that.


Okay, just so we are square:

1. The instances where the CB are moving sideways, they are following the WR and getting outmaneuvered as the WR changes directions.

2. The instances where the CB are stepping forward, they are being faked by a WR that is running forward and head-faking backwards (I can't type it without laughing). And you think this is WAI.

They are completely unrelated, then. We think the (2) instances are bugs, and if it's WAI, it's poorly intended, tbh.

Edited by thunderdoozer on Aug 29, 2009 13:58:12
 
Page:
 


You are not logged in. Please log in if you want to post a reply.