v3 Analysis Report lacks Blunder details.

In v2, the Analysis Report on games included lines showing why blunders, mistakes, and inconsistencies were bad.  Often times, I don't know why my blunder was bad.  Like the example shown below, I can't figure out why 28. Re1 was such a blunder on my part.  Without loading it up in to Chessbase or other engine on my own, I can only gander at what I missed.  I used these to learn quite a bit about my own blunders. 

Could you please re-introduce those lines in to v3's analysis?  Thank you.

i see the line in your pic

The line shown is the "Best Move" line - 28. Bf4... .  It does not show why 28. Re1 sucked as much as it did.

but it does.

look at the next move, if it's a good one, that means the second person found out the solution, so you can just look at his moves, if it's not a good move, it will show the better move, which is also the move that shows why your move was bad

I totally see your point but I think its difficult to display everything. For example, Rc1 is likely not bad because of any one line; the computer probably sees 100 (or 1000s) or lines that all contribute to why Rc1 was a bad move. 

I think the best and most eductional way to handle this is to port the pgn over to the computer analysis and explore the move with the engine there. Then you can look at any line you wish that isn't obvious to you. 

I t

Oh, I see.  So Rc2 was the 'best' move.  There.  But, if my opponent had not blundered, I don't think v3's analysis lists the 'Best line' information.

At least in the v2 Analysis Reports we had separate lines shown for both areas -- the Blunder and the Best tangents.

if your opponent had not made a mistake, blunder, or inaccuracy, then he played one of the right moves to win (or not lose). whenever his first wrong move comes, you still know what is the right one

get it? it's a bit confusing

Yeah i totally agree with you spacebux. It would be cool if you could do more stuff so that you can see why the move was so bad. But if chess.com cant do that its totally fine with me

One thing you can do is then load that into self analysis and explore the line!

I will look once more, but I did not see a method in v3 to explore those lines.