Community ManagerJust noticed an older comment mentioning DirectX error crashes and most of the crashes have a DirectX error pop up. I remember one, maybe two, messages (as in only one or two recurring messages), but I can't remember what they said off the top of my head. I don't get crashes if I keep play times short, which can be hard to do because I get hyper-focused.
Community ManagerNameGani Yeah there are a few Direct X errors that happen. Most that I have seen relate to either PhysX or Nvidia drivers. Most are pretty easy to fix, just have to have that exact error.
Welp, it's doing something new now. Made it to the end of playthrough #3 without crashing again, until the post credit statement. Hitting Esc didn't take me back to the main menu like normal, the game just quit on its own, no error. Starting playthrough #4 (I mean, you need at least try all the faction origins and so many builds), it's done it twice more. After the second "fix" in the mission where you meet Bellara (breaking crates using rogue's running hard attack post-fight), and again in the cut-scene where you get the dagger. Just quits, no error; like I used the 3-finger salute (Ctrl+Alt+Del), but I didn't. Game restarts just fine when I get back to it.
Game crashed, as did the EA App / Origin, and I got a screenshot of the DirectX error it threw. This time it was breaking boxes in the Ossuary just before the vial room; know it's not a cut-scene but it's one that's recurring. Honestly can't remember if there's a second one I get as frequently, but...
Community ManagerThanks for the image. This one is hard because it can be due to quite a few issues. The most common ones are Nvidia files. Even if you you, like me have AMD, the game itself still uses Nvidia files.
Check out this link here. It's a different game and the same error, but hopefully, the steps work.
