[2.0.55] Crash removing screen mechanically "DrawCommandBatch.cpp:594: Failed to get buffer for 4 vertices."

[Hiran]

https://www.amazon.pl/Bi-Directional-Sw ... text&gQT=1
I use a device similar to this one to switch one of my monitors from pc to laptop and the other way around, and when I have Factorio on the screen that is being switched, the game crashes. Game seems to handle being on the other screen (one that is not being switched) a bit better, but it also sometimes causes the whole screen to freeze, and I have to use the restart button because my whole pc is just frozen.
It doesn't matter if the game is in full screen or not. It also doesn't seem to matter if I use OpenGL or not, both have the same issue.

[eugenekay]

but it also sometimes causes the whole screen to freeze, and I have to use the restart button because my whole pc is just frozen.

Since the entire system needs to be Restarted via the power button, this really sounds like a Graphics Driver and/or Hardware Crash due to the monitor's EDID rapidly being changed, or a Voltage transient, etc.... not something that is occurring within Factorio.

[Hiran]

I've done that with many games, even with some super old titles like Black & White. Factorio is the only game that has this issue.

[eugenekay]

That just means that Factorio is the only way you have found so far to Trigger the problem on your Hardware. I have a similar DisplayPort and HDMI switch, and it sporadically causes a Nvidia crash if one of my cables is loose, because the new Monitor does not reply with the EDID string in time. It is less problematic in Windowed mode, because then Factorio is just “drawing in a rectangle”; not trying to exclusively use an entire Monitor.

You can check the Windows Event Viewer for more information on what is going on with the Hotplug monitor events.

[Meddleman]

Unsure if directly related, but some laptops have... interesting ...power saving/efficiency strategies when idling.

Even when powered from a cord, the screen will go to black and into a kind of semi sleep mode. If this happens often/long enough, the game will crash amd show an error box, citing a video card was removed/experienced a loss of power.

I'm guessing since the GPU is the literal powerhouse to keep the game's staggering spritemap in memory, the loss of this might happen during another crucial step that can't account for said loss, and crash the game rather than correct against it.
This occurs also extremely intermittently/seldom, but never reliably to reproduce.