"stick in the mud" slider setting

[dlb731]

I'm trying to find the slider that causes the players to not burst off... I.e. the animation will take three steps before the player even moves, or after the turbo is pressed, the reaction time is at least a half a second late... I've adjusted a number of sliders, and changed what I thought might help under the player sliders, but just can't find it.... Any suggestions?

[TheWood56]

Right now I'm playing on 53 game speed with player acceleration and speed sliders at 50. This is probably the happiest I've been player movement wise. I tried increasing acceleration so players would be more explosive but didn't really feel right. Reverted back to keeping both the same at 50. I definitely think 50 game speed or below is too slow animation wise. At 53 I feel the game isn't too fast but it definitely does speed up the animations (dribbling, jump shots, post moves, etc.) and in turn it makes the game feel more responsive to me, which was probably my biggest pet peeve. It felt like whenever I wanted to perform a move, especially dribbling wise, it would take a second or so to perform in the game and a other second or so to branch out of that, meaning instead of reading and reacting to what I'm seeing, I was having to wait for my guy and I felt completely out of control basically. At 53 game speed, whatever you do on the controller plays out faster in game which in turn makes the game feel more responsive which is exactly what I was after.

[Black Bruce Wayne]

Quote: Originally Posted by TheWood56

Right now I'm playing on 53 game speed with player acceleration and speed sliders at 50. This is probably the happiest I've been player movement wise. I tried increasing acceleration so players would be more explosive but didn't really feel right. Reverted back to keeping both the same at 50. I definitely think 50 game speed or below is too slow animation wise. At 53 I feel the game isn't too fast but it definitely does speed up the animations (dribbling, jump shots, post moves, etc.) and in turn it makes the game feel more responsive to me, which was probably my biggest pet peeve. It felt like whenever I wanted to perform a move, especially dribbling wise, it would take a second or so to perform in the game and a other second or so to branch out of that, meaning instead of reading and reacting to what I'm seeing, I was having to wait for my guy and I felt completely out of control basically. At 53 game speed, whatever you do on the controller plays out faster in game which in turn makes the game feel more responsive which is exactly what I was after.

Hmmm ill try this

[TheWood56]

Quote: Originally Posted by Black Bruce Wayne

Hmmm ill try this

I'm testing 52 game speed with 55 acceleration now. Also plays well. I dunno how people play with reduced game speed. The game feels so unresponsive that way and the animations take too long to play out IMO.

[dpower15]

Even 52-53 game speed feels slow to me. I have been testing in the 55-58 range.

The NBA is really fast paced and those dudes are unbelievably explosive. 50 game speed makes it feel like an 8-9 year old rec league game to me


Sent from my iPhone using Tapatalk

[TheWood56]

Quote: Originally Posted by dpower15

Even 52-53 game speed feels slow to me. I have been testing in the 55-58 range. The NBA is really fast paced and those dudes are unbelievably explosive. 50 game speed makes it feel like an 8-9 year old rec league game to me Sent from my iPhone using Tapatalk

Game speed being too high makes it feel arcady and at times out of control for me. With game speed 55-58, do you lower player acceleration and/or speed?

[uforce]

i'll have to try this. I agree with you guys. It's too slow and frustrating.

[mikelow777]

Quote: Originally Posted by TheWood56

Game speed being too high makes it feel arcady and at times out of control for me. With game speed 55-58, do you lower player acceleration and/or speed?

Right now I'm testing game speed at 55, acc at 0/0 and speed at 50/45. The problem is the insane attribute boosting that sometimes becomes the CPU.