well, i felt as though i was making some good progress in Tomb Raider: Definitive Edition....then...see picture below...
I was reading about this glitch/bug after it happneded to me, supposedly it is known and common. i was on the portion where Lara jumped from the flaming tower onto the helicopter and just like that...all my progress gone. i had all the updates, so i am supremely frustrated.
Anybody who owns Tomb Raider:Definitive Edition on PS4 should google "TR:DE ps4 save corrupt" and follow the advice. In summary, you want to use all 3 save slots and PS+ cloud save. I didn't and I do not want to start the game over...going on the shelf for now...

That's just wrong.
I just realized that every next gen game i have played has given me a glitch and I've lost all my progress: Battlefield 4 and now TR:DE 
dammit! 
I know, so frustrated...
I had a glitch on that part but you my friend got the bad end of the stick. When I got to that part, it just quit the game altogether. No warning, just like magic,it was at the main PS4 screen. Games are always plagued with glitches sadly, there may be one day there ot but for now we must deal. I remember when Soul Calibur 3 had a corrupt save file one, I was so mad when it happened to me.
It really sucks...I thought I was finishing up too. I am putting it aside for now, no way I want to restart, atleast not at this point.
Ugh, that's awful. I lost saved game progress in Battlefield 4 and I won't go back to the campaign... at least your game was fun until you lost it.
I also had it happen to me in Battlefield 4, so this is 2/2 for me as far as playing a next gen game campaign and losing all my progress. Sucks!
Sorry to hear that. I hope I don't encounter that glitch if I get the game on Steam.
I think it only affects people on PS4, PC should be safe.
Ugh. That's the worst. It's bad enough when you're save gets saved over but this is just cruel.
Yea, I really don't want to start the game over. Sucks because I wanted to see what happened...
Hot damn, I'd be pissed. Shame the patches/updates didn't fix this.
