CPU Catching a rebound=ALWAYS fastbreak

[engrishbwudd]

Re: CPU Catching a rebound=ALWAYS fastbreak

Raising the hustle slider up to 70 seems to have served as a temporary solution for me. CPU is getting open up court because your A.I. teammates transition with a brisk jog, which results in them getting beat constantly.

[Illustrator76]

Re: CPU Catching a rebound=ALWAYS fastbreak

This issue also happens on Rookie and Pro. As soon as you miss a shot, the CPU will rebound and go on a fast break. They wont slow down and walk up the court and run a play. The CPU goes on a rampage attacking the paint. Try playing the Clippers. Blake Griffin goes on dunking havoc.

Here is a scenario:

Joe Johnson shoots, misses ... DeAndre Jordan rebounds and passes to Chauncey Billups. Billups will sprint up the court full speed, aswell as the CPU team mate; offense appears to be in a fast break mode. Chauncey will attack the basket, if he fails, a bigman will come in and get the offensive board, usually Blake or DeAndre. Standing dunk or inside shot that goes in 90% of the time. I say 90%, because there have been instances where they actually miss.

This bug also works with the User. If you catch a defensive rebound, sprint up court and not run any plays. If you are wide open - SPLASH. MarShon Brooks hit every single three point shot when he had a good look.

This makes the game scripted in a sense and the reason why the game has high FG%. The CPU only makes shots in people's faces following a defensive rebound. If you make a basket, the CPU will inbound, and physics matter. If you play good defense, it matters. The main problem is, when you miss a shot and the CPU rebounds - nothing matters. You need to protect that paint at all costs because the CPU's first priority will get the paint.

Go try this. Intentionally miss shots and watch how the CPU goes on a fast break following a rebound.

YUP, Every single thing you stated is exactly what I am seeing as well.

Raising the hustle slider up to 70 seems to have served as a temporary solution for me. CPU is getting open up court because your A.I. teammates transition with a brisk jog, which results in them getting beat constantly.

Thanks for posting this. I will try this solution as well.

[manustyle90]

Re: CPU Catching a rebound=ALWAYS fastbreak

Raising the hustle slider up to 70 seems to have served as a temporary solution for me. CPU is getting open up court because your A.I. teammates transition with a brisk jog, which results in them getting beat constantly.

tried that same result, long passes, forced transitions and fastbreaks, no plays. i'm already done with this game until 2karcadesports don't fix that (as a pc user i'll have to wait till march for a patch as usual)

[jenglund]

Re: CPU Catching a rebound=ALWAYS fastbreak

Raising the hustle slider up to 70 seems to have served as a temporary solution for me. CPU is getting open up court because your A.I. teammates transition with a brisk jog, which results in them getting beat constantly.

Oh yeah, the Hustle slider. Good call.

This is exactly what I was seeing...I was the Thunder against the Hornets on Pro Sim, and my Thunder teammates are lollygagging down the court while the Hornets are going full speed getting dunk after dunk.

Anybody lowering Attack the Basket tendency as well? I raised 3pt and Mid Range tendency and that's it so far. That helped them take a few more jumpers.

[sword1986]

Re: CPU Catching a rebound=ALWAYS fastbreak

Oh yeah, the Hustle slider. Good call.

This is exactly what I was seeing...I was the Thunder against the Hornets on Pro Sim, and my Thunder teammates are lollygagging down the court while the Hornets are going full speed getting dunk after dunk.

Anybody lowering Attack the Basket tendency as well? I raised 3pt and Mid Range tendency and that's it so far. That helped them take a few more jumpers.

I tried everything. I went into Choose Sides, Coaching Profile and decreased Fast Break slider to 0, increased Run Plays to 100. No avail. CPU still went on a fast break following the defensive rebound.

This is a huge issue and nobody is reporting it, which is a problem - if no one complains about it, the Patch won't even address it. I made a post on the main board. Please go comment. This must get addressed!

[tuck243]

Re: CPU Catching a rebound=ALWAYS fastbreak

I tried everything. I went into Choose Sides, Coaching Profile and decreased Fast Break slider to 0, increased Run Plays to 100. No avail. CPU still went on a fast break following the defensive rebound.

This is a huge issue and nobody is reporting it, which is a problem - if no one complains about it, the Patch won't even address it. I made a post on the main board. Please go comment. This must get addressed!

Have you tried turning down YOUR crash the offensive glass in coaching profile???

But I do see this, NOT often but sometimes... I played on HOF with simulation and was getting whooped by the CPU... I really think Sliders is only for the user not the CPU... I still was getting killed by the Clippers shooting 3's, mid-range, and close contested shots... If they did miss they got the offensive rebound... Here's a stat for y'all... They shot the ball 15 times in the 4th at the 5 minute mark (playing 10 min qt)... They only missed 4 shots... And 3 of them shots were offensive rebounds and put backs or a foul... That mean I only stopped them ONE fawking time in 5 minutes... WOW!!!

Outside of that the gameplay is awesome, they need to patch a lot of this cheese, but I still feel this is the best 2K ever made... It has a ton of potential just a lot of tweaks too...

[youALREADYknow]

Re: CPU Catching a rebound=ALWAYS fastbreak

Have you tried turning down YOUR crash the offensive glass in coaching profile???

It doesn't matter if the CPU has numbers or not, they won't execute a play.

They run the floor looking to do nothing but score or find a shooter. That's the problem.

I thought that this would be similar to 2K12 where Coach Profiles could fix this, but unfortunately it's not.

The only thing I've found to make it slightly better is to drastically improve defensive sliders and increase defensive pressure and help defense across the board to at least force the CPU to pass the ball 1-2 times on missed baskets. That's a half-assed workaround, but it matches the product at this point.

[papaey]

Re: CPU Catching a rebound=ALWAYS fastbreak

i hope 2k would prioritize this issue. Many aspects of the game will be fixed.

If CPU do not go on a rampage in every def. rebound.

1. Less(realistic) Field goal attempts = less(realistic) offensive rebounds
2. less FG% - because you can play defense at the other end.

Believe me 2k. The pace is not a problem. its just how the CPU runs like hell in fastbreak. I FEEL LIKE IM PLAYING NBA LIVE 2006.

[mythreesons]

Re: CPU Catching a rebound=ALWAYS fastbreak

It doesn't matter if the CPU has numbers or not, they won't execute a play.

They run the floor looking to do nothing but score or find a shooter. That's the problem.

I thought that this would be similar to 2K12 where Coach Profiles could fix this, but unfortunately it's not.

The only thing I've found to make it slightly better is to drastically improve defensive sliders and increase defensive pressure and help defense across the board to at least force the CPU to pass the ball 1-2 times on missed baskets. That's a half-assed workaround, but it matches the product at this point.

I posted earlier and stated I had never noticed this (CPU constantly fastbreaking). Well I played against the Clippers (vs Heat) and they toasted me for 30 fast break points out of 53 total points (All-Star/Sim 5 mins qt). Pushing the pace after EVERY missed shot.

So I played them again making a concerted effort to get back on "D" usually with my 1 or 2 guard sprinting all the way back to the rim then coming forward to pick up the ball.

CHECK THIS OUT: They scored 4 FBPs out of a total of 40.

Guys, you don't want to hear this, but the CPU is doing what most real NBA teams will do (at least those with the right personnel): Push the pace and try to score if you don't stop them. Even if the primary break fails they will continue to attack if your defense is still in dis-array. Like I said, you probably don't want to hear it, but you can counter the break, not with sliders, but sound defense. I found that when they were stopped a few times the CPU tended not to do it as often. When they are having success the CPU is merciless and will ram it down your throat.

Not intending to DIS on anyone just relaying my experience.

[Sundown]

Re: CPU Catching a rebound=ALWAYS fastbreak

I posted earlier and stated I had never noticed this (CPU constantly fastbreaking). Well I played against the Clippers (vs Heat) and they toasted me for 30 fast break points out of 53 total points (All-Star/Sim 5 mins qt). Pushing the pace after EVERY missed shot.

So I played them again making a concerted effort to get back on "D" usually with my 1 or 2 guard sprinting all the way back to the rim then coming forward to pick up the ball.

CHECK THIS OUT: They scored 4 FBPs out of a total of 40.

Guys, you don't want to hear this, but the CPU is doing what most real NBA teams will do (at least those with the right personnel): Push the pace and try to score if you don't stop them. Even if the primary break fails they will continue to attack if your defense is still in dis-array. Like I said, you probably don't want to hear it, but you can counter the break, not with sliders, but sound defense. I found that when they were stopped a few times the CPU tended not to do it as often. When they are having success the CPU is merciless and will ram it down your throat.

Not intending to DIS on anyone just relaying my experience.

You might be onto something-- they CPU might just be doing whatever works. There were games that seemed to slow down and turn more into a slug fest once I prioritized getting back on D. Does the CPU reset after a failed fast break though? That I would like to see.

[mythreesons]

Re: CPU Catching a rebound=ALWAYS fastbreak

You might be onto something-- they CPU might just be doing whatever works. There were games that seemed to slow down and turn more into a slug fest once I prioritized getting back on D. Does the CPU reset after a failed fast break though? That I would like to see.

Yes they reset... I even had a few possession (of theirs) that went down to the shot clock countdown [3.. 2.. 1..]. I had to work on "D" though, but they did reset.

I do a lot of hands up on defense (hands down man down); even deflected a few alley-opp attempts. A time or two hands up defense caused misses on FB lay-up attempts.

[Sundown]

Re: CPU Catching a rebound=ALWAYS fastbreak

Yes they reset... I even had a few possession (of theirs) that went down to the shot clock countdown [3.. 2.. 1..]. I had to work on "D" though, but they did reset.

I do a lot of hands up on defense (hands down man down); even deflected a few alley-opp attempts. A time or two hands up defense caused misses on FB lay-up attempts.

Hmm. Is it more effective than block attempts? I have had zero success with block attempts on fast break layups unless my guy was already riding him. Even when they collide in the air, the CPU just slides me out of the way and swishes the layup. There should at least be contact, probably a missed shot, and a foul.

That's a real problem this year-- that their collision engine seems to turn off when any player gets a head of steam and goes into an animation.

[roadman]

Re: CPU Catching a rebound=ALWAYS fastbreak

I posted earlier and stated I had never noticed this (CPU constantly fastbreaking). Well I played against the Clippers (vs Heat) and they toasted me for 30 fast break points out of 53 total points (All-Star/Sim 5 mins qt). Pushing the pace after EVERY missed shot.

So I played them again making a concerted effort to get back on "D" usually with my 1 or 2 guard sprinting all the way back to the rim then coming forward to pick up the ball.

CHECK THIS OUT: They scored 4 FBPs out of a total of 40.

Guys, you don't want to hear this, but the CPU is doing what most real NBA teams will do (at least those with the right personnel): Push the pace and try to score if you don't stop them. Even if the primary break fails they will continue to attack if your defense is still in dis-array. Like I said, you probably don't want to hear it, but you can counter the break, not with sliders, but sound defense. I found that when they were stopped a few times the CPU tended not to do it as often. When they are having success the CPU is merciless and will ram it down your throat.

Not intending to DIS on anyone just relaying my experience.

Doesn't using the turbo button leave your #1 or 2 guard fatigued and coming in and out of the game more?

For me, I don't want my best players, Jennings and Ellis, on the pines after 5 minutes of a sprint fest.

Am I missing something?

Just trying to understand your theory.

[RedPhazon8]

Re: CPU Catching a rebound=ALWAYS fastbreak

The overuse of fast break, the lack of shot distribution when a shooter is not shooting well, and the lack of plays ran by the cpu are probably the only issues I have with the game at this point. I fixed the offensive rebounding, drives, points in the paint, and the horrible defense off screens and picks. Seems to be tougher to fix then I originally thought...

[lostsoul]

Re: CPU Catching a rebound=ALWAYS fastbreak

it's just plain stupid, isn't it - how in the hell did 2k not notice this? this kind of issue deserves immediate attention and patching, even for the pc version. it just ruins the game for me.

the only solution is to switch to the cpu controlled team after they rebound and call a play for them, then switch back to your team. that's no way to play the game...