So after looking into how rotation works with an inserter, I seem to have managed to close in even further on the issue: Inserter::setupDropoffVector(void) has the following code: 000000013F6E0476 movsd xmm1,mmword ptr [rbx+1F0h] 000000013F6E047E xorps xmm1,xmmword ptr [__xmm@80000000000000008000000...

So I managed to find exactly what is causing this bug and fixed it for one inserter in my own little test world (the actual fix would require a code change). Note: This is going to get kind of technical because I used Visual Studio to modified memory in game to get the fix to work, hopefully the dev...

When a constant combinator is set to only output negative values the light will not turn on even when the combinator is on.


All four combinators are turned on, however the top two have their lights off because they are only outputting negative values.

Strange... Was hosted on Google Drive as a public image, but it seems like Google's changed how that works so you cannot directly link to the image URL anymore
Fixed the image, but yeah, it was basically like that.

Constant Combinators that are placed by construction bots will not have their active light turn on unless manually turned off then on again or the save is reloaded. https://i.imgur.com/AHv180z.png The top combinator was placed by hand, then copied and pasted via the use of blueprints to create the b...

For when you all decide to work on this issue, I managed to find out what appears to be the cause of it. Inserters that are faced north will place their first item down the tick after they arrive at the target orientation, while all other directions will put the first item down on the tick that they...

Does ut work at your intstall? My game still crashes :( Works fine for me. Check if it still crashes when you start up a new world. The bug in 0.13.0-0.13.8 would cause the game world to be in a bad state that would persist through saves. I'm not sure if the fix would also work if the game was alre...

Working Unofficial version for 0.13 is attached to this post.
Note: It requires Factorio v0.13.9 to work. Versions before 0.13.9 had a bug in the on_research_completed event that would cause the game to crash (as Steinio mentions).

So there seems to be several different ways to make it crash, at different spots but they all revolve around this one issue. This version actually crashes in a different place to where it was crashing with research queue, however it is from the same cause. I just wrote my own mod to create this erro...

Sure, attached is the log file as well as the mod file for Research Queue.
I removed a lot of my own debug logging from the log file (most of the [RQ] in function X logs), but otherwise it is the same.

Note, with the infinite loop situation, no log file is produced.

While trying to update the Research Queue mod (https://forums.factorio.com/viewtopic.php?f=92&t=17219) to work on Factorio v0.13.8, I ran into a MEMORY_ACCESS_EXCEPTION. Was looking into the LUA code trying to figure out what could cause this exception and nothing was sticking out, so opened up ...