It’s a real shame, because there is a really good game here, it’s such a shame that the latest update has screwed it up so bad.
Firstly, the fact that for a stealth game, and after two major updates, that machines can STILL severely glitch and shoot through walls is totally unforgivable. It’s not like you haven’t been told time and time again. What’s the point of having a forum if you don’t listen to your community?
And now… after a 9GB patch, the game is unplayable because every time I go to loot something it crashes to the PS4 blue screen. I mean, who is testing this???
I think I’m done with this game. The shame is, I really don’t want to be. But now I can’t play it, so I have no choice.
I am a ps4 user too and just bought the game yesterday. First day really impressed me, but after the game breaking psych I’m currently digging through the trash to find my receipt (physical copy).
@D3kk Find that receipt bro! Lol! Don’t let them get away with this, making it seem as if this is a complete game and accepting people’s money for it. After this, if they really cared about their community they’d allow refunds after a month from initial purchase. To show us that this update wasn’t just a ploy to pull in new players long enough to pass that refund window. Good luck my dude!
PS4 user here as well. You would think that they would’ve tested this update before releasing it. I just dont get it. After all this time of not playing it because of the bugs and it’s still not fixed. I thank they need to hire an outside source to fix their own game, because apparently they cant do it themselves. I have supported this game from the beginning and the developers,but I just dont know anymore. This game should have never been released yet, but I guess their using us as quality control since they dont have to pay us to test the game which is really sad. Here’s to hoping for another update and then another update to fix that one and so on.
I also am on a PS4 and after the update, the game loads up the Main Menu, and hangs upon choosing the Continue button. The system will hang for a few seconds, trying to load your saved game, but fails and give you a CE-34878-0 error. Sometimes, you will be presented with a option to restore a backup file, which also fails. Who is doing the QA and testing? Is this a Microsoft product…lol. The game is fun to play and I have been enjoying it. Just needs some TLC.
Well, first off, it is not a stealth game, it’s action-adventure and not focused around stealth, even though there is a stealth element to it
secondly, yes, machines clipping and shooting through walls is a major inconvenience and I’m personally pushing towards getting it fixed.
Of course, the crash issue on ps4 is also very frustrating for the affected and it’s being investigated as we speak. Hotfix will be out ASAP.
Thanks for your thoughts!
Well here we go again having to wait on an update to fix a previous update. I just dont understand, what is the deal with them and these updates? The updates have never worked without some kind of complications. Do they even test these things first. One of the things that they said was going to be fixed in this update was the robots clipping through buildings. The few people that were able to play after this update says that the clipping was still present in the game. So what did they update then is what I would like to know. They said they were going to address this in this update, but once again they did not. If they arent going to address an issue than they need to stop putting these issues in their newsletter saying that it’s going to get fixed in the next update, because apparently the problems arent getting fixed. Now we have the game not even playable now…SMH
Im just hoping after the team has finished fixing the ps4 crash (1.05 update) that the saves will still be there and mission progress. Dont want to lose hours of gameplay specially when i just got all golden tier weapons.
@SR_Carni@Zesiir should this post be locked with the release of the PS4 hotfix? It seems there are still problems, but they are being reported separately in new bug posts which makes sense since it is on a new version.
