DazT

To be honest I'd expect nothing less from some players in multiplayer who seem to use Sz like it's going out of fashion. If you use Sz without a legitimate reason (ie, a fault or a failure or where signalling regulations require and allow for it) then I consider those that use it outside those reasons I've just given, then I think you're a (think of a not very nice descriptive word and insert here). The last time I used Sz was well over 2 maybe 3 months ago through no fault of my own, some people are using it as an ordinary signal, which is not what it's designed for, like yesterday where a player on Kozlow was Sz'ing to Sprowa, train after train just because they can. If PKP wanted you to have multiple trains in section between Kozlow and Sprowa then they'd of installed signals accordingly to allow for that. All because people are just too lazy to wait for literally for a few more minutes for an occupied block to clear rather than just signalling, you know, properly. If a train has to stand, let it stand, not every train is going to get a good run all the time, just like on the real railway, delays happen. I mean I get it (partly), people want to keep things moving, but to me I can see the inherent danger of using Sz if you get it wrong as that seems common sense to me, but I guess I have the unfair advantage of being a real signaller, so safety is sort of ingrained into me. I bet no one who uses it is locking up all the points on the panel correctly like you're meant to, again that's second nature to me. I think there does need to be something in the manual, some hard and fast rules on its use. And I guess that's the bit that bugs me more than anything, Sz into an already occupied section, which generally in signalling is a big, no-no. One train, One Section, One Line, One time - that's the first thing you're taught at signalling school.

Server: N/A Build: 14/12/2024 00:42 344xxx trains show a 14 minute layover at Niedźwiedź but isn't marked as pt in the EDR

Server: N/A Build: 14/12/2024 00:42 Faults with Słomniki 1) Firstly the player character is either a giant and the panel is made for a munchkin or the player perspective is too high in comparison to the panel height. 2) The light switch or the lighting control shortcut doesn't work Already reported by someone else. 3) Panel segments 05,06 (it2924a) and 05, 08 (it2925a) don't appear to do anything. Surely it2936 should be where it2924a is (and 04. 08 mapped accordingly to whatever track circuit that should be, and it2925a should actually be it2925 and whatever it2925 (04.08) mapped to whatever track circuit that actually is.

I'm pretty sure that even if you don't own DLC, you can still see the train/rolling stock concerned anyway. you just can't drive it. Very different to how TSW works where if you want a decent variety, you have to buy countless DLC even if you've got no intention of ever driving it!

Location: Psary (Line 570) Server: EN1 Time/Date: 13:15hrs 10/12/2024 So there was a little traffic jam caused by a player on Psary who then left and dropped back to AI control. But the AI needs tweaking so that no trains are let loose from Psary towards Starzyny if there is no where for a train to go. So in the example below, 13121 should have been held back at Psary because it had nowhere to go because 1323 is in the section ahead. This needlessly then delayed 3122 even more (caused by said player) and also delaying 31122 behind that at Sprowa.

Think the only way of solving the SPl/SG thing is for the AI to actually hold off until the last second AND also follow what the timetable says. So even though 429xx has a lower priority if you believe this priority train nonsense, is for the AI to ignore that and actually just run them over the single line (if both ontime) in timetable order! I've seen it a few times where a high priority train has only gained it priority by running early so then goes on to cause carnage elsewhere EVEN THOUGH it's not actually the next booked train over a particular line if reading the timetable to the letter!

Location: Between Sosnowiec Południowy and pzs R52 (Line 660) Server: EN1 Time/Date: 10:51hrs 01/12/2024 This appears to happen every hour when both SPł and SG are AI. Because the 241xx service usually passes early through Dandowka (because when the line speed on Line 171 was raised between Dorota and Juliusz from 30 to 100 kph the timings were never altered) Because 241xx is running early, SPł then goes on to request the WBL for Track 2 (Line 660) to SG far too early. This then causes 429xx to sit on the main line at R52 Jcn awaiting a path over Line 660, even though 241xx isn't booked to depart SPl until XX:01 and 429xx is actually booked over Line 660 first, booked to arrive at SPł at XX:55. With 429xx sat on the main line, this then delays 406xx (even numbered) behind it which if AI driven will then do 20kph to sit behind 429xx, making this train also late. This then causes the 406xx to lose it's path in the Bedzin area because it's late and the AI there will more often than not hold the 406xx thinking it's late (even though the 406xx could actually be right time by DG!) for 411xx. All from one mistake by the SPł/SG AI's 11:21 edit - And Bedzin has gone on to do exactly what I wrote above, holding (now) late 40670 for 41118.

Location: Łazy Server: EN1 Time/Date: 23:49hrs 02/11/2024 Łazy Łb AI held on time 40694 for 42144 for no reason, this also delayed southbound 40147, which in turn also delayed 441067 and also 73139 that was stuck behind 40147. 4 trains in total delayed. 42144 is booked behind 40694 to Zawiercie so there was no reason/need for the AI to hold 40694.

Location: Będzin Server: EN1 Time/Date: 13:38 hrs 27/10/2024 (Server time) - 12:38hrs UTC 27/10/2024 (Real time) Będzin AI ran 1423 Track 1 to Track 4 back to Track 1 for absolutely no reason at all, following nothing ahead, and nothing was behind apart from 40625 back at DG. 1423 was further delayed whilst the AI was running 649068 from Track 2 to Track 6

Location: Będzin Server: EN1 Time/Date: 16:45hrs 26/10/2024 Będzin AI held 40631 for 14127 despite 40631 being right time and 14127 also being right time with 14127 booked to follow 40631 all the way to Katowice. NB. This pretty much happens every single hour that these two trains run 406xx (odd number) and 141xx (odd number). Either 406xx needs to run earlier, or 14127 needs to leave DG as few minutes later -or- the AI at Będzin just needs to be told to stop being silly!

When the EN76 runs as a double set, only one set is shown on the TMS screen Server: N/A Build: EAB 21/04/2024 14:12

Certainly looks the same scenario, I originally spotted it on Bedzin back in February, but it's only took another 8 months for me to get around to faulting the others (one being Grodzisk) after working out what the common factor is between them all.

I've already reported a similar fault already But I think I've found the pattern as this also happens at Grodzisk. If a player disconnects from either Grodzisk or Bedzin and a route is already set for a train towards a controlled signal (red/white post) controlling the entrance to an ABS section where the signal is ahead of the point work, if that player disconnects the signals protecting the ABS section will return to red for no reason at all for about 30 seconds to a minute and will then reclear. From what I can see this affects the following signals Bedzin B_C B_D Grodzisk Gr_P1 Gr_P2 Gr_P3 Gr_P4 I suspect this will also affect Signal KZ_J2 at Zawodzie, as this is also a controlled signal reading into an ABS section, although I've not tried it, but it fits the pattern/scenario of the other four mentioned above.

Hacking the AI signalling to your advantage. Example at Tunel for 429xx stopping trains routed erroneously set by AI signalling towards the siding If the AI at Tunel when coming off line 62 shows you the siding rather than the platform because the AI has got a little ahead of itself with route setting, you can stop just beyond the signal protecting the junction (you have to take the signal given and stop about an engine/coach length past the signal.) You'll know it's a wrong route as you'll get yellow over yellow (40) which is for the siding, rather than yellow over yellow, over yellow strip (60) which is for the platform, so you need to pay attention! Check external map to see if the train in front has gone from the platform line (which is normally the reason why it put you towards the siding because the platform line was occupied, even though you're booked to stop!) Set the train back behind the signal, it will have now returned to danger (red), wait until the AI resets the route and you'll be given the platform route (if it's free/unoccupied of course) This works other locations I've tried where I didn't agree with the route the AI gave (40 routes, Sz routes, silly routes where the route given at the time isn't the "normal" route for the location concerned, usually because you've caught up with something in front or the AI is just being silly. My advice though is to use this hack sparingly, and ideally you need to keep a portion of the train approach side of the signal so nothing can come up behind you at line speed and potentially crash into you if you clear the whole signal section!

Location: Łazy Łc Server: EN1 Time/Date: 1720hrs 14/10/2024 Łazy Łc AI decided to run 40633 via Track 3 (Line 160) due to closely following 146039, meaning that 40366 could not complete its booked ph calls at the intermediate stations. The AI should have either asked for the train to run on Track 2 or Track 4, or simply waited for Track 1 to become available.