Factorio 0.8.8 Sprite Rendering Issue

[rlerner]

Started the game up after a long hiatus. Ended up having a few issues, so I uninstalled it and re-installed 0.8.8.

I realize it is experimental.

I played a new game for a few days without many issues, today started it up and the steam engines were flashing (as if there were frames missing out of the sprite), and the belts didn't show up.

I then started walking around and the ground never refreshed (dragged the image):



I figured I'd restart it and try again:



This time the belts (except corners) are not showing, and the yellow inserters aren't showing either.

System Specs:
Windows 7 R2 x64
8GB Ram
On split displays (3), game on primary desktop.

Factorio 0.8.8 x64

This is in need of immediate attention, if I don't have a working version STAT I might have to do some work around here!

[rlerner]

Restarted again. Belts and Inserters showing.

[kovarex]

Hello, the most important system specs is the GPU, mainly the video memory amount.
Trying with the low-graphics might solve the problem, as long as the problem is the insufficient video memory size.

[rlerner]

REstarted, labs were pulsing, radars didn't show.

Took me a few minutes but realized a lot of the work I did earlier did not save. Checked my autosaves, same story, all behind.

[MF-]

Sounds a bit similar (but with way weaker consequences) to my problem
burrided & hidden at https://forums.factorio.com/forum/vie ... php?t=1991
I am not suggesting those are related. They look a bit similar, though.

Does your screen have black spots before you move your character? (mine does)

[cube]

Some time ago I've had similar problems on Linux when I resized the loading screen. But I assumed (perhaps incorrectly) that it was only a problem of my graphics card...

[rlerner]

MF- Mine did not.

Here is my overkill solution.

I wiped my computer. Reinstalled the OS, reinstalled latest factorio, and it worked.

I know problems like these are hard to track down, and I doubt it was the graphics card (the current version runs fine). So I took that approach to rule out other isses.

I would say this is resolved for me, and was probably just an isolated issue.