10.31....Frank Thomas

[lethimroll]

I am new here so forgive me if these have been reported.
The Frank Thomas from the 1960s shows the "Big Frank" Frank Thomas picture, instead of the usual black profile "no photo". Also, in 1910 I played in some insane, but accurate parks. The CF fence was over 600 feet away in Boston, but Tris Speaker hit two homers for me that went 250 feet and landed just behind second base. Both were regular homers, not inside the park.

[HoustonGM]

The Frank Thomas issue is because the game searches for photos based on the first ten letters of the players name, after first searching for the lahman id. If your photos are tagged as the names of the players, and not the lahman id, that is what you'll see.

The second issue, the distances are pretty much just cosmetic and don't mean much of anything, although I do believe Clay's looking into improving all that.

Moved to General Discussion.

[RedsoxRockies]

Yah, Ken Griffey SR. has Juniors pic, as does the old Pedro Bourbon and reliver Pedro Martinez

[Technetium]

Also, in 1910 I played in some insane, but accurate parks. The CF fence was over 600 feet away in Boston, but Tris Speaker hit two homers for me that went 250 feet and landed just behind second base. Both were regular homers, not inside the park.

Happens a lot to me. From what I understand, it doesn't happen in modern-day parks, so I really think it is a bug that has to do with the game improperly making calculations using those extreme center-field distances. Likewise, it only seems to happen when the ball is judged to go around 220-260 ft.

Also, have you noticed a definite pause in the batter's animation sequence when this happens? I can tell it is going to be one of those home runs before the game even tells me the result, simply because of the stutter in the animation that seems to somehow be related to it. It looks to me like the result of the AB is determined at the same time that the animation sequence makes contact with the ball, and that in this case the game is processing a lot more information that it normally would (which would cause it to delay before going to the next frame of the animation).

[RickD]

Also, have you noticed a definite pause in the batter's animation sequence when this happens? I can tell it is going to be one of those home runs before the game even tells me the result, simply because of the stutter in the animation that seems to somehow be related to it. It looks to me like the result of the AB is determined at the same time that the animation sequence makes contact with the ball, and that in this case the game is processing a lot more information that it normally would (which would cause it to delay before going to the next frame of the animation).

Ditto but I think the new unofficial patch makes this less of a stutter. i could be wrong as I have not downloaded the 10.33 but I think it addresses the slowdon stuff.