Forum Discussion
Read the full thread.. seriously. not only do i provide examples of the very games you claim to have had no problems with having the exact same issue, but i've also word for word quoted the guys from bioware on their multiplayer livestream... the issue has gone to the frostbite devs, its a frostbite engine issue, and if it is not completely the engine then it was some shoddy front end code that interfaced with it.. either way.. its a frostbite issue.
I am done with this thread now, it is NEVER going to be fixed.. the thread started way back in april and it never even got so much as a work around for the gamers.. nothing.
I'd given up weeks ago of ever seeing a fix/workaround, and this latest news just pretty much signed it for me. I've made my decision what i'm doing about the future IP they are lording, and i'm going to stick to it. whether others do the same is entirely up to them, but i am looking further afield for my next game. I will also not be playing a sequel to a game in a galaxy far, far away.
That may true but it's not DICE games that i am having an issue with and i own all of their Frostbite titles.
They can blame the Frostbite engine all they want. I blame BioWare. It's not DICE that worked on this broken and rushed piece of *. The * thing wasn't even optimized properly until recent patches.
This * is downright pathetic.