justify wrote:Do you mean that WD was scanning the RAM or do you mean that WD processes responsible for scanning kept appearing in the RAM?
If it is the ladder, I'd suggest process monitor to see what is scanned during game execution.
I myself will give it a try tomorrow.
I mean in standby memory I would get large files 100mb+ that were the result of windows defender performing scans. There is folder in the windows defender folder where it puts these files. I am not sure what exactly it was scanning.
I have used processmonitor to see what faf and fa are doing many times. It is mostly looking at the gamedata folder. Some software like afterburner/rivatuner can also cause FA to probe wow6432 system all the time for d3d files.
When sound is used a lot FA looks for non existent registry entries all the time, and I know its an issue that was not solved and was apparent years ago, but shouldn't have a huge impact.
Would be nice to see some computer literate people looking deeper into how FA is working.
Also, perhaps unrelated.
Changing permissions on C: (following this procedure
https://answers.microsoft.com/en-us/win ... 642?page=1)
appears to really help with mouse and keyboard lag (not just in FA)
Also using vmmap with FAF, I have seen the staticcache.dat file(in the windows fonts folder) get quite large( 16mb)
With a lot of stuttering happening on FAF when it is reading new font files. However this is really not a major issue, just more info.