^That's basically why I'm getting it. It's only ?22 here in Japan.
-
-
Strider this has been ?34 at most places online in the last month. Even GAME had it for ?37 at one point.
Excellent game though and a small price to pay for it, and worth ?25 to flog on if not more at the moment.Comment
-
Does anyone know if this bug hits the XBO version too?Originally posted by MrKirov View PostComment
-
On the 360 version, I was on the beach, looking for crabs to shoot or something and I jumped to climb on one of the rocks.
For some reason, Lara glitched and fell through the rock! She then plummeted for several seconds until eventually to crunched to a halt and died.
Naturally, it caught me by surprise and it was annoying that I did nothing wrong and killed me, but you know exactly what I did when I reloded... I tried it again!
Comment
-
Some advice from the PS forums:
FOR TOMB RAIDER OWNERS in Story mode, a lot of you have had issues with crashes and save file corruption.
The crash that occurs from playing the game was coming from bad programming. That game has been ported to PS4 in a hurry and it is plagued with crashes until Crystal Dynamics release a patch. Several players have experienced identical crashes at identical locations or scenes (that is what makes the "bad programming" a valid hypothesis. Let's call this type of crash "Crash A" (programming issue)
The crash that occurs at the launch of the game when you press continue and select the corrupted save slot is coming from your corrupted save file. Let's call it "Crash B" (due to the attempt of loading a corrupted save file). "Crash B" the worst of all crashes in this game because it prevents you from continuing your progress.
"Crash B" is the result of "Crash A" when "Crash A" occurs during an auto-save. You know you MUST NOT turn off the console while the game is auto-saving otherwise your save is corrupted. Well when "Crash A" occurs during an auto-save, it is exactly like turning off the console during an auto-save. It destroys your save. And Tomb raider is auto-saving almost constantly.
Two different crashes under one same generic error code CE-34878-0
To avoid losing your progress, here is what you have to do:
1/ Just use the 3 save slots every time you save in a camp. Press "options" during the game, choose "change save slot", select a new slot by pressing X on the slot, wait for the TR logo to blink on the bottom right of the screen and do it again until the 3 slots are identical (you can do that with only 2 slots if you want to keep the 3rd for another purpose like missable trophies attempts)
DO NOT FAST TRAVEL TO SHIPWRECK BEACH (complete that level 100% before leaving it). IF YOU FAST TRAVEL TO SHIPWRECK BEACH, THE GAME WILL CRASH AND WILL DESTROY YOUR SAVE (VERY BAD PROGRAMMING).
2/ If the game crashes on you while you are playing (Crash A) and corrupt the save in your current slot, simply reload the game and a save file from another slot. You will only lose the progress from the last save and the moment of crash.
3/ Then from the healthy save, overwrite the corrupted slot (this will be done naturally if you always save on the 3 slots.)
THIS HAS WORKED 100% of the time for me on Tomb Raider D.E. to avoid "Crash B" to occur permanently.Comment
-
Too late for me sadly!Comment
-
I know what I'll be testing when I get home...Comment
-
I fast travelled to Shipreck beach without having got 100% of stuff on there already and all was fine.
I got the save error and blue screen while it was auto-saving in Shantytown.
Hopefully they will think about an update to sort all this out.Comment
-
I envy some next gen owners who can't experience 91%.
That 1% is incredible beautiful, even in ugly 30fps.
Anyway, I've been playing more of this and even 2nd time round my thoughts are the same. The missions are 2 linear and I much prefer the exploratory sections such as the beach and the first wooded area. The QTEs are inconsistent and I often fail them first go the same sections that had me dying repeatedly hadn't been tweaked in this version so I still had a few hiccups of repeated frustration.Comment
-
Does anyone know if you can check your playtime? I am curious how long it took me. (All tombs, but not all items.) I would guess 12 hours, as I was taking it slow and enjoying the environments.Comment
-
Yet again, what has the fact I've hit a save bug due to poor programming have to do with whether its 30fps or 60fps?
I'm slightly confused why a mod is consistently allowed to misquote and bait members so often. Normally I like you Boris, but your blatant fanboyism is beginning to grate quite frankly.
I've had an unfortunate circumstance occur, and your first thought is to have a dig dependant on my current console of choice. Get a grip.Comment
-
The rulez:Originally posted by MrKirov View Post
- Deliberately inciting flame wars for attention, aka Trolling, is obviously not allowed. If you see a thread that is designed to wind people up then please don't reply to it but inform a moderator or administrator of its existence instead.
It's a bit tricky when a Mod decides to bait you isn't it.
Back OT I'm really sorry to read you lost your save, that is seriously crap and if it's any consolation, the last 20% of the game were the worst, almost as if the dev's didn't think anyone would get that far!Comment
-
I'm just winding you up KIrov, sorry if you don't find it funny. Just give me it back!
To be honest If we started pulling people up on the trolling rule we would lose about 50% of the people on this forum.Comment
-
IIRC all of the last section was a big fun battle with silly enemies anyway. It's more that I wasn't able to get all the trophies
All that time grinding in the MP for nothing!!!!!
Never mind, Lightning Returns on Friday
Comment
-
You didn't go for level 60 in multiplayer did you? We were playing last night and gave up when we got to about level 22.
Then ending does go all weird and supernatural though from what I recall, unless I'm getting it confused with Lost.Comment
Comment