I thought 1.16fps was glorious...


(henki000) #21

[left][quote=“K1X455;32829”]
[*] 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.
[/quote]

How did you configure BaseEngine.ini?[/left]


(K1X455) #22

BaseEngine.ini is now called ShooterEngine.ini.

I changed the following parameters under [Engine.Engine] header:[list][]bSmoothFrameRate=FALSE
[
]MinSmoothedFrameRate=92
[*]MaxSmoothedFrameRate=144[/list]

The setting for MinSmoothedFrameRate and MaxSmoothedFrameRate is dependent on your GPU so you must consult your hardware for those settings.


(henki000) #23

@K1X455 didn’t solve my problem. I don’t see any good or harm to my FPS, when I changed those parameters. Maybe we have different issue.


(K1X455) #24

The latest attempts to achieve glory has yielded me this…


(eNkiiz) #25

after uninstalling and reinstalling my game seems to work


(K1X455) #26

Did you uninstall using STEAM? What specific steps did you do to un-install? I might have to bite that nasty bullet for the love of the game, but it could be the last nail.


(Dropdown) #27

Having the same problems. After the mofo update I went from 90 to 120 FPS, but yesterday i started to see a steady decay in fps.
Any solution found yet?


(K1X455) #28

Stop Start DB. Problem goes away instantly. Rinse and repeat. Three times. Makes me salty so quick.

“… there aren’t asterisk in the world to print it…”
- E “Proxy” Wells


(nApeeeboy) #29

Thank God. Atleast now I know im not the only one. just after the update, ive been experiencing game freezing, and it disconnects itself. So I goes back to home screen and I have to join another game again. But this time, it crashes and have to restart pc coz I cant access task manager (ctrl+alt+del)
I also tried lowest settings possible.

If you have something to fix it, please share. Thank you so much.


(Dropdown) #30

Stop Start DB. Problem goes away instantly. Rinse and repeat. Three times. Makes me salty so quick.

“… there aren’t asterisk in the world to print it…”
- E “Proxy” Wells

[/quote]

just start and stop with out getting in to a much, just 3 time, thats it?


(K1X455) #31

There are tell tale symptoms that it will happen. When I hear audio cracking, that means that the DPC has reached a high threshold already and if the game is about to end, I should finish the game, exit DB and start it again.

What could be annoying is that towards the 2nd half of a very good stopwatch match, it will hitch around the 25~28 minute mark and quitting DB will make me forfeit the XP/Credits I have earned. Very very annoying and inconvenient solution, but I got nothing else at the moment. I have listed the things I have done to see if it will work (including choking NGS of processing), yet I still have the same issue since SS III. BTW, have you seen my uber glorious 0.44 fps?


(K1X455) #32

I recently re-opened my ticket again before SD/Nexon forgets about the problem.


(K1X455) #33

check this out

and this was the 31st minute Resource Monitor profile of that game
http://i.imgur.com/lDeDB66.png


(K1X455) #34

here’s Massive/Ubisoft’s Tom Clancy’s The Division game’s comparative DPC Stack/CPU loading Resource Monitor profile.

http://i.imgur.com/rIoUOaL.png


(henki000) #35

Do you have this problem still after they replaced to easyanticheat?

Is it possible, that there is problem with your RAM? Sometimes they can be loosely installed or they don’t match with dual channel slots. You should also try putting your OC settings back to normal.

Try running memtest. http://www.memtest.org/

Then, if there is no problem with RAM, try running Aida64 stress test for half hour. If you have ssd you can untap stress local disk.

Then, I didn’t read your thread completely but if I remember correctly you could crash your OS with dirty bomb. If you could provide your BSOD error message, I would appreciate. You can make them visible in settings or look at your log.

The last thing you could try is to make dual boot windows 7 and try game with drivers installed/completely clean installation.

Then, if the problem still persist. You can try some other game with unreal engine 3, to see if there is any problem. Preferably FPS online game. You can see list here: https://en.wikipedia.org/wiki/List_of_Unreal_Engine_games#Unreal_Engine_3

I hope you can solve your problem with this. Good luck.


(K1X455) #36

There is no problem in terms of hardware. My rig is built brand new by me and my mate, speicifically for running DX12 games (I don’t have any yet, but I might have one soon).

I don’t have Windows7 in 64 bit that will have no hitch with 64bit hardware.

From this thread, you can see that the OP has nearly similar hardware as I have and even his GTX 1080 is suffering from DPC related stacking.

Have you seen this thread?


(henki000) #37

Even if your rig is brand new and everything else works, there can still be factory defect. You might have moved your computer and ram stick might have disconnected. Its not likely, but still there is a chance among every other possible explanation. I have seen those threads now. But how do you explain that the game works with most of us? Even with completely same rig as yours.

You can use Windows 7 64 bit 30 days before you have to activate it with product key. If you have old product key somewhere, you can download it from here:
https://www.microsoft.com/en-us/software-download/windows7


(K1X455) #38

If there were factory deffect(s), it would have shown immediately after bench marking it with Win10 Pro. There was a noticeable white trace on the monitor after a few weeks, but it was promptly replaced by the distributor.

Yes, I have moved it. The POST reveals I have 32GB of DDR4 RAM that is used by Win10. My game loads are tremendously boosted by the amount of RAM I have provided. It also reduces the stress on the hard drives by allowing them to load frequently used data, less frequently.

It’s the same explanation as to why all our other games works perfectly fine, except for Dirty Bomb. The game used to work properly prior to SS III, and after that, SHTF.

[quote=“joyousBowl;c-221958”]You can use Windows 7 64 bit 30 days before you have to activate it with product key. If you have old product key somewhere, you can download it from here:
https://www.microsoft.com/en-us/software-download/windows7
[/quote]I don’t have any Win 7 Pro 64 product key. Care to PM me an authentic one?

Listen, we’ve gone through the hardware, and firmware. Neither of them are at fault. If you have read the threads, changing any of hardware (eg, replace RX480 with GTX 1080), you cannot guarantee that it will go away instantly. What we have narrowed it down to is the netcode of ShooterGame-Win32-Shipping.exe, netcode of ASUS Lan Driver (highly unlikely because other games work perfectly fine), or netcode of the OS(again, highly unlikely because other games work perfectly fine).

Here’s another picture for you to find explanation:
http://i.imgur.com/v29poVk.png

The DPC stacks went in as high as 12 in this picture, and as soon as D9D has exited the game, it vanishes to 0. Notice the cliff of how CPU0 has high processing state going down? What about the rest of the CPUs? In use is a 4 core 8 thread non-overclocked, and perfectly stable desktop game PC. Now, convince me that it’s not ShooterGame-Win32-Shipping.exe that is causing it.


(henki000) #39

Well. There is so much to explain, but also so much work. Have it your way then. If you decide to do tests anyway, maybe we can find solution to your problem.


(K1X455) #40

If you start at one point you’ll get somewhere. In case you haven’t looked at my first post, I did over 20 things to find out what can be done to remedy the situation, and a workable solution was found; annoying as having to interrupt shit coming out of your A55, but workable nonetheless.

You can’t explain the phenomenon can you? How is it that you can speculate finding fault on brand new hardware or firmware, yet you’re willing to ignore empirical evidence? I’m sure you’re just as confused as we are.

Have you even investigated the history of the problem? It’s been on as early as 2013, even back when Windows 7 was on. If you have a remote idea of what could possibly be wrong, you would have understood that it could have been firmware that was the issue as NVidia has made progressive updates to remedy the problem. However, I’m not using NVidia, but rather AMD ATI Radeon. It was one of the deciding factors why I chose to avoid the NVidia product line when we built this desktop; it’s because of this. How do you even know if it’s not server side related? It probably isn’t and it is more Windows related but stress testing the hardware is a waste of time as previous checks reveals all hardware/firmware are functioning nominally as expected. Using Latencymon app, the basis of the tests should encompass all other applications that has high processing requirements.

So despite my frustration with The Division for their lack of direction in gameplay, I was asked by friends to help them to power level. I took the opportunity to monitor my DPC for over two hours of playing and it yielded the same result as I have earlier posted, so no point of putting in a new profile (including very high use of Discord). This involved being connected to a server in Asia and the latency was relatively high, but no issues when it comes to DPC, graphic corruption or anything technical beyond our ability to resolve it. They are although on different game engines, one is more efficient & effective at resource management.

I have new findings regarding this matter. The Windows file wdf01000.sys is making the highest reported ISR (Interrupt Service Routine) and is a probable cause to the audio stuttering. Whether it is ShooterGame-Win32-Shipping.exe or Coherent_UI.exe that is making the calls to wdf01000.sys, we are yet to ascertain. I have already performed an administrative system file check and Win10 reports that there is no corruption on the sys file in question. So again, back to which applications is causing excessive system to call ISRs, is a question that needs our focus.