User Pass
Home Sign Up Contact Log In
Page:
 
Summers
offline
Link
 
Edited by legalbama on Aug 31, 2009 21:39:49
 
The_Jonas
offline
Link
 
Yes.

This bug only happens when the offense is moving up.

I had a started a thread about it last season or maybe 2 seasons ago and it was fixed within 2 days. (thanks to Hazy)

It returned when the season started.

How f**king hard can it be to code coverage the same way both directions? This never EVER happens when the offense moves down.

No argument about build or tactics is valid because it only happens when moving ONE direction. Tactics and builds are not picky about that... but the sim engine is.
Edited by The_Jonas on Aug 31, 2009 21:48:06
Edited by The_Jonas on Aug 31, 2009 21:46:27
 
Sik Wit It
offline
Link
 
Must have been the season before, because this was happening last season to some guys on one of my teams too.
 
jdbolick
offline
Link
 
Yeah, it's been happening for a while. Bort has acknowledged that it's a bug and tried to fix it with various updates, but can never seem to eliminate it completely. It also seems like various changes to the WR / CB dynamic have made it more prevalent again this season.

And fyi, we have found at least one example of it happening when going down the screen.
 
Sik Wit It
offline
Link
 
I still think it's at least a 10:1 ratio of up : down though...at least in the examples I've seen.

edit: damn smilies
Edited by Sik Wit It on Aug 31, 2009 22:27:23
 
The_Jonas
offline
Link
 
Originally posted by jdbolick
Yeah, it's been happening for a while. Bort has acknowledged that it's a bug and tried to fix it with various updates, but can never seem to eliminate it completely. It also seems like various changes to the WR / CB dynamic have made it more prevalent again this season.

And fyi, we have found at least one example of it happening when going down the screen.

Yeah, but as rare as it is one could make the fake dispute. I've not seen the 'every CB on the field jumps forward' going down yet, but I'll take your word for it.
 
datongw
offline
Link
 
Originally posted by Koncorde
I've never understood the "played CB before" logic. My point highlighted the conflict between GLB and the NFL logic and the fact that there is no advantage in GLB by being further away from the player (i.e. running parallel).


It's not NFL vs GLB, it's football vs GLB. Running parallel is not being further away. Check out when a WR goes in motion, does the CB run parallel with him or does he run up to the LOS? When WR is running toward the sideline when the ball is snapped, running parallel with him will give the CB best angles to react to whatever the WR will do next.

Regarding to the "played CB before" logic, people who never played the position has no idea of what they are talking about most of the time. It's like a guy who has never driven a car trying to teach people how to be a NASCAR driver.
Edited by datongw on Sep 1, 2009 02:01:15
 
Koncorde
offline
Link
 
Originally posted by TrevJo
You're completely on your own on that one. There certainly is an advantage to running parallel, rather than moving toward the line of scrimmage, it is common sense. The many replays of CBs getting stepping forward and getting torched demonstrate why it is disadvantageous to move toward the line of scrimmage.


Sorry to explain that one a bit better:

There is no GLB Logic (where "common sense" is not a rule) that states standing further from a man is a better defensive position. There is NFL logic. There is "no" GLB logic.

And it is disadvantageous to fall for a fake, regardless of the direction you move.

Also it's not feasible for me to test every build or setting without some basis.

Originally posted by jdbolick
Originally posted by Koncorde

I've attempted to point out on numerous occasions where the logic lies in what a CB does, but apparently that's trolling.

No, you're the one and only person arguing that this isn't a problem / bug / whatever. Do you notice that? You're the only person on your side, while everyone else says that you're wrong. And you're not dumb enough to be disagreeing legitimately. You don't believe the bullshit you're spewing, you're just saying it to be antagonistic. So yes, that's trolling. You're making up excuses to frustrate and antagonize people reporting a legitimate bug.

There is no logic in the CB stepping forward at the snap. None. All your excuses have been complete bullshit and every single person who posts in this thread has told you that you're wrong.


Lets be clear here - I believe what is happening is not a "bug". I believe it's a side effect of the faking/failed vision check system that results in an unrealistic outcome. It's not a math error, it's not a conflict of settings or something that is actually hard coded. A fake is a fake is a fake is a fake, and unfortunately in some cases the fake causes a forward step because of a combination of settings.

That doesn't mean I don't believe it doesn't need fixing, only that I can't suggest "yeah, stop everyone stepping forward" as a fix because it's the kind of fix this game has had too many of - i.e. a bullshit one that would likely cause more issues that it fixes (particularly if it hides multiple "bugs" which only return to haunt the game in 3 seasons).

So, yeah, apologies if I am actually trying to establish what the problem and prevailing logic is for each instance but:
A - my bug fixes actually work.
B - my bug fixes don't need fixing 3 seasons later because they aren't hurried in or stupid blanket ideas.

If I was being obstructive I wouldn't be here at all.

As it stands - I still have nothing to go with and I am asking "you" for more examples and details so that I actually have something to run with.
 
jdbolick
offline
Link
 
Originally posted by Koncorde
Lets be clear here - I believe what is happening is not a "bug".

Then you're wasting everyone's time and should stop posting in this thread because Bort already said that this was a bug when he tried to "fix" it in previous seasons. See, this is a case of you trolling. Bort said that it's a bug, every single person who posts in the thread can clearly see that it's a bug, and you're still antagonistically trying to invalidate our complaints. It reminds me of an asshole I dealt with in customer service recently who kept trying to make ridiculous excuses just to keep from acknowledging the fact that I had been overcharged. The guy kept insisting over and over again that I wasn't, even though the facts were clear, and he kept using the excuse that he was "just trying to find out what happened" whenever I got mad about his stalling.

Originally posted by
A fake is a fake is a fake is a fake, and unfortunately in some cases the fake causes a forward step because of a combination of settings.

It's not because of fakes. This bug existed before creative route running.

Originally posted by
That doesn't mean I don't believe it doesn't need fixing, only that I can't suggest "yeah, stop everyone stepping forward" as a fix because it's the kind of fix this game has had too many of - i.e. a bullshit one that would likely cause more issues that it fixes

This is what I mean. This is an absurd, bullshit excuse that you make with no logic or justification whatsoever, simply because you want to be an obstinate ass instead of just acknowledging the problem and a potential fix. Will hard-coding it so that CBs never come forward at the snap eliminate the bug itself? No, and I'm all for the staff continuing to try and figure out why the bug is happening on the test server. But stopping CBs from coming forward on the snap will eliminate the negative effects of the bug, which is the more important issue right now. And you have no evidence whatsoever, or even any logical hypotheticals, to suggest why preventing that forward movement would be bad in any way.

Originally posted by
If I was being obstructive I wouldn't be here at all.

That makes no sense. To be an obstruction you have to be here. And constantly telling people that they're wrong, or that you don't believe something is actually a problem, or that you can't do anything about it until you have all the knowledge in the world are all obstructionist tactics. We can't control your knowledge or lack thereof. We don't have access to the code and can't figure out why something is happening, we only know how it's affecting our teams.


Koncorde, I don't know what you do for a living or if you're even old enough to have a job, but I really hope you're not in any kind of service industry. Behavior like yours hurts businesses because customers get pissed off at your smarmy, obstructionist attitude. You apparently think it's funny to frustrate people complaining about an obvious problem, but in the end it just serves to make customers feel alienated and unwanted.
 
Koncorde
offline
Link
 
The thread CB Step Forward Bug has been merged into this thread
 
Troymk1
offline
Link
 
http://goallineblitz.com/game/replay.pl?game_id=717441&pbp_id=11027609

Seems to me it's a little vision related. If the CB reads the snap (ie jumps it) he suffers from the stepping forward to coverage distance. then is burnt badly by his turning rate versus a WR going straight ahead.

 
Troymk1
offline
Link
 
So what's the fix?

Coverage distance setting doesn't activate till 4 ticks into the play.
 
Robbnva
offline
Link
 
Originally posted by Troymk1
So what's the fix?

Coverage distance setting doesn't activate till 4 ticks into the play.


how do you know? the CB3 has a decent cushion on WR3, so why can't CB1 have the same sort of cushion

is that a created defense play? if so position the CB further away from the line
 
Koncorde
offline
Link
 
See Alerts.
 
Robbnva
offline
Link
 
DAMN FORUM BANNED FOR WHAT?!?!? I DID NOT CALL YOUR MOM A WHORE
 
Page:
 


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