DirectX Function Error (Nvidia) - Are you actually serious EA? ( 28.03.17 - 21:34 CEST )

[Neo_Bahamut_19]

@Kwobiwan

@Neo_Bahamut_19

@Alabatross

@GrateFuIlDead

@Braddock512
Although I think this is a Nvidia problem, thanks for giving this attention and showing support in efforts to find a simple fix.
I been reporting on Nvidia’s driver bug forums for release 375.63 , and so far no response from them at all .
Rolling back the drivers is one thing I have not tried because BF1 prompts you to update driver in order to continue .
I wanted to use the driver I used for the beta but dont know a work around to that message that pops up when you start BF1.

Nvidia already said they can reproduce the crash on non-Nvidia cards, ball is in DICE’s court.

The ball has been in Dice’s court ever since the emergence of the Frostbite 2.0 Engine. These issues have been plaguing every Battlefield game that has used it. Instead of looking at their own code they like to point fingers and blame everyone else. They’ll never own up to it until people file a class action lawsuit against them for selling a faulty product.

I’ve literally tried everything that has ever been suggested to fix this issue for any Frostbite Engine game. The only game that doesn’t have remotely the issues has been Battlefield 4 ever since the “third string” or “life support” team took over patching, which was after all the DLC was released and they shifted everyone over to Battlefield 1 development. Says a lot that those guys are actually capable of fixing issues, says a lot about the incompetence of the initial dev teams.

At first my crashes were every hour or two, maybe 3. Now I can’t play a single round without crashing, sometimes locking things up so bad I have to hard shutdown. This is literally the only game engine that does this crap too. I have a Steam library of around 200+ games, not a single one has stability issues that I’ve seen. Only my Battlefield collection since Battlefield 3 (Frostbite “2.0”, more like “.0”) has had these issues with the Device Error. This error has been across multiple GPUs, CPUs, motherboards, RAM, HDDs, SSDs, and OSs.

Every single time they try to pass the buck to Nvidia/AMD, or other driver manufacturers and deny all responsibility. Then, once that “third string” gets involved, they magically start to disappear. I think a lot of it is developer pride and arrogance. They refuse to look into their own product. We won’t get a fix for this for another year or two, and then it’ll just silently stop happening.

Uh ? every Frostbite Engine Game?
For me i Played BF Bad Company 2 ; BF 3 ; BF 4 ; Star Wars Battlefront; and i never ever had in this Frostbite Games this Dirext X error. So it is at least for me a BF 1 specific Problem.
God Thanks im Going to vavation for a Week . Hopefully they fix somthing.

MFG

Why don’t you look through the forums for the other games for similar issues, hrm? Ye ol’ “didn’t happen to me so it doesn’t exist” logic you haz.

I even plainly stated that I’ve had those issues, “across multiple GPUs, CPUs, motherboards, RAM, HDDs, SSDs, and OSs” and that “Only my Battlefield collection since Battlefield 3” and that “The ball has been in Dice’s court ever since the emergence of the Frostbite 2.0 Engine”

This issue started cropping up AFTER Bad Company 2, that was still on the Frostbite 1.0 Engine. BF3 was the first on the FB 2.0 E.

Just a few threads:
Battlefield 3: battlelog.battlefield.com/bf3/en/forum/threadview/2955065210854961836/
Battlefield 4: device hung?
Hardline: https://talk.turtlerockstudios.com/t/tell-us-the-status-of-dxgi-device-hung-error/50487
MoH Warfighter: Forums - Battlelog / MOHW

Took me a minute to find just 4 examples of other Frostbite 2.0 Engine games that have the Device Hung issue.