I am getting beyond frustrated at this point. Its been a month and neither AMD or DICE will acknowledge the major issue that a large number of users are experiencing. For those unaware here is the rundown on the issue:
- After playing for a while the game will start stuttering/looping in short intervals making it unplayable. For me it was most likely to happen shortly after a map change and some maps seemed worse than others, (i.e. Rogue Transmission). Others have reported that it seems to happen when there is lots of destruction on a map. If you exit the game (which takes a long time due to the freezing) and then check your memory usage in Windows it will be at 90%+ but with no process showing that its using that memory. Further investigation will show that its in the "Non-paged Pool" of memory. More detailed info here: http://forums.guru3d.com/showthread.php?p=4689663
- The common factors for this issue appear to be people with Windows 8.1 and an AMD 5xxx, 6xxx or 7xxx series video card (not 100% sure on the 7xxx series but the other 2 for sure). So far for me the workaround has been to set the game to run in Windows 7 Compatibility mode. The main change here being that Windows 7 only uses DirectX 11 and Windows 8.1 will use DirectX 11.1. This is likely why Windows 7 users do not experience this issue
NOTE: For those who have the same issue but without the common factors above try this thread: http://www.reddit.com/r/battlefield_4/comments/1r7hd6/windows_8_bf4_memory_leak_the_cause_and_the_fi...
I have issued a bug report to AMD as well but neither side (DICE or AMD) have mentioned even a single word regarding this issue. Keep in mind that just because an AMD driver is affected it does not mean that their driver is the issue and in either case this game was co-marketed between these 2 companies so you'd think both sides would be willing to coordinate and find a fix as fast as possible. It has now been a month with this issue (only recently found the workaround for Windows 7 mode) and I'm just about at my wits end. More so regarding the complete lack of communication/acknowledgement from either DICE/AMD.
On top of that I would be more than willing to do any diagnostics/logging, etc. requested by DICE/AMD to resolve this.
An official response on this issue would be EXTREMELY welcome. Even if its just "We are aware of the issue and are looking into it". At this point I dont even care if its just lip service.
