User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Ball lobbed and not even attempted to catch
Page:
 
Wes-Welker
offline
Link
 
The code could be fixed so the reciever with the "best" chance at making the catch goes for it. I'm pretty sure you can code that and it should have been since season 1. No reason at all to not make that play. Whats the point of "vision" if it doesnt work right on a reciever.
Edited by Wes-Welker on Nov 6, 2009 17:09:00
 
Sprocket
offline
Link
 
Originally posted by Wes-Welker
The code could be fixed so the reciever with the "best" chance at making the catch goes for it. I'm pretty sure you can code that and it should have been since season 1. No reason at all to not make that play. Whats the point of "vision" if it doesnt work right on a reciever.


Right. Ive seen it happen IRL, where one receiver makes the catch on the ball targeted for another.

I dont think its a 'Bug' though, but should be a very good suggestion.
 
Gunner65
offline
Link
 
I am no code guru nor have the slightest clue on how to program ... so I have always assumed all the calculations were run first and then the visual representation of that result is shown ... if that is somewhat in the ball park of what happens ... then the play calculations resulted in a bad throw with an incomplete pass ... it was just poorly represented by the visuals ... but ... if that is not how this monstrosity works ... then I have no clue what I am taking about and will return to my corner of GLB and be quiet
 
TrevJo
offline
Link
 
Sprocket, you just don't get it. In GLB the only receiving dot that ever reacts to the ball is the one being targeted. That means one of two things:
A. Only one receiver looks at the QB per play and that's who the QB always throws to...
or B. The current code accounts for a vision check by the targeted receiver but no vision check by non-targeted receivers. Which has nothing to do with dots having a facing or not, whatsoever.

Hint: The answer is B
Edited by TrevJo on Nov 6, 2009 18:48:18
 
KJDCanefan
offline
Link
 
Originally posted by Novus
Yeah, but that one didn't land all that far from the receiver either.

If I was a head coach in real life and saw a WR stand there and make no effort to get to that ball, I'd bench him. Would've been a difficult catch for sure, but you try anyway. And if you're not gonna try, you're not gonna play as far as I'm concerned.

I'd say this is a bug, because I seriously doubt Bort programmed WRs to stand there and watch passes go over their heads.


Sarcasm, its a wonderful tool.
 
mrmattregan
offline
Link
 
Why do people always to make rational comparisons by bringing up what happens in the NFL or College... This is a simulation engine game people. Learn what that is...


 
KJDCanefan
offline
Link
 
Originally posted by mrmattregan
Why do people always to make rational comparisons by bringing up what happens in the NFL or College... This is a simulation engine game people. Learn what that is...




Why do you have to make sense in this fantasy of a game?

 
mwindle
offline
Link
 
Originally posted by jaredcope90
seriously to you sir. the Wr is running a route that appears to be a button up. No it is a button up so its facing somewhere on his frontside, and by that time the ball is near him its common sense that its at least at a catcheable "altitude" going by where it hits the ground.My guess that its is anywhere from the knees to the shoulders.


Another commonly misunderstood thing. The dot doesn't know it's ass from it's face. Meaning there is no back or front. It has a VIS radius and doesn't have any logic as to what is front or behind or to the side. THat's why when fast OTs get out in front on screens they turn around and block a DE that's already out of the play instead of going forward. In a case like that the blocker finds the closest dot to block. Even if that dot is 5 yds behind the play.
 
eaglesfan20
offline
Link
 
Originally posted by TrevJo
All of the receivers continue running their routes (except for the intended receiver, the TE), which is stupid.


and that is the most likely conclusion - the TE was the intended receiver
he was running across the middle of the field and the through was way off target to the outside - very bad throw
so is it possible that the WR was not looking for the ball so he never saw it - because possibly its coded that once a player is targeted all other players know that and then dont respond to the off target throw because they are sure its not coming to them

i have no idea - just a thought/guess



 
Wes-Welker
offline
Link
 
Originally posted by Sprocket
Right. Ive seen it happen IRL, where one receiver makes the catch on the ball targeted for another.

I dont think its a 'Bug' though, but should be a very good suggestion.


Can someone please move this to suggestions?
 
Sprocket
offline
Link
 
Originally posted by TrevJo
Sprocket, you just don't get it. In GLB the only receiving dot that ever reacts to the ball is the one being targeted. That means one of two things:
A. Only one receiver looks at the QB per play and that's who the QB always throws to...
or B. The current code accounts for a vision check by the targeted receiver but no vision check by non-targeted receivers. Which has nothing to do with dots having a facing or not, whatsoever.

Hint: The answer is B


I actually DO get it. Thats what I was saying.

Wasnt I?
Edited by Sprocket on Nov 7, 2009 12:19:34
 
puubescent
offline
Link
 
Everybody is focusing on the O, the D is in this particular example also is oblivious to the 'lame duck'. If the receivers are allowed to adjust, then the D needs to also. After the ball is thrown, the LOLB, FS, SS, and CB all converge on the TE with another CB coming in late. If the WR adjusts and catches that, it's a TD. He should be attempted to be tackled by the SS (judging by his reaction I'm guessing he has enough vision)
 
this_guy1015
offline
Link
 
The defense should switch to the person they see can play on the ball too then.
 
RMiller517
offline
Link
 
Thread locked by moderator.
 
Page:
 


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