[0.10.8] Factorio x64 Lags every 4 seconds

[Kimel]

Hello guys. I have a little lag every 4 second . But if i'll chek box [Low graphics setting] lags will disappear.
But my PC has nice performance.

PC

Intel i5-3570K (overclocked)
8GB DDR3 (overclocked)
GTX 750

I am playing dota 2 and crysis 2 on max settings without lags..

Help me please.

[cube]

Hi, I'm not sure I'll be able to help you, but try posting the timing debug info and log file here.

To show the debug info, start the game, load your problematic save, press F5, then wait 10 seconds (some of the values are updated only every 10 seconds) and make a screenshot.

[darkrising]

Hi, I'm not sure I'll be able to help you, but try posting the timing debug info and log file here.

To show the debug info, start the game, load your problematic save, press F5, then wait 10 seconds (some of the values are updated only every 10 seconds) and make a screenshot.

I'm having the same issue, frame drops every 4 - 5 seconds.

Windows 7 x64
GTX 780 TI (344.11 drivers)
AMD 8350 oc @ 4.2Ghz

Issue for me started when I updated my graphics drivers.

Here's a screenshot of the debug screen.

Edit: If I maximize the window I will get frame drops, if the window is small or fullscreen I don't get any frame drops...

[Ideoges]

Same problem here

Factorio 0.10.12
Windows 7 x64
8 GB RAM
AMD Phenom II X6 1075T 3.00 GHz
AMD Radeon HD 6800

I have tried each of the game-options but the Lag is still there.

[boro]

I have this too sometimes and restarting factorio or rebooting fixes it for me. Doesn't seem to happen the first time I launch factorio after a reboot. It's noticable right from the start in any zoom level.
I'm running on winx64 and never noticed this before 0.10.12 + latest dytech.

[Ideoges]

Thank you for the tip boro, but the lag appears even if I restart the PC. The latest graphic card driver update also seems to have no influence.

[cube]

Sorry guys, I have no clue what to do here. Wait for 0.11, we will have some improvements there that might help with this. If the problem exists even in 0.11, then please open a bug report.