Optera wrote:
I wanted a truly universal station, able to be provider & requester at the same time, making full use of the train composition signal to showcase what is possible. I hope others will showcase even better station designs utilizing LTN.
Well, the idea is right. But for me it still doesn't make sense, as it doesn't make sense to have any type of train in one map.
For example: In the current game - in which I want to really use logistic trains in a big scope - I have until now three types of trains:
- Bulk transport (LLCCCC),
- Bulk tank trains (LTTT)
- and now Supply (LCC)
And I doubt there will be more needed. (For example: As I want to have any outpost in a distance of 1500 tiles to another, reverseable trains make not so much sense.)
And depending on these three types of trains I (plan to) have 6 types of stations (eventually only 5, cause for the supply it is eventually really useful to have them work into both directions).
What I want to say is: A truly universal provider/requester station makes (in my eyes of course) not so much sense.
even when I designed something myself I often miss connections in this mess... There should be some form of "logic connection mode" showing at glance all connections and the signals on them, I bet you have a whole collection of requests for something like that.

Yes. I just looked (
viewtopic.php?f=80&t=22760 ,
viewtopic.php?f=80&t=18153 ,
viewtopic.php?f=80&t=30845 and much mentions besides the threads). But not so much as I thought.
Maybe we should push this as a an important suggestion? cause I think this hinders really playing with a bit more complex circuits than standard.
To get rid of the glitch I thought about using a latch to switch between loading and unloading mode depending on loading signal signs. If I can make it work I'll update this post to include that design.
What I thought about is
a) integration of the item-count-combinator mod. This morning I used that and it was a big fun to see how easy the circuits become then.
b) enhancement of the train stop or a new combinator, which "provides clever stuff". Like:
- deliver a "Pre-requesting-signal" to pre-load the requester-chests before the train comes,
- signals that update with the train content and signal if this is now "loading" or "unloading" station.
- deliver 12 signal ports: For each inserter/chest on the train one. Well, that is complex.
- and some more vague ideas, that I would like to share only at a beer
On the other hand it is an interesting task to create such a train-stop!

I tried now several hours.
But currently I see much too much glitches, I counted now 5 different states, where such a glitch can happen. And they are so difficult to reproduce. I come in several situations into the problem, that the train doesn't work anymore, cause it fills one too less or too much into the wagon. Well, I'm sure, normally you will never see that happen, cause I use that in an unusual way. But it's just frustrating.
This encoding would make those signals unusable for any other purpose and isn't very flexible.
Well, my opinion is, that this is barely understandable and I don't like to sit and calculate the binary decodings.
BTW: Why is the input in the example is decoded like that? I searched in this thread, but didn't found the reason.
My encoding shows every possible mod added loco or wagon with it's own signal
I still think this isn't really needed. Yes, flexibility in the mod to try it out is a good idea, but if this mod might be implemented into vanilla (hmmmm....), this needs to change somehow into something, that is much easier to understand (not for everybody, but for the interested ones, and without calculator).
Optera wrote:Here's an updated version of the universal provider
Well, will try this of course.
Anson wrote:ssilk wrote:For example for a LCCC train there are 3 signals:
[1] = 1, [2] = 2, [3] = 2, [4] = 1
And signal [0] contains the train-length (here 4)
So you can explain trains up to length of 36...

[1] to [4] are 4 signals (not 3), LCCC should be 1222, and 1221 would be LCCL,
and [1] to [9], plus [A] to [Z] are 35, since you use [0] for the length
I think I was very tired yesterday.

Thanks for correction.
