CPU Catching a rebound=ALWAYS fastbreak

[ParisB]

Re: CPU Catching a rebound=ALWAYS fastbreak

Last year we were complaining that cpu didn't run break or play aggressive.
Like the other poster said, its actually not that bad if you prioritize to get back. If you stop them on the initial break, they back off, and then run a play. After a few times they slow it down.

The key is to not switch defenders right away. Thus fixed the O rebounding too.

[lostsoul]

Re: CPU Catching a rebound=ALWAYS fastbreak

i've played two entire games trying to counter this problem including fixing sliders and a myriad of different ways to create a defensive presence/stop. sorry, but you're wrong.

[mythreesons]

Re: CPU Catching a rebound=ALWAYS fastbreak

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.

I understand what you're saying. But after evey missed shot one of your guards will already be near half court or in the other teams front court. I believe it's important for the CPU to detect that someone is there (meaning back). The sprint is from near half court to the opposing teams lane.

THEN come forward and pick up the ball. I believe again that it's important to come on a STRAIGHT line to the ball AND you DONT need to SPRINT. Seriously I'm playing full games now (12 mins) with, on average 10-14 FBP per game. I play on-ball defense 98% of the time AND I don't have issues with offensive rebound being overboard (on average 8-12 per game which reflects the NBA).

Regarding fatiguing your players, you are sprinting no more than their 1 or 2 guard who is pushing the pace. I believe the right stick dribble moves are much more exhausting than a sprint from half-court to the lane.

Slow up the pace on offense and only run when it's there. It's important to manage the games pace, because the CPU feeds off momentum.

[mythreesons]

Re: CPU Catching a rebound=ALWAYS fastbreak

Make sure you don't come forward unless you have a teammate back...

[HisMommaCallHimClay]

Re: CPU Catching a rebound=ALWAYS fastbreak

I'm afraid most of these problems aren't flaws but programmed. This is 2Ks way of basketball. This is how they make the game harder instead of making it more difficult through bball IQ.

Big issues in this game like rebounding and breaks aren't oversights there programmed.

I questioned 2K bball IQ and was attacked by posters only then to have the Czar say they talk to coaches and players(he never said how their feedback was used though, I asked).

What good is all these sliders if the CPU just cheeses to win.

[xSavageAssassinx]

Re: CPU Catching a rebound=ALWAYS fastbreak

I know this may sound crazy but I have put all tehe tendecies on 0 for CPU. And they still play a good game of basketball.

[xSavageAssassinx]

Re: CPU Catching a rebound=ALWAYS fastbreak

Could someone else try this and tell me how it is?
I'm also playing on HOF - Sim Sliders with Tendency on 0

[risewithus56]

Re: CPU Catching a rebound=ALWAYS fastbreak

Well, good news and bad news with 0 tendencies.

I just finished the first quarter (12 minutes) on Pro/Sim sliders with my Blazers against the Jazz, who I picked because they naturally don't run it up and down the court and they have quality big men, so I figured they'd be a good test. What I've noticed is that with every CPU tendency down to 0, it does seem to negate the fast break issue. If they have numbers, great, but it's not there, it's not there.

However, as would be expected, they don't do anything. Once the ball's down the court, they pass it around until someone in the post gets it and maybe forces it up with 3 seconds left. This continued almost every possession, with the ball ending up in the post and then kicked back out until finally something had to happen. I intentionally stopped guarding their perimeter guys and made my defensive settings sag off on-ball and off-ball for every player, but even when confronted with wide open 3's, Mo Williams and Gordon Hayward didn't know what was going on and just dribbled the ball.

What good comes out of it though is that the issue was fixed, albeit with a much larger issue coming from it. However, it seems that the fast break problem can be changed with tendency adjustments, but someone with more knowledge of sliders than me probably needs to do the extensive testing.

Just my 2 cents.

[Bwnarrow3]

Re: CPU Catching a rebound=ALWAYS fastbreak

Boy this is weird. It's like we're playing two different games. I'm seeing a few fast breaks by the computer, but it's nothing more than realistic. I've had no problems with this game besides the lack of non shooting fouls. They even fixed rebounding. This is the best 2K yet IMO

[risewithus56]

Re: CPU Catching a rebound=ALWAYS fastbreak

Boy this is weird. It's like we're playing two different games. I'm seeing a few fast breaks by the computer, but it's nothing more than realistic. I've had no problems with this game besides the lack of non shooting fouls. They even fixed rebounding. This is the best 2K yet IMO

What sliders are you using?

[Zeppelin8]

Re: CPU Catching a rebound=ALWAYS fastbreak

Well, good news and bad news with 0 tendencies.

I just finished the first quarter (12 minutes) on Pro/Sim sliders with my Blazers against the Jazz, who I picked because they naturally don't run it up and down the court and they have quality big men, so I figured they'd be a good test. What I've noticed is that with every CPU tendency down to 0, it does seem to negate the fast break issue. If they have numbers, great, but it's not there, it's not there.

However, as would be expected, they don't do anything. Once the ball's down the court, they pass it around until someone in the post gets it and maybe forces it up with 3 seconds left. This continued almost every possession, with the ball ending up in the post and then kicked back out until finally something had to happen. I intentionally stopped guarding their perimeter guys and made my defensive settings sag off on-ball and off-ball for every player, but even when confronted with wide open 3's, Mo Williams and Gordon Hayward didn't know what was going on and just dribbled the ball.

What good comes out of it though is that the issue was fixed, albeit with a much larger issue coming from it. However, it seems that the fast break problem can be changed with tendency adjustments, but someone with more knowledge of sliders than me probably needs to do the extensive testing.

Just my 2 cents.

Try bumping midrange to 25 and 3pt to 45-50. Slightly better shot variety, maybe its a placebo effect. Lot more 3 pointers for sure, around mid-high 10s low 20s.

But still, I did not like the flow of the offense with adjusted tendencies.

[Bwnarrow3]

Re: CPU Catching a rebound=ALWAYS fastbreak

What sliders are you using?

Default. Raised all non shooting foul sliders to 100 and lowered CPU off rebounding a tad

[Pristy]

Re: CPU Catching a rebound=ALWAYS fastbreak

Boy this is weird. It's like we're playing two different games. I'm seeing a few fast breaks by the computer, but it's nothing more than realistic. I've had no problems with this game besides the lack of non shooting fouls. They even fixed rebounding. This is the best 2K yet IMO

I concur, the fast breaks r far in between for me also. Once you get back on D, the cpu starts to setup up the Off.

[tyberious4now]

Re: CPU Catching a rebound=ALWAYS fastbreak

This is a non issue. Vice versa if the CPU never did a fast break we would make an issue of it..

What gives?

[Serra11]

Re: CPU Catching a rebound=ALWAYS fastbreak

Transition team defensive concepts are completely missing from the game. Nobody stops the ball. No identification of leak outs or "weakside" off-ball players. Guys just seem to run down their predetermined lanes with no awareness of the positioning of the offensive players.

You are completely right YAK but...you can do it by yourself while playing.
As I wrote in vannofhauk'thread,I played my first game with 2k13:
All-star level,48 game speed,12 minutes quarter and default sliders.
Me Miami against the Kings.I chose Sac because their coach profiles(80 pace,85 fastbreak,30 call plays,60 attack the basket).

In my opinion,the cpu run after a defensive rebound only when I've taken a bad shot with poor offensive spacing.So my players weren't in the right place to make a good defensive transition.
The Kings rushed a bit more during the end of the fourth quarter but they were down by 5-6 points,so it is reasonable.

I'm sure that when you YAK will have the time and the will to take a look at this game,you will create something special,better than what you have made with NBA 2K12:wink: