Originally posted by NWWarrior
Originally posted by MattMan Firespot
Originally posted by pink_panther
Originally posted by PP
Originally posted by DaRealest
Not a bug.
So, when CBs are set to play close and they don't that's not even a bug? How about a CB being so blind, that he can't even tell which WR the ball is being thrown to? Sure, you can make the case that 49.08 V, with 5 in Super V isn't that great yet, but it sure the hell aint bad either...You don't even see that in pee wee ball. hummmmm, tell me, what is that then?
build a better corner.
Cant get much mroe ignorant than that right there lol
There isnt a person in all of GLB that can show me a CB that this same stuff has never happenned to.
QFT
And your right PP....Ken1, Da Realist and theres another guy I cant remember his name right now do nothing but Patrol the Bugs thread and tell people they are either posting in the wrong forum or that they dont know what they are doing, build a better "blank"...ETC, ETC.
They are like BORTs personal thread patrol out to stop anyone and everyone who finds a glaring flaw in this game from talking about it in these forums.
CB coverage is mostly broken in the game right now and needs fixed IMHO. Cb pass deflections that the WR still catches and then runs for a long touchdown is just one of the glaring issues Bort had said he would fix...why not do it now?
Many, many people have the issues with CB coverage distance, not just the few who post in here!!!
A bug is when code is not working as intended. Bort intended to create more realistic outcomes to pass plays, and that's what his code is doing.
Now, these "bugs" were explained:
Originally posted by MattMan Firespot
1-head fake
2-seen this before, looks like the CB misreads the trajectory of the ball
3-same as 2
4-pump fake
5-i would say head fake, but the CB went to his left and jsut stopped, weird
6-pump fake
7-pump[ fake again
Working as intended.
But then someone comes in and claims pass results aren't realistic but "2.5 to 3 yards over the NFL average." And that's just a lie. 6.9 yards per attempt is the NFL average. It's hard to find even a team getting 9.9 yards per attempt, which would be 3 yards over the NFL average.
People got used to CB's playing perfectly in Season 3, and the defensive domination it caused; and so they call it a bug because they can't shut everyone down anymore.
Quoting Bort himself:
Originally posted by Bort
I would like to say, though, that there's a difference between a bug and something you just don't like, and each should be posted in a different place.
Examples:
Bugs, that should be posted in the BUGS forum:
"When I choose cover 2, it kicks a field goal instead."
"When I go to page X, it gives me a 500 server error."
"I tried to create a CB, but it made a G instead."
"When I select close coverage for my CB, he plays 20 yards off his man every time."
Gripes about things that are working as intended but you don't like, that should go to the SUGGESTIONS forum:
"I don't like the zone coverage on this play. Here's what I think it should be instead."
"I think RB's should break fewer tackles. Here's why, and here's what I think a better solution is."
"I think WR's should catch fewer balls. Here's why, and here's what I think a better solution is."
"I don't like this particular restriction on trading. Here's why, and here's what I think would work better."
Gripes about things that are working as intended but you don't like, that should probably not be posted at all:
"My RB doesn't work right! I have no suggestions on why I don't like it or how I think it could work better, but FIX IT."
"WR's suck! I have no suggestions on why they suck or how they could be made to not suck, but FIX IT."
"This game is stupid. FIX IT."
Etc.
Originally posted by MattMan Firespot
Originally posted by pink_panther
Originally posted by PP
Originally posted by DaRealest
Not a bug.
So, when CBs are set to play close and they don't that's not even a bug? How about a CB being so blind, that he can't even tell which WR the ball is being thrown to? Sure, you can make the case that 49.08 V, with 5 in Super V isn't that great yet, but it sure the hell aint bad either...You don't even see that in pee wee ball. hummmmm, tell me, what is that then?
build a better corner.
Cant get much mroe ignorant than that right there lol
There isnt a person in all of GLB that can show me a CB that this same stuff has never happenned to.
QFT
And your right PP....Ken1, Da Realist and theres another guy I cant remember his name right now do nothing but Patrol the Bugs thread and tell people they are either posting in the wrong forum or that they dont know what they are doing, build a better "blank"...ETC, ETC.
They are like BORTs personal thread patrol out to stop anyone and everyone who finds a glaring flaw in this game from talking about it in these forums.
CB coverage is mostly broken in the game right now and needs fixed IMHO. Cb pass deflections that the WR still catches and then runs for a long touchdown is just one of the glaring issues Bort had said he would fix...why not do it now?
Many, many people have the issues with CB coverage distance, not just the few who post in here!!!
A bug is when code is not working as intended. Bort intended to create more realistic outcomes to pass plays, and that's what his code is doing.
Now, these "bugs" were explained:
Originally posted by MattMan Firespot
1-head fake
2-seen this before, looks like the CB misreads the trajectory of the ball
3-same as 2
4-pump fake
5-i would say head fake, but the CB went to his left and jsut stopped, weird
6-pump fake
7-pump[ fake again
Working as intended.
But then someone comes in and claims pass results aren't realistic but "2.5 to 3 yards over the NFL average." And that's just a lie. 6.9 yards per attempt is the NFL average. It's hard to find even a team getting 9.9 yards per attempt, which would be 3 yards over the NFL average.
People got used to CB's playing perfectly in Season 3, and the defensive domination it caused; and so they call it a bug because they can't shut everyone down anymore.
Quoting Bort himself:
Originally posted by Bort
I would like to say, though, that there's a difference between a bug and something you just don't like, and each should be posted in a different place.
Examples:
Bugs, that should be posted in the BUGS forum:
"When I choose cover 2, it kicks a field goal instead."
"When I go to page X, it gives me a 500 server error."
"I tried to create a CB, but it made a G instead."
"When I select close coverage for my CB, he plays 20 yards off his man every time."
Gripes about things that are working as intended but you don't like, that should go to the SUGGESTIONS forum:
"I don't like the zone coverage on this play. Here's what I think it should be instead."
"I think RB's should break fewer tackles. Here's why, and here's what I think a better solution is."
"I think WR's should catch fewer balls. Here's why, and here's what I think a better solution is."
"I don't like this particular restriction on trading. Here's why, and here's what I think would work better."
Gripes about things that are working as intended but you don't like, that should probably not be posted at all:
"My RB doesn't work right! I have no suggestions on why I don't like it or how I think it could work better, but FIX IT."
"WR's suck! I have no suggestions on why they suck or how they could be made to not suck, but FIX IT."
"This game is stupid. FIX IT."
Etc.






























