User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Wide Open Incompletion Case Study - Intended to answer Borts questions about the frequency of this error
Page:
 
Mike Rogers
Lead Tester
offline
Link
 
Originally posted by SCACE
Bukowski - take the douche bag off your eyes and actually read. It takes time to correct or balance a build out. Posting replays is great and all, but I never once said my team had completed the work on all of their builds -- the higher the level, the longer it takes to fix things...thought you had been around long enough to realize that.

Enkidu - you make my case. Sure, if the ball is going to hit the ground, the play will stop as the ball will hit the ground...but in the previous "tick", maybe the ball is about to hit the ground, but it won't on that tick...queue diving catch. Jumping catch & 1-handed catch have nothing to do with the ball being anywhere near the ground.


Scace that is EXACTLY the Bug, the gap between ticks is not enough to allow the option to catch the ball.

Tick 1: Ball is too far away.
Tick 2: Ball is on the ground.

Between the ticks, the ball is perfectly catchable, but the WR never gets a chance to make the play.

The pass can be perfect, but it arrives at the WR between ticks.
Because of the level of builds in the game this season, the combination of the WR speed (Demanding more of a lead on the pass and deeper fade routes) and the QBs strength (Ball moves too fast) are creating this Bug.

This is a direct result of the sim not being able to cope with the spped and strength of higher level builds.

This is NOT people complaining about there players not being perfect every time.

It is players being penalised because their builds exceed the limiltations of the Sim, due to a error in the code.

People should READ THE THREAD, READ BORTS COMMENTS, and stop trying to disprove a Bug that Bort himself has said exsists, and is trying to resolve.

This is not a bitching thread, and its not a thread trying to prove or disprove a bug exsists, that has been done already.

The delay is that we are all waiting for Bort to find a away to resolve the bug, without making passing too powerful.

So far no word on progress, but Bort is working on it last we heard.
Last edited Oct 18, 2008 09:26:41
 
Enkidu98
offline
Link
 
SCACE I suggest you go back deeper in the thread and read Bort. Since the ball moves into 'catching range' on that tic and also will hit the ground _on that tic_ there is no way they will get the chance to catch.

The order of the checks has 'hit the ground?' first.

If its 'hit the ground=yes' then no other check is performed. Meaning it is IMPOSSIBLE to catch those balls.

_impossible_ as in 100% _NO_ catch no matter how many points you have in SA's or attributes.

It doesn't matter if the ball is coming in too low, or if its coming in from a high angle perfectly thrown to go over the defenders heads, etc. Once the ball is in 'catchable' range, it is also going to hit the ground in the same tic.

READ BORT'S EXPLAINATION!

 
Link
 
I don't know SCACE. I'm an outsider to this conversation, and I don't care who wins this argument. It seems to me that you are giving advice without have success following it. It would be one thing for you to say "we did it this way and we are having problems, don't do what we did" but you are telling people to build their players a certain way and you aren't having success. Where is your evidence? I frankly think you are giving dubious advice based on what your idea of how a WR should be built as opposed to what actually works.
 
Link
 
I don't want to read the entire thread. For the folks that have been involved in it: OK, so Bort confirmed the bug. Did he give a timeline on fixing it? Or did he even say he was going to fix it? Don't make me read 27 pages
 
Bukowski
offline
Link
 
Originally posted by phthalatemagic
I don't want to read the entire thread. For the folks that have been involved in it: OK, so Bort confirmed the bug. Did he give a timeline on fixing it? Or did he even say he was going to fix it? Don't make me read 27 pages


Well.. A couple pages (about 4 days) back, he said that he thought he had it figured out. He also said that if he had time, he would implement the changes that night.

But.. He hasn't made another appearance, so we're not exactly sure what's going on.
 
Bukowski
offline
Link
 
Originally posted by phthalatemagic
I don't know SCACE. I'm an outsider to this conversation, and I don't care who wins this argument. It seems to me that you are giving advice without have success following it. It would be one thing for you to say "we did it this way and we are having problems, don't do what we did" but you are telling people to build their players a certain way and you aren't having success. Where is your evidence? I frankly think you are giving dubious advice based on what your idea of how a WR should be built as opposed to what actually works.


Exactly.
 
SCACE
offline
Link
 
Originally posted by Enkidu98
SCACE I suggest you go back deeper in the thread and read Bort. Since the ball moves into 'catching range' on that tic and also will hit the ground _on that tic_ there is no way they will get the chance to catch.

The order of the checks has 'hit the ground?' first.

If its 'hit the ground=yes' then no other check is performed. Meaning it is IMPOSSIBLE to catch those balls.

_impossible_ as in 100% _NO_ catch no matter how many points you have in SA's or attributes.

It doesn't matter if the ball is coming in too low, or if its coming in from a high angle perfectly thrown to go over the defenders heads, etc. Once the ball is in 'catchable' range, it is also going to hit the ground in the same tic.

READ BORT'S EXPLAINATION!



I did read that and all of his responses. It makes sense why he hasn't just reversed the order of the checks re: overpowering passing. All I was saying is that certain attributes and abilities can make a ball catchable earlier in the sequence of ticks. I'm also not lobbying against any change -- if one is required, that is fine -- but I'm glad Bort is taking his time with it vs. appeasing the whines and making something else overpowered.
 
Link
 
Originally posted by Bukowski
Originally posted by phthalatemagic

I don't want to read the entire thread. For the folks that have been involved in it: OK, so Bort confirmed the bug. Did he give a timeline on fixing it? Or did he even say he was going to fix it? Don't make me read 27 pages


Well.. A couple pages (about 4 days) back, he said that he thought he had it figured out. He also said that if he had time, he would implement the changes that night.

But.. He hasn't made another appearance, so we're not exactly sure what's going on.




Ohhh shucks
Last edited Oct 18, 2008 09:41:07
 
Bukowski
offline
Link
 
Originally posted by SCACE
Originally posted by Enkidu98

SCACE I suggest you go back deeper in the thread and read Bort. Since the ball moves into 'catching range' on that tic and also will hit the ground _on that tic_ there is no way they will get the chance to catch.

The order of the checks has 'hit the ground?' first.

If its 'hit the ground=yes' then no other check is performed. Meaning it is IMPOSSIBLE to catch those balls.

_impossible_ as in 100% _NO_ catch no matter how many points you have in SA's or attributes.

It doesn't matter if the ball is coming in too low, or if its coming in from a high angle perfectly thrown to go over the defenders heads, etc. Once the ball is in 'catchable' range, it is also going to hit the ground in the same tic.

READ BORT'S EXPLAINATION!



I did read that and all of his responses. It makes sense why he hasn't just reversed the order of the checks re: overpowering passing. All I was saying is that certain attributes and abilities can make a ball catchable earlier in the sequence of ticks. I'm also not lobbying against any change -- if one is required, that is fine -- but I'm glad Bort is taking his time with it vs. appeasing the whines and making something else overpowered.


Well then maybe your opinion would have been more easily accepted, if you didn't act like you knew the secret remedy, when in fact you're still having the same exact problem as all of us.
 
SCACE
offline
Link
 
Originally posted by phthalatemagic
I don't know SCACE. I'm an outsider to this conversation, and I don't care who wins this argument. It seems to me that you are giving advice without have success following it. It would be one thing for you to say "we did it this way and we are having problems, don't do what we did" but you are telling people to build their players a certain way and you aren't having success. Where is your evidence? I frankly think you are giving dubious advice based on what your idea of how a WR should be built as opposed to what actually works.


I don't know how many more ways I can say that we were caught off guard by this on game 1 and at higher levels that see about 2 level gains per season after boosting, it can't be fixed right away. I've looked at receivers who are having better success under the current system vs. ones that aren't and we're balancing out as we're able to. Our overall completion % has improved over our early season woes, but its still not where we want it.

Regardless, I'm done with this conversation since noone cares to actually have a conversation.
 
SCACE
offline
Link
 
Originally posted by Bukowski
Originally posted by SCACE

Originally posted by Enkidu98


SCACE I suggest you go back deeper in the thread and read Bort. Since the ball moves into 'catching range' on that tic and also will hit the ground _on that tic_ there is no way they will get the chance to catch.

The order of the checks has 'hit the ground?' first.

If its 'hit the ground=yes' then no other check is performed. Meaning it is IMPOSSIBLE to catch those balls.

_impossible_ as in 100% _NO_ catch no matter how many points you have in SA's or attributes.

It doesn't matter if the ball is coming in too low, or if its coming in from a high angle perfectly thrown to go over the defenders heads, etc. Once the ball is in 'catchable' range, it is also going to hit the ground in the same tic.

READ BORT'S EXPLAINATION!



I did read that and all of his responses. It makes sense why he hasn't just reversed the order of the checks re: overpowering passing. All I was saying is that certain attributes and abilities can make a ball catchable earlier in the sequence of ticks. I'm also not lobbying against any change -- if one is required, that is fine -- but I'm glad Bort is taking his time with it vs. appeasing the whines and making something else overpowered.


Well then maybe your opinion would have been more easily accepted, if you didn't act like you knew the secret remedy, when in fact you're still having the same exact problem as all of us.


I never called it a secret remedy, and I've made it quite clear we were caught off guard as well and we are working as a team to try and correct it based on review of builds that aren't having the same issues.
 
Bukowski
offline
Link
 
Originally posted by SCACE
Originally posted by Bukowski

Originally posted by SCACE


Originally posted by Enkidu98



SCACE I suggest you go back deeper in the thread and read Bort. Since the ball moves into 'catching range' on that tic and also will hit the ground _on that tic_ there is no way they will get the chance to catch.

The order of the checks has 'hit the ground?' first.

If its 'hit the ground=yes' then no other check is performed. Meaning it is IMPOSSIBLE to catch those balls.

_impossible_ as in 100% _NO_ catch no matter how many points you have in SA's or attributes.

It doesn't matter if the ball is coming in too low, or if its coming in from a high angle perfectly thrown to go over the defenders heads, etc. Once the ball is in 'catchable' range, it is also going to hit the ground in the same tic.

READ BORT'S EXPLAINATION!



I did read that and all of his responses. It makes sense why he hasn't just reversed the order of the checks re: overpowering passing. All I was saying is that certain attributes and abilities can make a ball catchable earlier in the sequence of ticks. I'm also not lobbying against any change -- if one is required, that is fine -- but I'm glad Bort is taking his time with it vs. appeasing the whines and making something else overpowered.


Well then maybe your opinion would have been more easily accepted, if you didn't act like you knew the secret remedy, when in fact you're still having the same exact problem as all of us.


I never called it a secret remedy, and I've made it quite clear we were caught off guard as well and we are working as a team to try and correct it based on review of builds that aren't having the same issues.


Look, I'm just telling you how we took your comments. And by we, I mean pretty much every other poster that has posted today - other than you. So if EVERYONE kind of had a problem with what you said, then its probably not everyone else with the issue..

Semantics isn't going to get us anywhere.
Last edited Oct 18, 2008 09:48:34
 
Link
 
Originally posted by SCACE
Originally posted by phthalatemagic

I don't know SCACE. I'm an outsider to this conversation, and I don't care who wins this argument. It seems to me that you are giving advice without have success following it. It would be one thing for you to say "we did it this way and we are having problems, don't do what we did" but you are telling people to build their players a certain way and you aren't having success. Where is your evidence? I frankly think you are giving dubious advice based on what your idea of how a WR should be built as opposed to what actually works.


I don't know how many more ways I can say that we were caught off guard by this on game 1 and at higher levels that see about 2 level gains per season after boosting, it can't be fixed right away. I've looked at receivers who are having better success under the current system vs. ones that aren't and we're balancing out as we're able to. Our overall completion % has improved over our early season woes, but its still not where we want it.

Regardless, I'm done with this conversation since noone cares to actually have a conversation.


I don't want you to feel like you are being ganged up on. I'd really like to learn. Help me learn. Can you show me some evidence please? Can you show me that your advice is working? That's all I'm asking for here dude.
 
Bukowski
offline
Link
 
Originally posted by phthalatemagic
Originally posted by SCACE

Originally posted by phthalatemagic


I don't know SCACE. I'm an outsider to this conversation, and I don't care who wins this argument. It seems to me that you are giving advice without have success following it. It would be one thing for you to say "we did it this way and we are having problems, don't do what we did" but you are telling people to build their players a certain way and you aren't having success. Where is your evidence? I frankly think you are giving dubious advice based on what your idea of how a WR should be built as opposed to what actually works.


I don't know how many more ways I can say that we were caught off guard by this on game 1 and at higher levels that see about 2 level gains per season after boosting, it can't be fixed right away. I've looked at receivers who are having better success under the current system vs. ones that aren't and we're balancing out as we're able to. Our overall completion % has improved over our early season woes, but its still not where we want it.

Regardless, I'm done with this conversation since noone cares to actually have a conversation.


I don't want you to feel like you are being ganged up on. I'd really like to learn. Help me learn. Can you show me some evidence please? Can you show me that your advice is working? That's all I'm asking for here dude.


I agree.
 
SCACE
offline
Link
 
Originally posted by phthalatemagic
Originally posted by SCACE

Originally posted by phthalatemagic


I don't know SCACE. I'm an outsider to this conversation, and I don't care who wins this argument. It seems to me that you are giving advice without have success following it. It would be one thing for you to say "we did it this way and we are having problems, don't do what we did" but you are telling people to build their players a certain way and you aren't having success. Where is your evidence? I frankly think you are giving dubious advice based on what your idea of how a WR should be built as opposed to what actually works.


I don't know how many more ways I can say that we were caught off guard by this on game 1 and at higher levels that see about 2 level gains per season after boosting, it can't be fixed right away. I've looked at receivers who are having better success under the current system vs. ones that aren't and we're balancing out as we're able to. Our overall completion % has improved over our early season woes, but its still not where we want it.

Regardless, I'm done with this conversation since noone cares to actually have a conversation.


I don't want you to feel like you are being ganged up on. I'd really like to learn. Help me learn. Can you show me some evidence please? Can you show me that your advice is working? That's all I'm asking for here dude.


I'll have to go through film of some of the WR I looked at who had good (not amazing) speed and agility but spent a lot of training and SP to ensure jumping and vision were also high, and spent SP on the jumping and diving catch SA's -- but I don't have time for that right now. When I reviewed it before, it appeared to me that they were able to "reach" more balls leading to less of these types of incompletions. The logic to me was that if you could increase the overall "catchable" radius for the WR they would make an attempt on balls other receivers would not.

If I'm completely off-base, I'll happily eat crow on this, I've never once thought I was perfect or had all the answers.

To note: my suggestions aren't going to solve the "tick" problem and were never meant to as Bort is working on a way to do that but not make passing overpowered. They were simply based on observations that appeared to increase the ability of a WR to make a play on a ball in a bigger radius.

EDIT: And, as mentioned, the reason I can't show you this from my team is that we made the mistake of boosting before the preseason games as we moved up a league and wanted to get a feel for how tough of a situation we were walking into...and since then, there just hasn't been enough SP to go around to make massive build changes.
Last edited Oct 18, 2008 10:01:44
 
Page:
 


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