Page 1 of 1
[kovarex] [2.0.11] Interrupts: the [Station Name] is not full condition isn't parameterized
Posted: Thu Oct 24, 2024 9:16 pm
by 4wry
Reproduction:
- Setup a train with an interrupt with the waiting condition of station not full (or full, this applies to both).
- Assign a station using a icon parameter
- Create a blueprint: parameterize the icon used in the station name assigned in the waiting condition
Outcome:
The Parameter should apply to the waiting condition, which it does not. Furthermore, when editing the saved blueprint the parameter will no longer be available to be set.
Conclusion and impact: the icon parameter in the waiting condition is not being saved or applied as intended. This limits the ability to apply dynamic parameters to waiting conditions that e.g. use the same icon as assigned to the trains main schedule. Instead the waiting condition station remains as originally setup.
PS: assigning specified stations is a workaround to a lack of option for e.g. 'next destination (not) full', but generally one way want to use parameters to have conditions for specific stations.
Re: Interrupts: the [Station Name] is not full condition isn't parameterized
Posted: Fri Oct 25, 2024 8:24 pm
by Borges
I am also having the same issue.
The '[Station Name] is not full' when adding a parameter, it does not take the actual value (which in this case should be a steel ingot) when placing the blueprint.
See the image below:
- 10-25-2024, 17-19-22.png (248.73 KiB) Viewed 340 times
EDIT: Now on 2.0.11 only the station takes the correct parameter value but not the train schedules:
- 10-26-2024, 06-24-44.png (212.06 KiB) Viewed 326 times
Here is the blueprint in case it helps:
Code: Select all
0eNqtWV1u4zYQvorAp7aQA4mW/IfmocCiwAKLbtENsA9ZQ6At2iYiiSpFJXWDHGAP0ov1JJ2hZElx6cjSbh5iUh598z/DoZ/JJil5rkSmyeqZxLzYKpFrITOyIr84iWSxU2iGD5ydVM4uKUXsyCw53nzJvmTvtROLgm0SXjhCFzzZOWLn6AOHl6Rie+5olj04onAyqZ1dmSQOywCRZ3FhyLRiIoOlbHfOE1P8IMuC3xCXiK3MCrK6fyaF2GcsQSkzlnIQz1BPgFFOXoAwi/lfZOW/uBZSI/bkie1Br5aWvqxdwjMttOAVD7M5RlmZbrgCMPcEUCCz/UFP4CMBsXJZiMpKzwS5zoO5S45kNVkE/guKcIZEG6REbmUqtXjkb8JMly8oG5o2SuReFFpsi+jpIGCfykeR7clqx5KCu0QqAdxYheNZmE9HqAH8LUjBGKS5DSkcgxTakGYNUspjUaYTnvCtVmI7yWViN/LyJmwgb6yg81a8lCXJJGFpboMKvV6oxRhNpzakZYOUl3ZxgmUDAMK4JBYKbGEofGpB9L0WUuS8T8OpXUPf70fx+1FoPwrtR2mDvZv0bxqbfr9U80dliLVk+OEAd3vXuXvWkc7U5wnW5z6H+efggQ17PkJzaq0y/uJbUpouLkTGckis06UdhQ7KmEuy0DGdhVoLKaXXhwmdXRUmdDpIx/kFHYMhVcGIZkMJB8lyCWU2pLZcRJkPri00/H61hY7pJNSuyXJMIaDBNYVg6o0R09rwpv6A2L6u403pGOmsBXo6/aYy5duDbBpce/Tw+7FeJ89Ey8leyTKL+9LIu4A36/VHF4VaMcb0Cd/aJ6ZtQsR8K2KuJnC23oiMQUz3mN9fvg4WgIJJQyuZRBt+YI8CEMxAZHAj+C42WAU+7e5gatgJVeioHTr0MUeZHoXSJUPFTvoaiskdjiA41kDKwdQVLEPPwwdpzpSRfEX+/foPweFEljov9fn804O/V5xnFY/8CJKXmY52SqaRyACsrjcva7AoyRN2BO1ej30fYbpzqppV1LNcNQDWo92nerS7O412nCl4A6c7MxR+rIR2mGMkcSqxTjPeCQy2FQ8YHG+IzbttjWJK6EPKoXb2OLgTfVc6uIU+8/FAp3K2PaDNC44wUeteKGEy56qu6+QncvLqoIC56KzfpIIqIf4GV7Hs6BgXdyx+X2NOqke3J8S18ZS44SvH9x6c+8r2tztRHNbOk4A5fcOdSk4eO6yoqC6B2dwXeENHXn8xsldi4f8//zFHLN96xAranrER+/4qH3pvw7V9o3OFYROrieXwqljeCrUthY4qG8ZkpVUJxjo9buJ7RHh3akonsF/VrFv82igUoUI5j4dFOOTOyaPkXmie3iI2pCaUdW/9u9g+lGilrUwqbRV6fhks8W+x8OZLb+57QbCk/mIOhoNgATdszH9m7oVIyjJgHlV3TlEiUqHrC6NzD42Z4nxrywxGtmCfnh9nFtgQiu2Bx2VSX1e1iYV76gZeh8TYCKqRiuv+cY11n1g3UKoXKy/zqPYhM7LXGyz60KnMpdsb+O+UHIPO01wfER7UQqvlDXjn/L3+1dxJfsZ1gTeGGfBUZV63zdr4f/BdyRMTPwOU40mE7OomCgW2C2BLo1PUyATEMxxf5Ux43uh/hsAH5TRTe67tfmqdvG6UGO4m0OTkqzXaqIBjTdSY6nQocBsN3vECoate/b4oSl4MM16MANX7hnMkVZTJKGf6QPpUbsvi+s5cCX8+XQmP0L3I4Qy3g/7elSiTurKH2x+3l0yG1RWPUZhzWm4fUKisytaTWvDU3P1uGC78aZUnstq4BE5lGBUNAUz4LQFOmzUB0lYUgdehwBbbvAhSPEGxQM73Mzd0/YUbrt17f+ZSXFNcw4cLU0u9DnGNNDANNs/xw4WjV70OXWh+SDNdVM+Dah24AdID08Zclc610UXc1vgP4k9M0Dv4xvkB7/N/xCyNsSK2pjYxgfbHJtv8JOGShG0g4sE3Z2ePMp8wpeTT+gP+RFGz+FS70iWPII9xajij2CPCwA8o9WGO+w8bMECp
Re: Interrupts: the [Station Name] is not full condition isn't parameterized
Posted: Sat Oct 26, 2024 10:32 am
by 4wry
Thanks for adding the screenshots and blueprint. These are very useful to better explain the issue.
Re: [kovarex] [2.0.11] Interrupts: the [Station Name] is not full condition isn't parameterized
Posted: Sat Oct 26, 2024 4:50 pm
by Borges
No worries!
However, reading more carefully the
FFF#389, I've noticed that I misunderstood the Locomotive Group and interrupt system.
The interrupt is shared globally across all locomotives and it is not intended to have specific 1:1 station. (i'm still learning the new system
)
Even so, the parameters are not updated when placing the blueprint and I believe this might be an issue. (although it makes a lot of sense to not touch these global values when placing a blueprint, or you could ruin your train network)
Re: [kovarex] [2.0.11] Interrupts: the [Station Name] is not full condition isn't parameterized
Posted: Sun Oct 27, 2024 9:25 pm
by kovarex
Yes modifying global interrupt with parametrisation sounds like a wrong idea, that is why I would prefer to not allow that.
Teoretically, if the interrupt name was also parametrised, it would make sense, as it would make a new global interrupt for that parameter.
But I would prefer to not go that path until I would be shown some practical design this is useful for.
Re: [kovarex] [2.0.11] Interrupts: the [Station Name] is not full condition isn't parameterized
Posted: Tue Oct 29, 2024 2:51 pm
by 4wry
If the interrupt is global it is a different thing, but I believe the main issue is the lack of generic 'next destination free/full' conditions, because a typical use case would be to re-direct a train to a waiting position to wait there. A workaround would be to repeat the interrupt using just a timer, which would entail trains visiting that station, but then exiting and re-visiting it as long as the next station is not available.