i thought Zoneblitz had a great topic the other day talking about how some of what the CPU does is realistic and how many of us are just SORE LOSERS 
that said, CPU Cheating has always been a part of NBA 2K. We all know its the easiest way to make the game "harder" and no one wants a game that is too easy, but I think it sticks out more this year because the game is so much harder and turnovers are really hurting alot of us. Secondly, with online play being so bad many of us are being forced to play offline to enjoy the game. I'm doing an article on CPU Cheating and i'd really like you guys to give me your examples. I'm going to be using alot of video (there's no substitute to being able to SEE foolishness--so link your uploads if you have any) so that hopefully that these "cheats" get resolved in the future. I'll also be listing what i perceive as some of the root issues and most of all? FIXES! Some of the things i've noticed:
1) Speed Cheat - yup. still in. you still get run down by CPU defenders unless you have a ridiculous head start. culprit: maybe the CPU has a shorter or automatic acceleration time in regards to going from stand-still to full sprint. fix? DUH. the CPU reaction time when "chasing" needs to slow down.
2. Contact Shots - the cpu shoots alot less of them. especially in the post. rarely will you get a shot in the paint up without a contact animation makign it more difficult. in three games i tracked an average of 44 contact animations in 9 minute quarters. the CPU averaged 16. culprit: again--a fast reaction time as far as shooting. we have a natural delay. fix? slow down the CPU's reaction a bit.
3. Open Shots - the CPU converts a much higher percentage. yes--even on real player percentage. hmmm...isn't that the reason we PUT our setting on real player percentage? so players will hit the shots they do in reality? culprit: a CPU release point that is probably always PERFECT. fix? fix the false advertising. make real player percentage a reality. that or vary the CPU release point to include shots that are too-early and too-late.
4. 50/50 Balls - The CPU not only recovers balls that are up-for-grabs at a too-high rate. it also recovers its own blocked shots, its own deflected passes and loose balls in general. culprit? this seemingly goes back to a faster reaction time and no need to find the ball, but in many instances our CPU defensive players fail to react as fast as the opposing CPU players, why? this may just be a CHEAT. fix? again--slow down the CPU reaction time. or develop an algorithm where the blocks/steals/deflections are recovered by the defending team at a consistent rate, say 7 times in 10--which i'm a fan of.
5. Offensive Rebounds - with the current settings i played 10 games with an Elite Team (Boston) a Solid team (Milwaukee) and a Poor team (Philadelphia) to see if the offensive rebounding by the CPU changed. NO SUCH LUCK. The CPU still won the offensive rebounding battle by a large margin (averaging 10, while i had 4) the culprit? again..that GD preternatural ability to "know" where the ball is going to be and react faster than we can. fix? for years we've been asking for a slider that works.
chime in guys, what examples have you seen?
that said, CPU Cheating has always been a part of NBA 2K. We all know its the easiest way to make the game "harder" and no one wants a game that is too easy, but I think it sticks out more this year because the game is so much harder and turnovers are really hurting alot of us. Secondly, with online play being so bad many of us are being forced to play offline to enjoy the game. I'm doing an article on CPU Cheating and i'd really like you guys to give me your examples. I'm going to be using alot of video (there's no substitute to being able to SEE foolishness--so link your uploads if you have any) so that hopefully that these "cheats" get resolved in the future. I'll also be listing what i perceive as some of the root issues and most of all? FIXES! Some of the things i've noticed:
1) Speed Cheat - yup. still in. you still get run down by CPU defenders unless you have a ridiculous head start. culprit: maybe the CPU has a shorter or automatic acceleration time in regards to going from stand-still to full sprint. fix? DUH. the CPU reaction time when "chasing" needs to slow down.
2. Contact Shots - the cpu shoots alot less of them. especially in the post. rarely will you get a shot in the paint up without a contact animation makign it more difficult. in three games i tracked an average of 44 contact animations in 9 minute quarters. the CPU averaged 16. culprit: again--a fast reaction time as far as shooting. we have a natural delay. fix? slow down the CPU's reaction a bit.
3. Open Shots - the CPU converts a much higher percentage. yes--even on real player percentage. hmmm...isn't that the reason we PUT our setting on real player percentage? so players will hit the shots they do in reality? culprit: a CPU release point that is probably always PERFECT. fix? fix the false advertising. make real player percentage a reality. that or vary the CPU release point to include shots that are too-early and too-late.
4. 50/50 Balls - The CPU not only recovers balls that are up-for-grabs at a too-high rate. it also recovers its own blocked shots, its own deflected passes and loose balls in general. culprit? this seemingly goes back to a faster reaction time and no need to find the ball, but in many instances our CPU defensive players fail to react as fast as the opposing CPU players, why? this may just be a CHEAT. fix? again--slow down the CPU reaction time. or develop an algorithm where the blocks/steals/deflections are recovered by the defending team at a consistent rate, say 7 times in 10--which i'm a fan of.
5. Offensive Rebounds - with the current settings i played 10 games with an Elite Team (Boston) a Solid team (Milwaukee) and a Poor team (Philadelphia) to see if the offensive rebounding by the CPU changed. NO SUCH LUCK. The CPU still won the offensive rebounding battle by a large margin (averaging 10, while i had 4) the culprit? again..that GD preternatural ability to "know" where the ball is going to be and react faster than we can. fix? for years we've been asking for a slider that works.
chime in guys, what examples have you seen?
Comment