Inaccurate Statcast Data

[El_MaYiMbE]

Re: Inaccurate Statcast Data

I also hope that sliders do not effect what is actually calculated.

For example, lets say a player runs 20 MPH from 2B to Home with sliders at default. If you adjust the baserunner speed slider, the runner should still be clocked at 20 MPH because even though the runner is technically running faster or slower, it is a global adjustment within the game and the player's "speed" within the context of the game should remain the same.

I would think this is already thought out because it is done properly with pitch speed....but just pointing out something that may have been overlooked.

[thaSLAB]

Re: Inaccurate Statcast Data

I stand corrected. Now what about that 550 foot moonshot Turner hit, or Andrus topping out at 18.5?

Actually, the home run distance argument is based off of too many assumptions too.

Sent from my htc 10 using Tapatalk

[jgb3]

Inaccurate Statcast Data

Actually, the home run distance argument is based off of too many assumptions too.

Sent from my htc 10 using Tapatalk

How is that so? Look at historical data. The closest home run (in EV) at that launch angle was 496 feet. It was 7 mph slower.


Sent from my iPhone using Operation Sports

[Blzer]

Re: Inaccurate Statcast Data

Hopefully these numbers will not only be affected by sliders, but that we can play with sliders until things are fine-tuned to more real life numbers.

In other words, this can probably help us build that more realistic set we've been looking for.

[thaSLAB]

Re: Inaccurate Statcast Data

How is that so? Look at historical data. The closest home run (in EV) at that launch angle was 496 feet. It was 7 mph slower.


Sent from my iPhone using Operation Sports

Not to turn it into a Physics lesson, but you need to know both drag (takes into account air density and wind resistance) and Magnus Force (takes into account rotation and angular velocity) to determine where that ball will land.

It could have well landed 425 feet away. Anyway, this is one assumption made from a short clip containing 2 variables in a much larger equation. I'm just saying...

Sent from my htc 10 using Tapatalk

[Lorne_SCEA]

Re: Inaccurate Statcast Data

Not to turn it into a Physics lesson, but you need to know both drag (takes into account air density and wind resistance) and Magnus Force (takes into account rotation and angular velocity) to determine where that ball will land.

It could have well landed 425 feet away. Anyway, this is one assumption made from a short clip containing 2 variables in a much larger equation. I'm just saying...

Sent from my htc 10 using Tapatalk

...or we used our Autohit widget to make sure the player hit a no doubt home run in order for that display to appear.

[Woodweaver]

Re: Inaccurate Statcast Data

...or we used our Autohit widget to make sure the player hit a no doubt home run in order for that display to appear.

Lorne, you just killed Big Foot. They were just building some steam too...

[HypoLuxa13]

Re: Inaccurate Statcast Data

...or we used our Autohit widget to make sure the player hit a no doubt home run in order for that display to appear.

[Bullit]

Re: Inaccurate Statcast Data

...or we used our Autohit widget to make sure the player hit a no doubt home run in order for that display to appear.

Lorne, you just killed Big Foot. They were just building some steam too...

I love you guys. Its threads like this that really make me appreciate you and this game. Not to mention that you guys come here at all. I am also glad that apparently I am a fan boy and don't see all of these flaws and can just enjoy the game.

[tessl]

Re: Inaccurate Statcast Data

I understand the desire for the game to be 100% reality based but I want a game that works - in manage mode. I'll give an example. Two or three years ago someone discovered the number of cpu chased pitches in the game wasn't as high as IRL. The developers "fixed" the problem by changing it so batters had less of an idea where pitch location was. There were more chased pitches. There were also more called third strikes. More chased pitches and more called third strikes = fewer runs scored. They "fixed" one thing but in manage mode suddenly there were too few runs scored. People joysticking the game probably loved it because cpu hitters were less competent but I hated it.

It's too early to tell for this game but in one video they showed a split screen of the new infielder AI in which Billy Hamilton hit a ground ball to shortstop which bounced 3 times and he was out by 10 feet and the fielder "realistically" sped up his animation due to the fast runner. I'm wondering if infield hits are gone from the game.

Nothing they tinker with happens in a vacuum. When they change one thing it impacts other things. If they strengthen throwing arms then they have to change base runner speed and base runner AI.

I want the game to work. If that means Elroy McFadden IRL throws 85 mph but in the show throws 79 mph as long as the game works I'm fine with it.

[PhantomPain]

Re: Inaccurate Statcast Data

I understand the desire for the game to be 100% reality based but I want a game that works - in manage mode. I'll give an example. Two or three years ago someone discovered the number of cpu chased pitches in the game wasn't as high as IRL. The developers "fixed" the problem by changing it so batters had less of an idea where pitch location was. There were more chased pitches. There were also more called third strikes. More chased pitches and more called third strikes = fewer runs scored. They "fixed" one thing but in manage mode suddenly there were too few runs scored. People joysticking the game probably loved it because cpu hitters were less competent but I hated it.

It's too early to tell for this game but in one video they showed a split screen of the new infielder AI in which Billy Hamilton hit a ground ball to shortstop which bounced 3 times and he was out by 10 feet and the fielder "realistically" sped up his animation due to the fast runner. I'm wondering if infield hits are gone from the game.

Nothing they tinker with happens in a vacuum. When they change one thing it impacts other things. If they strengthen throwing arms then they have to change base runner speed and base runner AI.

I want the game to work. If that means Elroy McFadden IRL throws 85 mph but in the show throws 79 mph as long as the game works I'm fine with it.

My guess, as it can only be a guess at this point, is that infield hits will be harder to come by as they should. If Hamilton hits a routine ground ball and it bounces 3 times (at a very fast rate which it did in that video), he should be thrown out. If it were to do that deep in the hole between SS and 3B, my guess is no matter how quickly they throw he is probably safe. While the video maybe had him out by too many feet, it was still an out like it probably would have been in real life. Like you said, if the game plays right then who cares if he is thrown out by half a step or 10 feet?

Slow choppers to 3rd and a fast runner, my hope is, would be a guess in that sometimes they are out and sometimes not depending on the jump the 3rd baseman has and if he fields it cleanly.

Hits to the hole that a player dives for but can't field it cleanly will likely result in hits as they should. Hits in the hole that a player dives for AND fields it cleanly will also, hopefully, still have a chance to be safe depending on multiple factors.

Those are my guesses/hopes anyway. Doesn't help much since I don't work for SCEA nor do I have the game. Just some thoughts.