3B's are being recorded as 2B's in players' stat lines.
 

3B's are being recorded as 2B's in players' stat lines. Hopefully this glitch can be fixed.

Triples, to be clear, are being recorded as doubles.

They are not.

Not every play where a guy winds up at third base is a triple. It is very possible for a guy hitting a double, but moving to third on a throw to home plate f.e.; check the actual game logs for whatever you think was wrongly scored and you will find out that they are credited with a double in there.

Yes, but if you saw this play that I witnessed just now, you might not be so certain. Man on first, ball hit to deep left center. Runner scores standing up, batter makes it to third by plenty, throw is behind him. Sure looked like a triple to me but it's scored a double (click each image for a larger view):

Here's the ball on the way to the wall:

Attachment 635793

It's off to the races:

Attachment 635794

Here comes the throw:

Attachment 635796

The runner is coming home, the batter is almost at third:

Attachment 635795

The batter has not stopped once, slides into third with the throw behind him, and the runner scores standing up:

Attachment 635797

Sure looks like a triple to me. In case it's an animation issue, here is the code:

**/R21.5667/R18.2333/R17.0333/R20.3333/R20.0333/R22.0333/L23.4333/L24.6333/L20.4000/L30.9667/26.1333/0/0/0/0/\
0, .0000, , 1/, ,
14, .0000, 0/, 2/3/, , 810/.5000/3/1/0/.0000/
1, -0.5556, 1/, , , 4/-0.1777/.0000/2.1504/-1/6/0/0/1.0000/
3, -0.5556, 1/, 4/5/8/9/13/14/15/17/20/21/22/23/28/, , 6.3000/.5200/.0000/.0000/-0.1967/78/0/810/
14, -0.5000, 3/, 6/, , 310/2.0000/12/1/0/.0000/
14, -0.5000, 3/, , , 1010/2.0000/41/1/0/.0000/
0, .1000, 4/, 7/, ,
2, .0000, 6/, 10/11/, , 12/1/3/0/1/.0000/
2, .0000, 3/, 12/, , 13/2/3/0/1/.0000/
7, .0000, 3/, 16/24/29/29/, 10/, 10/0/44/27.0000/148.4800/.0000/.2148/.6394/.4000/1/100/1/0/0/
0, -0.5000, 7/, , ,
2, .0000, 7/, 26/, , 12/2/0/0/1/.0000/
2, .0000, 8/, 25/31/, , 13/3/4/0/1/.0000/
1, .2500, 3/, , , 6/.0000/.0000/.0000/107/0/0/0/.0000/
1, .2500, 3/, 28/, , 7/.0000/.0000/.0000/108/0/0/0/.0000/
14, .5000, 3/, , , 31/.0000/4/1/0/.0000/
20, .0000, 9/, 18/, , 1/
0, .0000, 3/, 18/, 16/,
1, .6000, 17/16/, 19/, , 3/2.1169/.0000/9.7734/-1/0/1/0/.9000/
12, .0000, 18/, , 9/, 3/-1/.1400/
1, 1.0000, 3/, , 9/, 5/.5000/.5000/-1.0000/27/0/1/0/1.0000/
18, .0000, 3/, , 9/, 9/1/0/1/
1, 1.0000, 3/, , 9/, 11/.2148/.9800/-1.0000/38/0/1/0/.5000/
1, .2500, 3/, , 24/9/, 8/.2148/.6394/-1.0000/44/0/1/0/.2000/
20, .0000, 9/, , , 2/
2, .0000, 12/, 32/, , 13/0/2/0/1/.0000/
2, .0000, 11/, 27/, , 12/3/4/0/1/.0000/
14, -0.7000, 26/, , , 12/.0000/12/1/0/.5000/
1, .2500, 3/14/, , , 7/.0000/.0000/.0000/108/0/0/0/.0000/
4, .0000, 9/9/, 30/, 23/31/, 8/-1.0000/149.6000/.2148/.9800/38/1/1/1/204/200/1/
4, .6054, 29/, , 28/26/, 7/-1.0000/.0000/-1.0000/-1.0000/138/2/0/1/204/200/0/
0, 2.0000, 12/, , ,
1, .3000, 25/, , , 13/.2148/.6394/-1.0000/109/1/0/0/1.0000/

Did you sim this game, watch it, or did you play it out? Because I am almost certain that the line in the PBP "Runner from 3rd tries for home…" and so on gives it away. It is the sort of play where when I play my games out in good ol' 2D I will see the guy hit a double, and then get the prompt for whether the lead runner should be sent from third base.

So in this particular case I am near certain that the animation displayed does not match what the game pre-generated for a play, and I think 3D will fool the player easier since it has more "moving parts".

For what it is worth, there are also instances in 2D in every OOTP I played where the flight of the ball does not match what happens in the PBP box and it's actually worse in 20 than f.e. in 16, which I still use to this day for my Raccoons dynasty.

My suspicion that it's a disconnect between play result and 3D animation led me to link to this thread in the 3D player animation / movement issues go here! thread.

I am fine with the play result. I trust the calculations of the game engine much more than I do the 3D animation, much as I esteem and admire the latter. But with this example laid out above, we cannot blame or ignore what the OP said.

I would wish the OP would elaborate on where he sees triples rather than doubles, because those two posts help nobody to find out anything.

Well, OOTPD does a pretty good job about following up on reported animation bugs so I would imagine they will follow my link and look at what I presented here. If that is the type of thing that OP is seeing, it's merely cosmetic and not something to overly worry about. I am sure that my particular play was actually a double, advance to third on a throw, and not what the animation showed me.

If OP has another concern wherein plays are not being recorded in box scores and stats correctly, then he does indeed need to come forward and explain his situation further. Screenshots are always helpful.

In the example shown by Deja Bru, the throw from the outfield was NOT to home plate. It was to the cutoff man who then threw it to 3rd. This is a triple. The runner was safe at 3rd. If the runner was out, different story, he gets a double. This play happens constantly. The animation and the pbp text don't mesh on this play. If like everybody says, the pbp tells the real story of the play, then the animation is the wrong one. The animation is fine, it's just not the right one for this play. To me, though, it would be easier to just change the text.

I assume the animation is the wrong one, because the PBP and the actual scores have always (well, as long as I've been playing) matched up and one seems to feed off the other. Hence, since the animation has more "moving parts", it is prone to be the odd one out.

It would be better to have the full PBP text, but I assume that can't be recovered?

I would very much prefer - actually depend on - the play and the PbP being correct and the animation being "the odd one out." Given OOTPD commitment to quality, I would not think that they would have allowed the game engine to be adversely affected by ongoing development of animation.

So I am fine with the interpretation of "wrong animation applied" especially since OP has not been back to explain his complaint further. I am thinking that he saw the same thing that I did and, based on the visual, looked for a triple instead of what was actually calculated: a double and advance to third on a throw to the plate.

I am pretty sure the animation is wrong if it is the same one I have been seeing. The 2nd baseman in the animation goes to the edge of outfield and acts as relay throwing ball to third. animation should have him playing much nearer to home plate where he can cut off the throw and then throw to third.
The game log says the outfielder threw to third but said it was a double. Game log never mentions the cutoff player throwing to third. I did post my results under technical support, animation issues but I think it may also be a game log issue.

The CF tried to throw out the trailing runner at third, and was unsuccessful. That makes it a triple, straight up.

It wasn't a matter for the runner on second to take third on the throw. He went to third, on his own, and the attempt was made to throw him out.

HAS to be a triple.

Matt in the technical section mentions this play and doing the animation is difficult. States they will be working on animation to better try to show a cutoff and throw back to try to get the trailing runner. Should be scored a double.
I have notice in this instance, and at least one other instance that I know of, the game log and PBP is wrong. The game log in this instance says it was the OF that threw to third, should say SS.
I also have seen runners on 1st and 2nd when batter bunts in the air back to pitcher who then throws to 1st doubling off runner on 1st. PBP and game log both said DP at third.