Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
This is no joke. .
Warsam71 said:Yes I have heard of the issue (i.e. memory leaks, bad or poor memory indexing and calls related to BF4) and it has already been reported to the Driver Team. I'm going to forward your PM to the engineers in a moment to ensure they have as much information as possible.
And will do my best to provide you an update
Thank you Priller
This is not due to user error, which is why I, and many others, are outraged. It has been three months and no word from AMD. This is why I am asking those who are in such a position to bring publicity to this, to do so, as all I am hoping for is some simple acknowledgement that the problem is being worked on. BF4 is a major game; this should not go unresolved and remain unmentioned for three entire months. Even if it's not AMD's fault, they should say something.
This is not an isolated incident, it is as wide spread as it appears.
I am at the point where I doubt I will ever buy another AMD card again, even if nvidia rapes and milks people with their prices and tactics, at least they are quick to resolve and improve issues of mainstream game titles.
0 issues with 7970 and dx11. This is with an intel chip (3570k)
Had zero issues playing bf4 with an r9 290. ZERO.
The only issues I ever had with bf4 was at launch with servers constantly crashing, which wasn't drivers related.
Tony can you post some details. Mantle or DX? Single monitor or Eyefinity, Intel CPU or AMD, How much System Ram? Are you overclocking your cpu or gpu at all? Have you played since the July update?
I don't think the 7000 series have issues with bf4. R200 series is another story.
I doubt that tony, memory leak is real and present with mantle, maybe you just didn't pay enough attention.l to your system ram or gpu load after 3 rounds because that's when it all starts to unfold.
I think tony didn't use mantle. That's why he didn't notice the memory leak. It's possible he may have had the gpu utilization bug but didn't notice it because he was running over 45 fps.
I think tony didn't use mantle. That's why he didn't notice the memory leak. It's possible he may have had the gpu utilization bug but didn't notice it because he was running over 45 fps.
He also said that he ditched his 290 for a nvidia 980 but didn't say why, I ditched my 290 because I wasn't happy with the actual perf for some big name games.
If he honestly and accurately has no issues with the r9 and bf under BOTH mantle and DX, then he will be the first person I have come across to be so lucky to not have an issue. However, I highly doubt it, and I attribute it to poor observation.
He also said that he ditched his 290 for a nvidia 980 but didn't say why, I ditched my 290 because I wasn't happy with the actual perf for some big name games.
To the guy that contacted the AMD rep... anymore feedback? When do they plan on fixing this problem?
I fear this sort of issue is going to become more and more prevalent as Mantle and D3D12 become more widespread. Removing the overhead of older D3D APIs also means that doing what was done in that inefficient, monolithic, catch-all overhead is given to the individual game devs to work out themselves "closer to the metal". This leaves gamers at the mercy of the competence level of the various game studios, rather than being able to blame the shortcomings of Microsoft.
I'm not certain DICE acknowledges that they have any responsibilities. Therein lies the problem...
Better the tedium be absorbed by graphics driver developers than by, in this case, customers.
The issue seems to reside within code specific to their Mantle rendering path, as the leak does not appear to affect the game while running within the D3D code path. If Mantle is as easy to implement as proponents suggest (I've heard "orders of magnitude" easier than high-level graphics APIs like OpenGL), why is DICE creators of "one of the most complex engines" in the industry, and an obviously technically competent group of developers unable to resolve the issue?Well DICE has one of the most complex engines and to keep it to your opinion of making it a driver related bug would be beneficial to whom exactly?
It appears not to be that simple, as there has been an acknowledgement, but no resolution.AMD driver team is not made to backtrack bugs and with Mantle it is simple DICE has to do it.
The issue seems to reside within code specific to their Mantle rendering path, as the leak does not appear to affect the game while running within the D3D code path. If Mantle is as easy to implement as proponents suggest (I've heard "orders of magnitude" easier than high-level graphics APIs like OpenGL), why is DICE creators of "one of the most complex engines" in the industry, and an obviously technically competent group of developers unable to resolve the issue?
It appears not to be that simple, as there has been an acknowledgement, but no resolution.
That's why I told you before that other Mantle engines and the other Frostbite 3 game Plant vs Zombies does not have that problem.The issue seems to reside within code specific to their Mantle rendering path, as the leak does not appear to affect the game while running within the D3D code path. If Mantle is as easy to implement as proponents suggest (I've heard "orders of magnitude" easier than high-level graphics APIs like OpenGL), why is DICE — creators of "one of the most complex engines" in the industry, and an obviously technically competent group of developers — unable to resolve the issue?
It appears not to be that simple, as there has been an acknowledgement, but no resolution.
Gotta love the AMD fanboys...
Mantle is released, and they think it's the second coming of Christ and how it will be the end of DX and NVidia will have to play ball
MS announced DX12 and they claim it's Mantle
Now suddenly, DICE, EA, MS and NVidia have all colluded to cripple AMD cards for a game that's been out for a year now and is actually an AMD launch partner.
It's never AMD's fault is it guys?
What do bugs in the game battlefield 4 have to do with AMD fanboys?