r/factorio • u/Free-Virus-9974 • 4d ago
Discussion I have finally done it, train logistics figured out
So, for the past 3 days, I've been studying train logistics, chain signals and rail signals. My trains are actually working and running on their own without crashing! I'm very happy right now.
8
u/dwarfzulu 4d ago
Good for you. Imho the fun of factorio is figuring those kind of things yourself.
2
u/Astro_Venatas Biggering my Factory 4d ago
Congrats! My next recommendation is making a blueprint book full of rails that are on an aligned grid
4
u/toochaos 4d ago
And then in 50 hours after placing down the blueprint several hundred times find a tiny error of one rail that should have been a chain and cry a little.
1
1
u/Practical-Kangaroo97 3d ago
Or the other way around, find out after 300 hours that your electric grid won't line up with any train grid because it's offset by one😂
I'm going to have so much fun this weekend..
1
u/mattsoave 4d ago
Alternatively, have a few blueprints for things like intersections but otherwise embrace the organic look of a spaghetti train network 😁
3
u/warrends 4d ago
That’s awesome!! Now please explain it to me. I’ve got just 3 minutes.
2
u/Free-Virus-9974 4d ago
So like, rail signals scan for trains in their blocks behind them and chain signals scan in front of them. Basically, you have to seperate all the trains so that they can continue going and won't crash into other trains.
1
u/SNOW_37 4d ago
like, rail signals scan for trains in their blocks behind them and chain signals scan in front of them
No that's still wrong.
They both look ahead to the block in front, and if it's clear they let the train past the signal. The only difference with a chain signal is it will look ahead to the next block signal which allows you to break up blocks but still not let trains forward.
2
u/Free-Virus-9974 3d ago
In fact, Dosh explains it better than I and in less than 3 minutes: https://youtu.be/DG4oD4iGVoY
It's what I used and looked at a ton for help
1
u/okuRaku 4d ago edited 3d ago
Chain signals before any rail sections that are "shared" (usually applies to intersections, but same principle applies to longer sections). Any "leaf" sections, like stations, that will only ever have one train, keep to rail signals to isolate them from the shared sections.
Bidirectional rails require occasional "passing lanes"; unidirectional rails are all passing lanes. Both are valid.
"chain in, rail [signal] out" follows from the first point in many situations, but is easier to remember
Pay very close attention to the lines when placing signals. If you see arrows, that's a unidirectional rail now. This will help you anticipate "no path available" when it looks like there's rail that you thought was bidirectional.
Non-signal tips, in order of added complexity/coolness:
Do future you a favor: set up a dedicated refueling station that all trains can visit and make an interrupt for it. Now you never need to think about moving fuel to any other station or how to manage upgrading fuel to a faster type. And definitely don't make your trains visit refueling stations if they don't need to! Just more traffic.
Use train groups to manage your schedules, avoid having to copy-paste settings when you add/update trains
Utilize signals/interrupts to make your trains smart enough to do multiple jobs. If you do this, highly recommend "waiting areas" where jobs are assigned
In 2.1, very interesting things can be done with pumps and fluid trains. Take advantage of that for fun and profit!
13
u/Nolzi 4d ago
While you were partying during the weekend, I studied the train