DEVROYCE HOF CUSTOM SET (No longer using)

[devroyce]

Quote: Originally Posted by ciaco

Sorry I noticed too late lol... however don't you think the game is a bit too fast? Sent from my SM-G928F using Operation Sports mobile app

No.

1. You can always lower the speed for your own liking.
2. You can test a slower speed and suggest it here and I will test it also.

Sent from my SM-G900T using Operation Sports mobile app

[ciaco]

Quote: Originally Posted by devroyce

No. 1. You can always lower the speed for your own liking. 2. You can test a slower speed and suggest it here and I will test it also. Sent from my SM-G900T using Operation Sports mobile app

Sent from my SM-G928F using Operation Sports mobile app

[meloisa]

I have been playing on game speed of 55 because 57 felt just a touch too quick for my eyes. Not a huge drop, but for me, visually, as well as feel, it has been a solid change I’m sticking with for good.

Oh, and I also dropped user acceleration to 43, as was a suggested test earlier in the thread, it felt great. My last game I won at the buzzer, 108-105, wizards over the hornets. CPU committed 10 fouls and I committed 17. Free throws were 28 attempts for the CPU and 21 for me. Shooting percentages were solid too, I believe 51% for both teams, CPU shot better from downtown 43% to my 38%. I do play user timing, FYI.

Great gameplay, solid stats from my perspective. Just all around solid sliders, really fun to play.


Sent from my iPhone using Tapatalk

[devroyce]

Quote: Originally Posted by ciaco

Sent from my SM-G928F using Operation Sports mobile app

@ciaco What game speed are you using? I'm more than willing to try it.

Sent from my SM-G900T using Operation Sports mobile app

[ciaco]

Quote: Originally Posted by devroyce

@ciaco What game speed are you using? I'm more than willing to try it. Sent from my SM-G900T using Operation Sports mobile app

I'm trying to get used to 57 but I personally believe a 52 is more than enough

Sent from my SM-G928F using Operation Sports mobile app

[devroyce]

Quote: Originally Posted by meloisa

I have been playing on game speed of 55 because 57 felt just a touch too quick for my eyes. Not a huge drop, but for me, visually, as well as feel, it has been a solid change I’m sticking with for good. Oh, and I also dropped user acceleration to 43, as was a suggested test earlier in the thread, it felt great. My last game I won at the buzzer, 108-105, wizards over the hornets. CPU committed 10 fouls and I committed 17. Free throws were 28 attempts for the CPU and 21 for me. Shooting percentages were solid too, I believe 51% for both teams, CPU shot better from downtown 43% to my 38%. I do play user timing, FYI. Great gameplay, solid stats from my perspective. Just all around solid sliders, really fun to play. Sent from my iPhone using Tapatalk

@meloisa Sounds great to me! I will test 55 game speed when I get a chance. It seems like 43 acceleration for the user is a favorite and keeper. And those stats look very good! Thanks for the detailed information.

The only other is user/cpu shooting successes that we all have to agree upon.

***Granted some of us play with user timing and others play with real fg% & maybe i will release separate "shooting success slider sections" for user timing and real fg% to suit all.***

Sent from my SM-G900T using Operation Sports mobile app

[devroyce]

Quote: Originally Posted by ciaco

I'm trying to get used to 57 but I personally believe a 52 is more than enough Sent from my SM-G928F using Operation Sports mobile app

I will try both game speeds of 52 and 55. Thanks.

Sent from my SM-G900T using Operation Sports mobile app

[TheSerbian]

Hey Guys.

I am from Serbia and my english is not the best

So my question is : How to reduce/decrease the CPU Field Goal Attempts ? In real life in NBA the average is about 85 attempts , but in the game the CPU have about 100 attempts.

Difficulty is Hall Of Fame ( Custom )

All Sliders are on 50 for CPU and User , except Movement sliders are Default.

I am thinking about Tendencies to set all to 40 for the CPU.