After a few minutes of playing (no mods, SP, 2D editor) FPS drop down to 1 or 2 frames.
FPS do not recover unless the game is restarted.
Task manager shows that a single core is nearly fully loaded. Memory consumption is not critical.
I have first experienced that behavior with todays dev build (10-DEC-15), so it looks like a regression. {F27567}
Play a mission in 2D editor.
Don't know what exactly triggers the problem, but my impression is that it happens during action (fire fights).
For me it happens sooner or later in each session.
The problem 0026881 seems to be gone with todays build, or maybe it has morphed into this one ;-)
Hello, could you please attach repro steps? Maybe add mission where the issue is happening. Thank you.
As far as I can say it seems to happen in every mission I play. I just played with build 133700, and it happened the first time I played after about 10 minutes in the game.
It seems to happen each time you play provided you take your time to finish the mission.
I have no clue what actually triggers the issue. It does not seem to be related directly to certain player interactions or events.
I always play my own simple scenarios (i.e. without much scripting) in the 2D editor.
Geforce GTX 970, 8GB System RAM, Core I7-2600K, Win7 Pro 64bit
When the issue occurs FPS drop from their normal level to 1 to 5 within a few seconds. They then stay on that low level whatever you do (exiting the mission, exiting the editor, restarting the mission...). The only remedy is ending A3 itself. After a restart of A3 it works ok until the issue comes up again after a few minutes of playing.
Adam: Before I encountered this problem I suffered from 0026881.
That issue seems to be resolved by yesterdays build, where I first encountered the FPS drop.
As a software developer I would first check, whether the fix for 0026881 or something in that area may have introduced a regression.
(Unless of course I simply do not encounter the crashes anymore because the FPS drop now kicks in before the crash can happen ;-) )
Still present with todays build.
Maybe something is wrong with memory allocation: In task manager I observed that A3 is producing _lots_ of page faults, though there is still plenty of RAM left.