Patch 2 - CTD problem solved

Most of the posters never had CTD until now, not to mention the graphics have been stripped, scars, freckles and other details are gone, hair looks like glass, scenery is a muddy mess.  Glad you aren't crashing though.

I can only inform you how the patch works on my PC.

But if I had these graphics changes I would try to start a new game from scratch and see how it looks,. I don't think it is a good idea to judge on a save made before the patch (created by a previous *.exe).

There is still plenty of CTD during multiplayer, sometimes with no error given, other times with the DXGI Hung Error.

Reason?

This guy made the patch for Bioware:

https://www.youtube.com/watch?v=_73NU6OlNuw

---

@mushashi7 wrote:

I can only inform you how the patch works on my PC.

But if I had these graphics changes I would try to start a new game from scratch and see how it looks,. I don't think it is a good idea to judge on a save made before the patch (created by a previous *.exe).

---

I think you need to look around on the forums, every poster who has updated are all seeing the same thing, just try adding scars in CC, they don't show anymore, or any other skin textures.  There is a SERIOUS problem with this patch regarding graphics. 

Like I said I am glad it seems to have repaired your crashing issue but it's probably due to them stripping the graphics down for everyone.

Yes, I figured so much. They lowered the pressure on the graphics. And now some will have issues due to this.

I don't run Ultra settings. Just 'High'. And the game loooks great on this setting.

The CTD vanished after the patch. There is no doubt. I've been playing all day and immediately straight after the patch was installed.

I dare say I haven't noticed if the scars have vanished.

Follow up:

The cutscenes play as they should. I still have normal hair, scars and freckles. I didn't notice any missing parts so far.

I only discovered one thing. The game tends to 'stop' for a short moment (half a second or so) during play.
I guess this has something to do with processing information? Maybe a memory limitation/post or pre processing?