Ps4 pro, patch 1.3 ruined the game

KHigdon8303 · February 23, 2018, 3:18pm

I do plan on chuggin’ through this playthrough during it’s current state but I can’t wait for later, more optimized playthrough’s of this game

chris67 · February 23, 2018, 3:24pm

No, sorry, you’re not entitled to anything, and that is something you need to understand.

Everyone is grateful that backers have backed up this project, otherwise we wouldn’t have this great game.
But that doesn’t give you the right to request anything, you can suggest and report bugs … respectfully, period.

I’m tired of seeing self entitled gamers think they can say/do everything they want just because they bought a game, that’s not how the world works.

I think it’s important to take a step back and question your motives, we’re talking about a video game after all, “period”.

REKT1 · February 23, 2018, 3:27pm

Admittedly less grass is pretty extreme, however character models with un-rendered clothing, town’s with building’s popping in and cow’s appearing within 50 feet aren’t in my opinion. Lock picking, Archery, Bug’s, Combat Difficulty i have all seen complained about, Im fine with those i just want patch 1.2, i shouldnt hesitate to patch my game’s, that seem’s ridiculous to me.

chris67 · February 23, 2018, 3:28pm

Yes, there are rendering issues, hopefully it gets patched sooner than later.
But I’m still greatly enjoying the game right now, doesn’t bother me that much.

DrFusselpulli · February 23, 2018, 3:31pm

DrFusselpulli · February 23, 2018, 3:44pm

I closed the thread because it is highly missleading. Patch 1.3 is not out yet, for no platform.

You are talking about patch 1.2, which can have different version numbers for different platform and different locations. I assume 1.0.3 or something like this for some playstation regions. This is not Patch 1.3, it is patch 1.2
Patch 1.2.5 is in certification right now, and 1.3 still in production. Nobody can have problems with patch 1.3 yet, because it is not out yet.

Existing patches are 1.1 and 1.2
For computer we released 1.2.5 already in two versions. One 2 days ago, which was causing a new bug, and a repared version of the patch yesterday which was fixing the new bug again.
The fixed version of 1.2.5 is now in the process of certification for consoles.