User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Incomplete passes are really pissing me off.
Page:
 
Enkidu98
offline
Link
 
Originally posted by SCACE
Originally posted by DarkVirtue

Originally posted by Kutzy


Incomplete?
http://goallineblitz.com/game/replay.pl?game_id=167483&pbp_id=7459271

The ball hits him, no pass deflection or drop. Why is this incomplete?

http://goallineblitz.com/game/replay.pl?game_id=167483&pbp_id=7462432
http://goallineblitz.com/game/replay.pl?game_id=167483&pbp_id=7463885
http://goallineblitz.com/game/replay.pl?game_id=167482&pbp_id=6884165


I can find alot more if needed


Yeah those plays are amazingly crazy...Those are better examples of the point I was trying to make Thank you.


There are jumping, diving and 1-hand catch abilities for a reason. Not every ball is thrown perfectly into the numbers.


SCACE, you're an idiot.

I suggest you go read Bort's various posts in http://goallineblitz.com/game/forum_thread.pl?thread_id=1114096.

He says outright there is a problem that is a bug. Balls thrown by QB's with a certain combination of abilities will be thrown with such an arc that when the ball gets to the targeted area and if the ball is not caught, will hit the ground.

Problem is, and BORT said this, the SIM determines that the ball would hit the ground this 'tic' and a such stops the play BEFORE any catch atttempt is made. It is IMPOSSIBLE for the receiver to make a jumping, diving or 1H catch on that ball because the sim says it will hit the ground in that tic and so it stops the play.

Repeat: PER _BORT_ the guy who codes the game. It's a bug!

I normally wouldn;t express such vitriol but your collected contributions to the forums have forced my hand. Really, you don;t know everything dude, so shut the hell up.
 
RAPB
offline
Link
 
Please repeat after Enkidu98:

ALL INCOMPLETE PASSES ARE BUGS PER BORT!

Now sit down and yell at Bort.



While Enkidu sure got a point, I doubt those low level guys got the same problem - especially when they suck at every game they play. Incompletions and bad passes happen. There are more reasons than just "the wrong tic".
 
Enkidu98
offline
Link
 
Oh, I'm certain that there are other bad passes. I throw one a game or more sometimes. There's a certain pattern though to the passes likely affected by this bug and Per Bort they have always been occurring, we're just seeing them more often now because of the higher level folks who can 'force' the situation to occur more frequently.

When the ball goes 'through' the DB's we know the ball is likely over their heads because if it was within their range, they would make a play on the ball. We know as well that when it gets to the receiver, the play stops. This means the ball was not too high for the receiver to catch (jumping catch would resolve) because in these isntances the pbp shows the ball go further downfield before play stops. We know the ball was not too low because the aformentioned moving through the defenders 'aoe' without a play on the ball. Lastly we know the ball wasn't just out of reach of the receiver because in those plays as well, the ball travels beyond the receiver.

I've seen off target passes... passes that were too low (ball doesnt get to receiver at all)... passes that were too high, etc etc. None of them are quite like this pass.

I'm all for incompletes. And if my receivers tried for the ball and failed, I don't care t'all. Its when the sim doesn't even allow for a possible catch because of velocity and angle that's frustrating. Because you throw a perfect pass but get penalised for it.
 
RAPB
offline
Link
 
I'm not sure if the text would report a pass a CB tried to catch but couldn't touch though. It only shows if the ball is actually touched ("deflected by ...") or caught ("intercepted by ..."). So the pass might actually be low - but the CB missed to touch the ball - he got less time to get in the right position and to react.
 
tjsexkitten82
offline
Link
 
I agree with this. When the ball goes over you, to the left of you, to the right of you, or short of you, you can tell. When the ball goes to your loldot and stops, you expect that your loldot was close enough to make a play on the ball. Maybe the ball landed at his feet, that happens occasionally...but this is happening WAY too frequently where the ball stops right at your dot and yet nothing happens, no drop, nothing. Very frustrating, mostly because it's entirely unclear what you need to do to correct it and turn those into completions.
 
Enkidu98
offline
Link
 
Originally posted by RAPB
I'm not sure if the text would report a pass a CB tried to catch but couldn't touch though. It only shows if the ball is actually touched ("deflected by ...") or caught ("intercepted by ..."). So the pass might actually be low - but the CB missed to touch the ball - he got less time to get in the right position and to react.


Oh, I agree... But then again, you'd expect a ball that low to sometimes stop before it reaches the receiver.

They never do. They generally stop right on top of the receivers dot after passing through one or more defenders a good number of times.
 
tjsexkitten82
offline
Link
 
Originally posted by Enkidu98
Originally posted by RAPB

I'm not sure if the text would report a pass a CB tried to catch but couldn't touch though. It only shows if the ball is actually touched ("deflected by ...") or caught ("intercepted by ..."). So the pass might actually be low - but the CB missed to touch the ball - he got less time to get in the right position and to react.


Oh, I agree... But then again, you'd expect a ball that low to sometimes stop before it reaches the receiver.

They never do. They generally stop right on top of the receivers dot after passing through one or more defenders a good number of times.


That's a solid point too. They appear to pass over the CB dot (no deflection, catch, etc.) and yet stop at the WR dot. If they're in the ground, they're clearly not going over the CB's head...so unless they're thrown straight up, it makes no sense.
 
Mike Rogers
Lead Tester
offline
Link
 
So we have a thread where bort is actively posting about this bug, and various people are trying to help fix it.

You post in there, are told that its not the same issue, and then decide that posting a thread with swearing in the title is the best option?

OK your first point, the TE is Not wide open, there are two defenders in his area, and although the dots dont show him in tight coverage, he may well be in tight coverage, the Text indicates that a defended deflected the pass, so it is obviously not the same issue as a Wide Open Incomplete caused by the Code order.

Now there are various other points in this thread that are all raised in the other thread, and many are answered, for example why the ball appears to pass through a DB but the WR cant make a play on it.

I know its hard to follow all the threads so I dont care about most multiple posts in Bugs forum, but you were given an answer in a thread where Bort himself was posting, and decide to create a new one to whine.

This doesnt help to get the bug fixed, all it does is make it look like the reports of Incompletes being bugs are wrong, because you are wrong in this instance, and when told so your being hostile to others.

Flaming never leads to Bort fixing bugs, just saying.

 
Mike Rogers
Lead Tester
offline
Link
 
Originally posted by tjking82
I agree with this. When the ball goes over you, to the left of you, to the right of you, or short of you, you can tell. When the ball goes to your loldot and stops, you expect that your loldot was close enough to make a play on the ball. Maybe the ball landed at his feet, that happens occasionally...but this is happening WAY too frequently where the ball stops right at your dot and yet nothing happens, no drop, nothing. Very frustrating, mostly because it's entirely unclear what you need to do to correct it and turn those into completions.


This is exactly what is being addressed in the original thread.
 
tjsexkitten82
offline
Link
 
Originally posted by Mike Rogers
Originally posted by tjking82

I agree with this. When the ball goes over you, to the left of you, to the right of you, or short of you, you can tell. When the ball goes to your loldot and stops, you expect that your loldot was close enough to make a play on the ball. Maybe the ball landed at his feet, that happens occasionally...but this is happening WAY too frequently where the ball stops right at your dot and yet nothing happens, no drop, nothing. Very frustrating, mostly because it's entirely unclear what you need to do to correct it and turn those into completions.


This is exactly what is being addressed in the original thread.


That seemed to be a study so I didn't want to clutter it with my comments
 
Mike Rogers
Lead Tester
offline
Link
 
Study became a debate. and then a Bort Q&A... which lead to bort trying to find a fix.

Descended into a bitch fest lately though, as no one wants to read a long thread to see what its actually about.
 
RMiller517
offline
Link
 
Thread locked by moderator.
 
Page:
 


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