|
Quote: |
|
|
|
|
Originally Posted by iameich |
|
|
|
|
|
|
|
|
Charlotte Bobcats (11-35) at Miami Heat (30-14) | Feb 4, 2013 | 1 | 2 | 3 | 4 | Final | Charlotte | 28 | 26 | 21 | 29 | 104 | Miami | 28 | 28 | 21 | 34 | 111 |
Top Performers | Charlotte Bobcats | K.Walker - 30 PTS, 8 AST, 2 STL | | Miami Heat | L.James - 33 PTS, 9 REB, 5 AST, 0 TO | |
| Team Stats Comparison | | CHA | MIA | FG Made-Att | 43-85 | 42-73 | 3PT Made-Att | 3-8 | 7-13 | FT Made-Att | 15-19 | 20-25 | Rebounds | 38 | 38 | Assists | 26 | 24 | Turnovers | 9 | 12 | Steals | 7 | 5 | Blocks | 8 | 5 |
| Charlotte Bobcats | STARTERS | MIN | FG | 3PT | FT | REB | AST | STL | BLK | TO | PTS | K.Walker | 35 | 13-23 | 1-1 | 3-3 | 1 | 8 | 2 | 1 | 0 | 30 | M.Kidd-Gilchrist | 36 | 5-12 | 0-1 | 3-4 | 9 | 2 | 1 | 2 | 1 | 13 | BENCH | MIN | FG | 3PT | FT | REB | AST | STL | BLK | TO | PTS | J.Taylor | 15 | 5-8 | 1-3 | 2-3 | 3 | 1 | 0 | 0 | 0 | 13 |
| Miami Heat | STARTERS | MIN | FG | 3PT | FT | REB | AST | STL | BLK | TO | PTS | L.James | 39 | 14-25 | 0-1 | 5-9 | 9 | 5 | 0 | 0 | 0 | 33 | D.Wade | 35 | 8-15 | 0-0 | 2-2 | 4 | 3 | 0 | 2 | 2 | 18 | C.osh | 33 | 7-11 | 0-1 | 3-4 | 8 | 3 | 1 | 1 | 2 | 17 | BENCH | MIN | FG | 3PT | FT | REB | AST | STL | BLK | TO | PTS | R.Allen | 20 | 4-8 | 2-3 | 4-4 | 2 | 2 | 1 | 0 | 0 | 14 |
|
|
|
|
|
|
|
based on your box scores (FGA) it looks like you slow the game down just a bit & run an offense which (not a fault) causes you to hold the ball sometimes which is when the CPU will swipe if they have a high pressure defense.
it is in fact a "non-fix" issue IMO because if you move that reaching slider down, it will cause them to A) not call enough fouls when needed & B) not get some of the foul calls you see under the basket & on drives because of a reach which in my opinion is VERY much a part of an NBA game flow.
also i HAD to use the reaching slider to somewhat offset & simulate the amount of non-shooting blocking fouls that occur in a game that are just simply impossible to get with any regularity in this game.
and lastly you get the occaional "swing-through" foul calls with this setting IMO... the ones Durant & Kobe get regularly; when a player reaches on a swing through for a jumper.
i've found the r"reaching slider" to be VEEEEEEEERRRRRRRY sensitive & you can see major OVERALL gmae changes in terms of fouls & timing with minimal tweaks & thats why i personally choose to keep them where they are at.
i acknowledge the fact that if you are stationary for too long with certain teams that there will be a unecessary reach in fould but again i say i assume that as the non-shooting blocking fouls that DONT get call (workarounds my friend) & i choose to to be a slight bit more erratic with my gameplay in the first half (like most NBA teams do now days), by not being TOO mythodical with my offense. i play loose & then tighten up my offense in the second half.
generally the CPU gets more aggresive with their ball pressure in the second halves (just as in the real NBA) so with that being said reach ins are also dictated by the users play style & swinging the ball in the second half instead of being stationary may reduce those calls & allow you to see some better looks asa well as getting those FGA up
i didnt think my response would get this long but DAMN good observation & a much needed explaination was warranted.
my suggestion would be to do as i've stated above because of the reasons ive stated above BUT if you simply cant...
lower the reaching foul slider for CPU ONLY, no more than 4 IMO
if you turn down the reaching tendency slider much more than that you will see the CPU be much less effective at getting turnovers & realistic occasion strips & conversely better at keeping you the user from driving.
remember that EVERY slider works in tandem & is converse to another so raising something will ALWAYS decrease something else therefor the key is balance.