Yes, the same RAM sticks that I put in in February. Haven't had any problems anywhere else so far, but I will also get new RAM next month with the new CPUs.

This new crash could be still caused by this, but I thought maybe the stacktrace could show something else in the code.

I just got a random crash when standing around in an early base, I think I was tabbed out of the game to my browser. On another save I could play for hours yesterday, so this seems kind of random.

All mods are disabled.

After dozens of hours without problems the game randomly crashed. - I was standing next to my factory, using the TimeButtons mod to set time to x999 and boost my UPS to the max (600~1000 UPS) - I was streaming on Discord and watching other streams on it - I exchanged RAM a few months prior because o...

It is already fixed for 0.16.4 which just released, so update your game.

I also got the "It stinks and they dont like it" achievement now multiple times on my new map whenever a first attack after game restart happens.

See viewtopic.php?f=30&t=54891 , there is a workaround, but a patch may appear tomorrow.

I just want to say that I feel kind of sorry for posting so many bugs and want to thank you all for your amazing work, so much dedication when I see you guys responding in the middle of the night and making new patches so fast.

Uninstalled 0.16.3, reinstalled 0.16.2, it runs fine. This time, the patch came down successfully, but same error as the stand-alone install of 0.16.3. Uninstalled and going to stay on 0.16.2 until this is fixed. Try to disable texture compression, a bug report is here https://forums.factorio.com/v...

Got another reproducable crash after steam upgrade 16.2 -> 16.3 while loading screen displays "Loading Sprites 89%" This may be related to https://forums.factorio.com/viewtopic.php?f=182&t=54843&hilit=factorio+0.16+BaseThreadInitThunk when I try to compare the logs. Update: Workaro...

The graphic of the top left belt seems a little cut off, is this intended as part of the belt optimizations?

FYI 16.2 seems to have done the trick, I can start the game with 6,5/16gb ram reserved which i couldn't with 16.1 and 10/16gb also works.

Update: 16.1 has the same problems for me, sometimes GDIPPreloadData error, sometimes train error, sometimes crash without error and now a new error saying my page file is too small (4GB). But all only if free RAM is getting low, the cached RAM seems to mostly stay untouched. Kill the Chrome and st...

Update: 16.1 has the same problems for me, sometimes GDIPPreloadData error, sometimes train error, sometimes crash without error and now a new error saying my page file is too small (4GB). But all only if free RAM is getting low, the cached RAM seems to mostly stay untouched.

Mostly chrome with a dozen 9gag tabs and 1080p youtube running in another window. For the test in the image graph I also had the Overwatch menu started.

I currently could only get the artillery error and not the loadBitmap error, but RAM seems to be the culprit (see image)

Update: Now it un-fixes itself again, get the loadBitmap error or artillery error at random, both at "loading sprites" between 40-69% so far. This last crash I didn't even get a message window and the window just closed, log attached.

Oh now it seems to work, I can get into my map and also start a new one.
Seems it was just the first 2 starts.

Dev-iL wrote:Did you guys do a clean install? Overwrite? Update?

Did dirty steam update from 0.15.40 to 0.16.0.

A great honor to post the first bugs

Started the game 2 times, got 2 different errors I think, see logs.

Edit: For now the issue of the second log is handled here: 54548

Will 0.16 be compatible with "old" 0.15 saves or do we need to start a new map?