Page 1 of 1

[1.1.39] Graphics glitches after alt tabbing

Posted: Sat Sep 04, 2021 8:07 pm
by lollerbob
Thanks for making a great game.
After playing for a while, various graphical glitches appear in both map mode and main game view.
It seems the glitches start appearing after alt tabbing into chrome showing streams.
They seem to have no impact on gameplay.
The glitches are in consistent locations on both map and gameworld and may be different entity graphics that are corrupt.
Glitches are often linked to zoomlevel, appearing and disappearing when zooming
Bug did not happen on newest version about 7 weeks ago.
The bug is observed in 3 play sessions, the screenshots are from session 2 (log: current1) and 3 (log:current2).
Attached save was used in all 3 sessions and from end of session 3.

Expected behaviour: no graphical glitches.

Hardware: Lenovo W510 laptop - Intel Core i7 820Q - Nvidia Quadro FX 880M - 16gb Ram.
From second session
From second session
Factorio bug.png (4.37 MiB) Viewed 1211 times
From third session
From third session
Factorio Bug 2.png (3.6 MiB) Viewed 1211 times

Re: [1.1.39] Graphics glitches after alt tabbing

Posted: Sat Sep 04, 2021 9:59 pm
by lollerbob
Another game session had the issue happen to the water, probably easier to debug.
Also see lower left and right of minimap.

Re: [1.1.39] Graphics glitches after alt tabbing

Posted: Sun Sep 05, 2021 7:41 am
by Koub
I would suspect too high graphic settings for your hardware. No offense, but the computer you're playing on is probably around 10-11 years-old. You're within the minimum requirements, so it should run, but you must be pushing your hardware to its limits on some aspects, like VRAM consumption.
What happens if you lower your atlas texture size to 4096 in Graphics Settings ?

Re: [1.1.39] Graphics glitches after alt tabbing

Posted: Sun Sep 05, 2021 6:14 pm
by lollerbob
Thats fine, it is my vacation computer, factorio is basically the only game that will run on it.
I just reported the issue as I had not seen it before, and maybe it was introduced by a new patch.

After changing to 4096 atlas size, I have not been able to replicate the issue, so that seems to fix it.