Started by THLeaderH, June 24, 2019, 10:58:17 AM
0 Members and 1 Guest are viewing this topic.
Quote from: Leartin on June 24, 2019, 02:43:41 PM1) Remove binary platform occupation. If there is enough space in a station to fit the full train, that train should be allowed to enter, even if part of the station is already occupied by a different train.
Quote from: DrSuperGood on June 24, 2019, 06:04:17 PMThat sort of line configuration is discouraged if one intends to maximize profit. Additionally it is very prone to causing 1 of the lines to stall since it will have to wait for the orther to progress.
Quote from: Leartin on June 24, 2019, 02:43:41 PMThe way your coupling works, I would be worried for deadlocks.For example, what happens to the child if it arrives at the coupling point, but there is no parent to pick it up yet? What happens if there are other trains on the line, and one of them blocks the child from entering the platform, while being blocked by the parent on the platform, which is waiting for the child? What if you had three rural lines and you wanted to combine any two of them bevor they enter a busier section, how could you do it? It all would have to be planned were meticulously, and any mistake may have grave consequence, so it would only ever be possible to be used in a "model railway" game, not in a "normally growing" game.
Quote from: An_dz on June 28, 2019, 06:19:53 AMVery nice and the UI is somewhat simple. But I have some questions:1. What would happen if no parent or child exists in the schedule?2. What would happen if I disable the "Wait for parent" checkbox in the signal?3. How is the behaviour of maximum waiting time if they differ between parent and child?4. How is the behaviour of minimum load? Does it check for the whole convoy or each for their own?And the schedule list UI could add something to let the user know the train will wait for a child or parent at that point, but that can wait for when the code is more mature.
Quote from: Leartin on July 17, 2019, 02:09:49 PMBut since I mentioned it earlier: How do you feel about completely powerless convois that can only be pulled by another convoi, to simulate a switched loco? I'm pretty sure players would try to do that anyways, perhaps with "invisible" vehicles of veeeery low power, just so a convoi counts as powered even though it behaves like an unpowered one.
Quote1) Remove binary platform occupation. If there is enough space in a station to fit the full train, that train should be allowed to enter, even if part of the station is already occupied by a different train.2) Whenever two trains are in the same platform, have the same next destination, and that next destination has a platform long enough to hold both at once, couple them until they reach the next station.
Quote from: THLeaderH on June 27, 2019, 03:17:25 PMI learned from Leartin's suggestion and totally remade the schedule settings method of convoy coupling. A new version of convoy coupling demo video is uploaded.To set a coupling schedule, check "Wait for child" option in the parent convoy's coupling point, and check "Find parent" option in the child convoy's coupling point. A parent convoy waits for a child at a stop with "Wait for child" option. A child tries to find a parent convoy at a stop with "Find parent" option. You do not have to specify uncoupling point because a parent convoy automatically releases its child under the following conditions.schedule entry mismatch between a parent and a child.insufficient platform length of the next stop.Therefore, the platform length must be sufficient for entire coupling convoys and schedule entries must be exactly same in the coupling section."Require parent convoy to enter" option for choose signals works as it was in the previous version.Coding is still unfinished. I'm working on implementing some corner cases.
Quote from: Freahk on September 28, 2019, 05:04:07 PMFrom the current description and videos, the parent will wait at the platfirm, while the child will only wait at a signal that is set up for waiting.That is why I suggested to drop the parent/ child hirarchy and instead add an optimally trinary "wait for other train" option, allowing "don't wait", "wait at platform" or "wait at signal".
Quote from: thegamer7893 on September 28, 2019, 10:23:27 AMThis is an amazing feature which you are making and I do with to get a chance to use it in Extended. However, my question to you is that, if one train comes before another, is that train just going to wait for the other train at a signal outside of a station and possibly cause delays to trains behind it or will it be able to be cleared into the platform and wait for the other train and thus preventing delays.