DazT

For comparison, this is the next day with an ET22, so it's not my laptop at fault as this sparking works as I'd expect it to

Server: EN1 Time/Date: 1917hrs (UTC) 29/12/2024 Build: 20/12/2024 21:27 Had a strange one regarding Signal S at Tunel on Track 2 of Line 8 Saw the signal had reverted to danger (red) despite me having the route in for a while and the only thing I can seem to deduce is the player spawned in just as the train was approaching the signal (but the bot had already passed it), so when the player actually spawned in it was sat at Signal S at red. The route was stuck in and I had to cancel it and recall the route again. Here's the log from the chinese logger site, signal was clear and then went to red as player spawned in, I definitely didn't throw it back to red. (Times read bottom to top)

I've noticed this on a few different trains, but can't remember if it's the same type of traction or just a few, but made a note of this one. I first noticed white flashes in the cab and thought I was seeing things, but on switching to an external camera view I noticed the reason why, under an icy overhead contact wire it appears THIS is going on outside. It never used to render like that and I've not changed my specs on my PC so something is going on. Loco in question at the time was EU07-092 Server: N/A Build: 20/12/2024 21:27

Just completed 2 hours on Bukowno which is my 23rd according to the records I've been collecting when the pop-up appears, but the counter on steam is stuck at 20/40

Server: N/A Build: 20/12/2024 21:27 Coordinates: S: psary_opoczno_terrain_x115_z44, P: (59294.36, 350.55, 22531.71), R: (348.31, 235.43, 0.00) Just inside the north portal at Tunel (Kozlow end) on Track 1 of Line 8, there is a graphical glitch of what looks like grass hanging down from the roof

Server: N/A Build: 20/12/2024 21:27 Coordinates: S: opoczno_warszawa_grochow_terrain_x222_z424, P: (113951.20, 105.69, 217239.50), R: (3.74, 257.44, 0.00) This has happened for all the time I've driven in SimRail. When you go through Józefinów and approach the back of Piastów station on Track 1 of Line 1, the building/structure in the picture appears to jump up as you approach it.

Server: N/A Build: 20/12/2024 21:27 Coordinates: S: psary_opoczno_terrain_x117_z152, P: (60291.62, 225.59, 78302.99), R: (335.84, 30.04, 0.00) High-voltage power cables crossing line (under railway overhead wires and above track.)

Server: N/A Build: 20/12/2024 21:27 Coordinates: S: tunel_krakow_terrain_x117_z27, P: (60076.87, 294.49, 14283.43), R: (3.97, 6.79, 0.00) Power lines crossing track 275.9 Line 8

Server: N/A Build: 20/12/2024 21:27 Coordinates: S: tunel_krakow_terrain_x127_z-4, P: (65073.69, 253.68, -1654.68), R: (339.52, 341.44, 0.00) Next to crossing km 293.712 next to Track 2 is a large tree with power lines going straight through the tree.

I saw the pop up after working both Lazy La and DGW for the required time and the counter is now stuck (and neither got counted)

If signal 1998_Ko_F is showing a S13 aspect (two yellows/40) then repeater signal Sp_F isn't flashing (Sp4 aspect) as I'd expect it to to indicate that Ko_F has been cleared at 40 Server: N/A Build: 20/12/2024 21:27 Coordinates: S: tunel_krakow_terrain_x109_z-35, P: (55851.48, 217.24, -17423.34), R: (2.40, 171.00, 0.00) Picture showing signal in distance (Ko_F) is clear with 40 restriction and Sp_F isn't flashing single yellow.

Server: N/A Build: 20/12/2024 21:27 Coordinates: S: opoczno_warszawa_grochow_terrain_x230_z428, P: (117794.00, 117.43, 219467.70), R: (19.65, 51.49, 0.00) Only spotted as there are some services that you can drive over this bit of track next to the 8.1km stanchion on Track 3L

The following stations have no station lighting effects Kraków Grzegórzki (granted, this is where you spawn out, but it'd be nice to see the station lit) Warszawa Stadium - Has lights on the canopy but no lighting being cast on the platforms Warszawa Ochota - in total darkness Server: N/A Build: 20/12/2024 21:27

Server: N/A Build: 14/12/2024 00:42 Selection screen doesn't show any text description, just shows #KrakowBatowice_Description instead

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