But I was W w www r r o nng.
I wasn’t fast enough to catch the 0.4x fps that happened in Execution today to make a pic, but it was like the 10th minute, 2nd map, 2nd half (after changing sides).
Audio stuttering was sss ss s sss ss s oo o ooo o oo o bb bb bb b bb aa a aa a aa aa dd d dd dd, I swear some shit is really on the game.
So i tried a few configs such as texturepoolsize = 1, but it’s didn’t do anything if at all. I did notice in about 24~34ms reduction in latency though so my 180~184ms became 148~150ms.
So Dox told me to put up a thread here and ask the knowledgeables on their take cause we’re going to get bald in fixing something that the rest of the installed games say that everything is OK except of course, DB.
Ticket:#306053
Board: ASUS Z170 Pro Gaming, with onboard intel discrete graphics processor.
CPU: Intel i7-6700K @ 4GHz (4C,8T) operating at factory default
GPU: ASUS ATI Radeon RX480 8GB, not OCed, dynamically ramping clock gpu based on graphics load Driver Ver 17.2.1
RAM: Corsair 32GB DDR4 LPX Vengeance, slightly overclocked to match CPU bus frequency, 8GB reserved for drive cache for super fast loading of whatever textures and whatever is loaded/unloaded frequently as managed by ASUS Ram Cache.
Audio: ASUS Xonar U7, Realtek HD Audio, AMD HD Audio on AOC 2460G4 monitor
OS: Win10 Pro64 to match Intel i7-6700K 64 bit cpu
Keyboard/Mice: Does it really matter?
Before you start thinking of temperature throttling, the CPU and GPU have been monitored and both are well within their nominal operating temperatures despite the onset of spring/summer. Of course the ambient air temp in winter is cooler, but they are still far below their “operating limits that should cause concern”.
So, I suspected previously that the GC in effect (if it is/was in effect) was faulty and thus I stop start DB again and this is how it looks like for reference:
[url = “http://steamcommunity.com/sharedfiles/filedetails/?id=780978276”]reference
I’m actually getting an extra 10~14 fps above the nominal 210fps I normally get, but just today, I got the uber gg gg ggll lll o o oo o r rr rrii iii ooo oo uu sss 0.4 fps.
EDIT:[list=1]
[] added OS in use to comply with TS Rules
[] Tried GPU driver rollback… no change
[] Tried disabling RaptR (as recommended by AMD)… no change
[] Tried stop start DB… performance OK in first 7 minutes and steadily decreasing towards 12 minutes of play.
[] Tried switching to on board Realtek HD Audio instead of Asus XONAR U7; also tried disabling one audio device and enabling using one… no change
[] Tried lowering graphic settings by turning off [list][]Motion Blurr Pause[]Ambient Occlusion[]Anti-Aliasing[]Dynamic Shadows[]Fog Volumes[]Light Shafts[]SH Secondary Lighting[]Bloom[]Depth of Field[]Lens Flares[]Light Shafts[]Dynamic Shadows[]etc[/list] These settings are usually on by default as prescribed by AMD/ATI and the game just looks like 5H1+
[] Tried updating to latest ATI Radeon Crimson Edition driver 16.10.2, then to 16.11.1, 16.11.5, 16.12.1, 17.1.1, 17.2.1… no change. Conclusion: It’s not a firmware problem.
[] Tried reverting to default HUD and performed “Verify integrity of game cache” on STEAM… no change
[] Console command KillAllSounds extended the average play-time by 2~3 minutes, so a very quick Stopwatch game can be played and is possible without hitching. You guys better look at audio garbage collection as well
[] Disabled XBOX_DVR and associated settings in Win10… no change
[] Tried to disable audio enhancements in Win10 as per instructions found here… no change
[] Tried unplugging “redundant pointing devices” from a solution done here… no change
[] Re-configured UE3’s BaseEngine.ini; some audio stutter fixed and a full length stopwatch game is now playable. However after 30mins of gameplay, the same symptoms of audio stuttering and fps dropping persist.
[] It was suggested I backup and delete my Config files, and perform a verify integrity of game cache via steam… no change; still best result was re-configuration of UE3’s base engine which allows me to play up to 30mins.
[] Updated DB wih MOFO update… game lasts a full length stopwatch, but still, at the end of the full length stopwatch, the framerate suffers similar symptoms and I can bet my RX480 that I can still achieve a glorious 1.16 fps or the uber 0.4fps if I push it any further. All the MOFO update did was delay the inevitable. New benchmarks are made using older Gearbox/2K Borderlands 2 and later Ubisoft’s The Division (both are make very stable framerates)
[] Verified integrity of ndis.sys at \Windows\System32\Drivers as a general troubleshooting advice given here, but a binary comparison of the original file with a known source yielded no difference, so the ndis.sys file is intact and not corrupted as suggested in the thread
[] Ran DB as usual, on Task Manager set execution priority of ShooterGame-shipping.exe to High and apply “end process” to BlackCipher.aes… game improved and longer game play. More stable but it takes two long games of Stopwatch to replicate the symptoms
[] Launched DB from AMD/Radeon ATI Crimson driver to see if any pre-video caching will affect any audio/fps stutter… no change
[] Changed power management settings in Win10 as per instructions found here… no change; reverted back
[] Downloaded app suggested here but only marginal gains were observed. It only shows that netcode of ShooterGame32-Shipping.exe is the culprit in making excessive DPC calls or unhandled interrupts causing CPU overloading.
[] Disabled secondary GPU (Intel HD Graphics 530) in Device Manager… no change :s
[] Disabled on board Intel Ethernet i219 system; rebooted; performed STEAM verify integrity of game cache… no change
[] D9D suggested this fix and still, no change. Even my schitt looks better.
[*] Disabled RTS of ESET anti-virus to see if hooked vectors are being picked up by it… no change; reverted back.[/list]
