User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Field Goal Looks good to me, says missed - NOT A BUG - CLOSED
Page:
 
TheGreatPuma
offline
Link
 
Originally posted by VolBrian
Novus has described the way this occurred about as well as possible. That explanation is far more comprehensive than just PBP > Replay, but both are accurate. I understand how it looks and why it can be so upsetting, but it's just not a bug.

Not likely a bug


His explanation doesn't hold water. The OP replay missed FG looks identical to the made FG I linked to. There's really no other way to describe this than PBP > Replay. Perhaps you could argue it hit the crossbar and bounced out, and that part of the bounce is not shown.
Edited by TheGreatPuma on Dec 10, 2010 07:58:39
Edited by TheGreatPuma on Dec 10, 2010 07:58:27
 
VolBrian
Rocky Top
offline
Link
 
Allow me to simplify it further than he did. The goalpost is rendered in 2-D.

So, there is actually no goalpost but in effect a yellow line painted on that spot. The ball will always appear to cross over the goalpost if it does not hit the ground first.

So, if the ball in real life would have been short, but long enough to go under the crossbar in the air, in GLB it will be rendered as going over the crossbar since the crossbar is essentially a yellow line painted on the turf.

Make more sense?
 
Novus
offline
Link
 
Leaving the Flash replays out of this for simplicity's sake... the normal replays are simply a bunch of small GIF images (22 different GIFs for each dot, plus 1 GIF for the football) sliding around on top of a background GIF which represents the field. And since it's just 23 tiny GIFs sliding around on top of 1 big GIF, the 23 tiny GIFs are ALWAYS going to appear on top of the background GIF.

"But Novus! But Novus! When the ball goes up in the air, it gets bigger! And when it comes back down, it gets smaller! Explain that!!!"

Simple. They swap out one football GIF for another, slightly larger one on the fly, and keep swapping out as needed. It's still a tiny GIF sliding around on top of a larger background GIF. It's nothing any more complicated than that.

This is not Madden. This is not a complicated 3-D CG rendering. This is basically like you printing out an overhead photo of a football field, then cutting out a bunch of tiny circles out of construction paper and sliding them all over the photo. And guess what: when you slide your little brown circle (the football) over the part of the photo where the goal posts are, your little brown circle is going to go "over" the goal posts -- even if you're trying to represent the ball going just under the crossbar. Or a ball going OVER the crossbar, for that matter. They're both going to look exactly the same.

It's construction paper circles sliding around on a flat photograph, people. That's it. Again, this ain't Madden.
 
VolBrian
Rocky Top
offline
Link
 
Originally posted by Novus

This is basically like you printing out an overhead photo of a football field, then cutting out a bunch of tiny circles out of construction paper and sliding them all over the photo.


Bort and DD are really Trey Parker and Matt Stone
 
Novus
offline
Link
 
Originally posted by VolBrian
Originally posted by Novus


This is basically like you printing out an overhead photo of a football field, then cutting out a bunch of tiny circles out of construction paper and sliding them all over the photo.


Bort and DD are really Trey Parker and Matt Stone


RESPECT MY AUTHORITAH!!!
 
NiborRis
offline
Link
 
You can look at the page source data to see that it went under the bar if you're so inclined. Just look at the var play_data array and find the entries for the ball near the end of the play.

id: 'ball',x: 88.5,y: 17.25,br: 0,mo: 0,z: 15.5
id: 'ball',x: 88.25,y: 6.5,br: 0,mo: 0,z: 12.5
id: 'ball',x: 87.75,y: -4.25,br: 0,mo: 0,z: 8.75

Since this is going up, the Z height at y=0 is the value you care about. Z needs to be (at least, don't have official word from Bort on that) > 10ft to clear the crossbar.
This is actually really close; just doing some linear math I can show that
17.25 (y-distance to travel until the crossbar) * (6.75 / 21.5) (ratio of z distance dropped per y distance traveled) = 5.42 (z distance dropped before crossbar)
Which is actually a slight bit less than the 5.5 it would take to get below 10ft. However, our math has a few flaws - it's not a linear relationship on the drop speed, and the distances we see are all rounded to the nearest quarter-foot. So 15.5 might mean 15.39, for example.

At any rate, this ball went under. It's hard to see because:
1) The graphics aren't fancy. The goalposts are painted onto the field layer and the ball is drawn on top of them, so even when the ball goes under the goalposts, the ball can't be "drawn" under the crossbar.
2) The view is from straight above, which makes it impossible to watch it float under the bar.

Improving the visual aspect when the ball goes under the crossbar might be a good suggestion? Maybe turn the ball red-outlined or something graphical like that. Also, would be neat for the ball to be able to hit the crossbar and bounce back into the field. *plink* and THAT would be visually obvious.
 
TheGreatPuma
offline
Link
 
Originally posted by VolBrian
Allow me to simplify it further than he did. The goalpost is rendered in 2-D.

So, there is actually no goalpost but in effect a yellow line painted on that spot. The ball will always appear to cross over the goalpost if it does not hit the ground first.

So, if the ball in real life would have been short, but long enough to go under the crossbar in the air, in GLB it will be rendered as going over the crossbar since the crossbar is essentially a yellow line painted on the turf.

Make more sense?


I understand. But there's no way to look at the replay and determine that. You have to simply assume it's short.

Originally posted by NiborRis
You can look at the page source data to see that it went under the bar if you're so inclined. Just look at the var play_data array and find the entries for the ball near the end of the play.

id: 'ball',x: 88.5,y: 17.25,br: 0,mo: 0,z: 15.5
id: 'ball',x: 88.25,y: 6.5,br: 0,mo: 0,z: 12.5
id: 'ball',x: 87.75,y: -4.25,br: 0,mo: 0,z: 8.75

Since this is going up, the Z height at y=0 is the value you care about. Z needs to be (at least, don't have official word from Bort on that) > 10ft to clear the crossbar.
This is actually really close; just doing some linear math I can show that
17.25 (y-distance to travel until the crossbar) * (6.75 / 21.5) (ratio of z distance dropped per y distance traveled) = 5.42 (z distance dropped before crossbar)
Which is actually a slight bit less than the 5.5 it would take to get below 10ft. However, our math has a few flaws - it's not a linear relationship on the drop speed, and the distances we see are all rounded to the nearest quarter-foot. So 15.5 might mean 15.39, for example.

At any rate, this ball went under. It's hard to see because:
1) The graphics aren't fancy. The goalposts are painted onto the field layer and the ball is drawn on top of them, so even when the ball goes under the goalposts, the ball can't be "drawn" under the crossbar.
2) The view is from straight above, which makes it impossible to watch it float under the bar.

Improving the visual aspect when the ball goes under the crossbar might be a good suggestion? Maybe turn the ball red-outlined or something graphical like that. Also, would be neat for the ball to be able to hit the crossbar and bounce back into the field. *plink* and THAT would be visually obvious.


THIS is an explanation I can buy. And looking at the play I linked, the z value for the ball finished at 9.
 
VolBrian
Rocky Top
offline
Link
 
Originally posted by TheGreatPuma
You have to simply assume it's short.


No, not really, this is where the PBP > Replay part comes in. There's no assumption. If the PBP reads it's missed, it's missed and if it's right down the middle, then it was short.
 
TruthHammer
Lead Bugs Mod
offline
Link
 
Originally posted by NiborRis
You can look at the page source data to see that it went under the bar if you're so inclined. Just look at the var play_data array and find the entries for the ball near the end of the play.

id: 'ball',x: 88.5,y: 17.25,br: 0,mo: 0,z: 15.5
id: 'ball',x: 88.25,y: 6.5,br: 0,mo: 0,z: 12.5
id: 'ball',x: 87.75,y: -4.25,br: 0,mo: 0,z: 8.75

Since this is going up, the Z height at y=0 is the value you care about. Z needs to be (at least, don't have official word from Bort on that) > 10ft to clear the crossbar.
This is actually really close; just doing some linear math I can show that
17.25 (y-distance to travel until the crossbar) * (6.75 / 21.5) (ratio of z distance dropped per y distance traveled) = 5.42 (z distance dropped before crossbar)
Which is actually a slight bit less than the 5.5 it would take to get below 10ft. However, our math has a few flaws - it's not a linear relationship on the drop speed, and the distances we see are all rounded to the nearest quarter-foot. So 15.5 might mean 15.39, for example.

At any rate, this ball went under. It's hard to see because:
1) The graphics aren't fancy. The goalposts are painted onto the field layer and the ball is drawn on top of them, so even when the ball goes under the goalposts, the ball can't be "drawn" under the crossbar.
2) The view is from straight above, which makes it impossible to watch it float under the bar.

Improving the visual aspect when the ball goes under the crossbar might be a good suggestion? Maybe turn the ball red-outlined or something graphical like that. Also, would be neat for the ball to be able to hit the crossbar and bounce back into the field. *plink* and THAT would be visually obvious.


Would be cool if the goal posts were above the field as well. Then you could determine how to layer the ball and the goalpost relative to the ball's height.
 
moepoker
offline
Link
 
Originally posted by NiborRis
You can look at the page source data to see that it went under the bar if you're so inclined. Just look at the var play_data array and find the entries for the ball near the end of the play.

id: 'ball',x: 88.5,y: 17.25,br: 0,mo: 0,z: 15.5
id: 'ball',x: 88.25,y: 6.5,br: 0,mo: 0,z: 12.5
id: 'ball',x: 87.75,y: -4.25,br: 0,mo: 0,z: 8.75

Since this is going up, the Z height at y=0 is the value you care about. Z needs to be (at least, don't have official word from Bort on that) > 10ft to clear the crossbar.
This is actually really close; just doing some linear math I can show that
17.25 (y-distance to travel until the crossbar) * (6.75 / 21.5) (ratio of z distance dropped per y distance traveled) = 5.42 (z distance dropped before crossbar)
Which is actually a slight bit less than the 5.5 it would take to get below 10ft. However, our math has a few flaws - it's not a linear relationship on the drop speed, and the distances we see are all rounded to the nearest quarter-foot. So 15.5 might mean 15.39, for example.

At any rate, this ball went under. It's hard to see because:
1) The graphics aren't fancy. The goalposts are painted onto the field layer and the ball is drawn on top of them, so even when the ball goes under the goalposts, the ball can't be "drawn" under the crossbar.
2) The view is from straight above, which makes it impossible to watch it float under the bar.

Improving the visual aspect when the ball goes under the crossbar might be a good suggestion? Maybe turn the ball red-outlined or something graphical like that. Also, would be neat for the ball to be able to hit the crossbar and bounce back into the field. *plink* and THAT would be visually obvious.


wat
 
Skoll Wolfrun
offline
Link
 
Originally posted by RiverRat2
stopped short.
Never crossed the bar


/\ this
 
TheGreatPuma
offline
Link
 
Originally posted by VolBrian
No, not really, this is where the PBP > Replay part comes in. There's no assumption. If the PBP reads it's missed, it's missed and if it's right down the middle, then it was short.


It wasn't right down the middle. It certainly could have hit the upright and bounced out.
 
Catch22
offline
Link
 
Verifying not a bug - can close and notify OP.
 
VolBrian
Rocky Top
offline
Link
 
Originally posted by Catch22
Verifying not a bug - can close and notify OP.


Done
 
Page:
 


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