CPU Catching a rebound=ALWAYS fastbreak

[slimm44]

Re: CPU Catching a rebound=ALWAYS fastbreak

Watching a CPU game between Philly and LAL. Pro/Sim with some tweaks. I will post what I see after defensive rebounds.

Rebound Howard. Pass to Nash. Pass to Kobe on left elbow. Back to Nash top of key. Dribble to left elbow. Pass to Gasol in Post. Shot with 1 second left. Fouled.

Rebound Holiday. Free path to bucket. Dunk.

Rebound Hawes. Pass to Holiday. Fast break opportunity. Missed shot by Turner, tip dunk by Bynum.

Rebound Turner. Outlet to Richardson. Pulls up. Pass to Hawes. Pass to Holiday. PNR. Pass to Richardson. Miss.

Rebound Kobe. Pulls up at 3PT line. Pass to Artest. Pass to Gasol in the post. Double team. Pass to Howard, dunk.

Rebound Gasol. Pass to Nash. Fast break opportunity. Bounce pass to Howard. Dunk.

Rebound Nash. Pass to Kobe. Fast break opportunity. Open lane. Layup.

Rebound Peace. Pass to Kobe. Pass to Peace. Pass to Gasol. Miss.

Rebound Allen. Pass to Holiday. Pull up at top of key. PNR. Pass to Allen. Miss.

Turner rebound. Pull up left elbow. Pass to Richardson. Drive lane. Block by Howard out of bounds.

Rebound Hill. Pass to Kobe. Pass to Nash. Pass to Kobe in Post. Make.

That was the summary of what happens after defensive rebounds through the first quarter. There is 2:21 left but I don't have time to continue. What I'm seeing after defensive rebounds is one of two things are happening - a fast break opportunity by the offense (not forced) or, if the defense gets back, they are setting up freelance situations. Most possessions have several passes but there was also a good amount of PNR action going on, especially by Philly. LAL tended to look for posting players more.

I haven't done this in HUM vs. CPU action, but so far, I can agree that plays aren't being called after defensive rebounds but I have to disagree about this insane fast break/pushing the action gameplay I've read about. I haven't noticed this happening in the HUM vs. CPU games I've played, but I also wasn't watching for it.

[slimm44]

Re: CPU Catching a rebound=ALWAYS fastbreak

After more testing, I've learned a few things.

1. With Play Calling set to 100 under Coaching Profiles, the CPU will usually take 7-8 seconds after a defensive rebound to initiate any plays or freelance situations. I learned this by watching CPU games and setting one team to Coach Mode, turning on Automatic Play Calling, Play Notification Always and Play Art Always. During those 7-8 seconds, the CPU ball handler goes hog-wild, runs to the top of the key, does a few And-1 Mixtape moves, then usually forces a contested shot and misses. I really don't know why I didn't see this before.

2. With Play Calling set to 0 under Coaching Profiles, the CPU will usually take 3-4 seconds after a defensive rebound to initiate plays and will usually run through those plays. Oftentimes, the CPU ball handler will not force the action but will occasionally run a faster paced offense for a few seconds, especially after turnovers or if they have numbers. I'm not sure if this is tied to Offensive Awareness, something different, or a combination of things.

In summary, there is a an issue with the CPU ball handler running out of control after a defensive rebound and it seems to be coded that way. However, setting Call Plays to 0 under Coaching Profiles seems to be a legitimate fix. I have had a few people in a few threads try this and they state that it works, also. I would HIGHLY recommend making this one, simple change before you play another game. There is still A LOT of work to do to make Playbooks/Play Types/Ratings/Tendencies correct, but it can be done.

[wepr3]

Re: CPU Catching a rebound=ALWAYS fastbreak

Hey, slimm. I was intrigued by your theory on turning run plays to 0 for the cpu to combat the fast break issue. I've spent a couple of hours doing some generic testing and wanted to share.

I do think run plays at 0 is related, but I don't think it alone solves the problem. I kept playing against the 76ers: first game, run plays and fast break were at 0. They played very slow, and didn't try to break unless they had a clear advantage. In the second game, I left the ratings as they were - they pushed the ball more, shot quicker, but it wasn't insane. Lastly, I left run plays at 0, but turned up fast break to 100 - it was like Live 10 all over again. Players were going to get to the hoop no matter what, or, it was one pass and a quick shot.

My question to you is, have you tried adjusting the 2 sliders together to see if there's some sort of happy medium? And perhaps there's a formula that we could create to try to replicate the real playing styles of each team? I don't want to put both sliders (run plays/fast break) on 0 and neuter the teams that like to run.

[manustyle90]

Re: CPU Catching a rebound=ALWAYS fastbreak

After more testing, I've learned a few things.

1. With Play Calling set to 100 under Coaching Profiles, the CPU will usually take 7-8 seconds after a defensive rebound to initiate any plays or freelance situations. I learned this by watching CPU games and setting one team to Coach Mode, turning on Automatic Play Calling, Play Notification Always and Play Art Always. During those 7-8 seconds, the CPU ball handler goes hog-wild, runs to the top of the key, does a few And-1 Mixtape moves, then usually forces a contested shot and misses. I really don't know why I didn't see this before.

2. With Play Calling set to 0 under Coaching Profiles, the CPU will usually take 3-4 seconds after a defensive rebound to initiate plays and will usually run through those plays. Oftentimes, the CPU ball handler will not force the action but will occasionally run a faster paced offense for a few seconds, especially after turnovers or if they have numbers. I'm not sure if this is tied to Offensive Awareness, something different, or a combination of things.

In summary, there is a an issue with the CPU ball handler running out of control after a defensive rebound and it seems to be coded that way. However, setting Call Plays to 0 under Coaching Profiles seems to be a legitimate fix. I have had a few people in a few threads try this and they state that it works, also. I would HIGHLY recommend making this one, simple change before you play another game. There is still A LOT of work to do to make Playbooks/Play Types/Ratings/Tendencies correct, but it can be done.

great find here! gonna mix it with my attack the basket experiments...the only thing i need for a good gameplay is cpu running plays when they should!

[slimm44]

Re: CPU Catching a rebound=ALWAYS fastbreak

Hey, slimm. I was intrigued by your theory on turning run plays to 0 for the cpu to combat the fast break issue. I've spent a couple of hours doing some generic testing and wanted to share.

I do think run plays at 0 is related, but I don't think it alone solves the problem. I kept playing against the 76ers: first game, run plays and fast break were at 0. They played very slow, and didn't try to break unless they had a clear advantage. In the second game, I left the ratings as they were - they pushed the ball more, shot quicker, but it wasn't insane. Lastly, I left run plays at 0, but turned up fast break to 100 - it was like Live 10 all over again. Players were going to get to the hoop no matter what, or, it was one pass and a quick shot.

My question to you is, have you tried adjusting the 2 sliders together to see if there's some sort of happy medium? And perhaps there's a formula that we could create to try to replicate the real playing styles of each team? I don't want to put both sliders (run plays/fast break) on 0 and neuter the teams that like to run.

I've used 0 in Call Plays for all teams and have had combinations of Fast Break Tendency at 50 and 75. Haven't went lower or higher than that, yet. I've also used combinations of 50 and 75 for Offensive Tempo. Haven't went lower or higher than that. Teams I've used so far are Philly, LAC, MEM, LAL, and GSW. I'm seeing the CPU run when they should and run sets when they should. Sometimes, after a defensive rebound, they'll still push it but usually only if they have numbers.

[slimm44]

Re: CPU Catching a rebound=ALWAYS fastbreak

great find here! gonna mix it with my attack the basket experiments...the only thing i need for a good gameplay is cpu running plays when they should!

That's something I'm editing now, also. I am watching a game between the Clips and the Warriors. Both teams at 75 Offensive Tempo and 75 Fast Break with 0 in Call Plays. I've edited all players' Drive the Lane and Attack Basket Tendencies to 0, turned the Attack Basket game slider to 0 and turned the Attack Basket slider under Coaching Profiles to 0.

With 9:21 left in the 4th quarter, LAC is up 85 to 71. The team stats follow:

FG% GSW 45 (27-60) LAC 54 (36-66)
3PT% GSW 25 (2-8) LAC 50 (3-6)
FT% GSW 88 (15-17) LAC 71 (10-14)
Dunks 4-6
Fast Break Points 4-16
PIP 28-38
2nd Chance Points 4-10
Bench Points 25-30
Assists 14-19
Offensive Rebounds 3-6
Defensive Rebounds 24-29
Steals 2-3
Blocks 1-4
Turnovers 8-4
Team Fouls 10-11
Biggest Lead 0-19

One thing I think I'm seeing is the AI is programmed to drive the lane/attack the basket at a high rate even with tendencies/sliders at 0. I haven't documented this through testing. It's passing my eye test right now and the stats I'm seeing on a consistent basis are lining up with what I want to see.

[nelsonb24]

Re: CPU Catching a rebound=ALWAYS fastbreak

Where exactly is the Call Plays Slider for the CPUs coach? I've checked every game option & slider & still don't know where this is. I also went to Coaching--> Coach Profiles but I can only change my own head coach's tendencies. Thanks for help

[res2]

Re: CPU Catching a rebound=ALWAYS fastbreak

Where exactly is the Call Plays Slider for the CPUs coach? I've checked every game option & slider & still don't know where this is. I also went to Coaching--> Coach Profiles but I can only change my own head coach's tendencies. Thanks for help

You want to go to Coaching --> Coach Profiles...but you can't edit other team's profiles in association (or season) unless you controll all the teams. You need to make the coaching profile changes before you start your association (or season).

[JZ2]

Re: CPU Catching a rebound=ALWAYS fastbreak

I first started playing on pro sim and remember seeing ppl complain about cpu fast breaks and never seen the cheap fast breaks playing a handful of games. Put settings to allstar and first couple games didn't see any cheap fast breaks either.

I played 2 games tonight and every rebound the cpu fast breaks it. I would make a break for it on defense after every shot and the cpu still would be way ahead of me. I felt part of the reason was the 2k cam when it switches gave the cpu a 1 sec start. Both games the cpu got about 15+ easy baskets this way and I was busting my butt just to hang with them but it was to hard to win with them getting that many easy cheap points.

I just deleted my association in anger. I love losing in sport games, but I hate cheap gameplay. Its a game ruiner and Im thinking about getting rid of the game now.

[slimm44]

Re: CPU Catching a rebound=ALWAYS fastbreak

I first started playing on pro sim and remember seeing ppl complain about cpu fast breaks and never seen the cheap fast breaks playing a handful of games. Put settings to allstar and first couple games didn't see any cheap fast breaks either.

I played 2 games tonight and every rebound the cpu fast breaks it. I would make a break for it on defense after every shot and the cpu still would be way ahead of me. I felt part of the reason was the 2k cam when it switches gave the cpu a 1 sec start. Both games the cpu got about 15+ easy baskets this way and I was busting my butt just to hang with them but it was to hard to win with them getting that many easy cheap points.

I just deleted my association in anger. I love losing in sport games, but I hate cheap gameplay. Its a game ruiner and Im thinking about getting rid of the game now.

Read through the thread. We found the fix, its very easy, and it works very well. Changes the whole game, really.