From LUA API the values for power are actually in Joule per tick. There's 60 ticks in a second so a value of 1 equals 60 W. If you want to set exactly 1W then use 1.0/60.0 as value.

The time of each recipe is the time it takes to craft by hand - the player's hand crafting speed is 1.0. In my calculations i use the quantities "nominal crafting time" and "real crafting time". the conversion between the two is just the crafting speed. As Nich pointed out, the ...

I tried to create a solar-thermic boiler (sun heats water) which seems to have no simple solution: Only 1 entity is able to heat water: The boiler. And boilers only support burning solid fuels - no oil, no gas, no electric energy, no solar energy Wouldn't it even be simpler to develop to create a g...

https://wiki.factorio.com/Inserter_experiments Easier way to remember: burner inserter: 60/102 items/s inserter: 60/72 items/s long handed inserter: 60/52 items/s fast/filter/stack inserter: 60/26 items/s And when facing north: burner inserter: 60/103 items/s inserter: 60/73 items/s long handed inse...

Something that bugs me about this kind of math is that the game implies there's a time associated with each recipe. But that's not true, the time a recipe takes is only known once the crafting speed of a machine is applied. As a result units become all out of whack. For example, what's the unit/dime...

If you have to do this often enough then just make a little loading bay for the car: Better if you have multiple cars (they're not that expensive), since you can swap a fully loaded one for an empty one.

I'm fan of single belt production facilities myself. Well done!

But I also have to accept that splitting the input from the intermediaries/output massively simplifies everything.If the ratios are right everything just works:

Forgive me that I play in chinese, but Maybe you can understand the position of what the function is. It is helpless because my Non-Stack Inserter is controled by another signal from red line and it's different from the signal of the thing it pick from the belt. Use (EVERYTHING < 1) as condition in...

Mbas: :re while(a<1000)a++; a-=333; goto re; -333 because... time from "detect value" to "remove value" is 3 ticks ( in my game ) ty. 4 TUT about Combinators but... dont need it ;x... ( lol xD sorry ;D ) -------------------- The tutorial shows a simpler clock design: https://wik...

So cute!!!!

There's this flawed idea that putting 3x more devs on a project will make it go 3x faster, it doesn't. ;) From what I understand Rseding does the code performance improvements, enjoys working on it too. Almost everytime talks about how this or that affects performance. Twinsen is the only one doing ...

From what I understand they do it in some specific order BUT they may skip some if there's not enough robots. So you need as many construction robots as items being placed to see the actual order.

This was posted a while back:
https://www.reddit.com/r/factorio/comme ... terballet/

However this is thinking about the problem completely backwards. Every object has a buffer and knows what it is going to do so outputs can be calculated in parallel. Then once all the outputs are known all the inputs can be calculated in parallel. This will however cause a 1/60th delay in an assemb...

Maybe you'll find this interesting: https://www.reddit.com/r/factorio/comments/5n059i/almost_single_belt_assembly_line/ Made using circuit network only. Almost all Factorio recipes are one way. So in theory a single belt can provide all the logistic needs. Input enough iron/copper/steel plates on on...

EliteMasterEric wrote:You can just do the below:



This combines all the items from two belts onto a single belt.

Not all. 2~4 items will be eternally stuck on the "blocked" side.

If both stations are same distance from the train's departure station then the one picked depends a lot on train pathfinding algorithm internals. For us mere players that means they pick a "random" one. If one station is further away then it will be less likely to be picked. Until a point ...

The belt is reading and feeding itself it's contents twice, due to duplicated connections. I'd say it's expected behavior, due to belts output looping back to it's input. Two connection == two loops.

Well, it's not "current" yet :) but better spread them evenly. As for per-surface threading - yes, we would go that way if Factorio would be natural to run multiple surfaces, and all those surfaces having a decent factory. I was just thinking that players already change their factory to o...

... yes. That's what I've been saying. I don't know where you got the idea that when I say "We're limited by RAM speeds" is memory throughput. It's both: tons of random access of little bits (latency) and a very small amount of throughput. Additionally that throughput listing for a given ...

you could use undergrounds to fully compress a belt. Let inserters unload their contents in an underground. Undergrounds work like a chest and will compress the belt where unloading or sideloading fails. Apparently at some point that "feature" was implemented when sideloading into normal ...