DazT

Another being the TLK trains via Juliusz where they have insufficient time between Dorota and Juliusz and will always lose about 5 minutes, I'm just glad we've got some trains to play with!

Had it the other day on a northbound EC at Psary with AI in charge, got the usual slow down before the box, entrance signal steps up to yellow and 60kph restriction, I get put on the sound bound loop and down to a red. A few go by soundbound and the AI then clears left line running to Pilichowice where I'm crossed back to the correct line for no reason whatsoever!

When driving around in an EP07/08 when it's starting to get dark I flick the 'train heat' switch to ensure my passengers are not sitting in the dark, my suggestion is for all AI passenger trains (not empty stock ones) to switch on their internal carriage lights also, say an hour before sunset and leave them on until an hour after sunrise. I notice the EP07/08 already does auto-adjust the headlight dimming brightness already when in bot mode, so this is a little add-on so that when you're passing other passenger trains their carriages are not in darkness as you pass them.

Hovering over the sun visor in the cab of the EP07/08 shows the tooltip description shows as a 'Roller Blind', a better more accurate description would be 'Sun Visor' (Server EN1 0610 02/03/2023 - Early Access Build: 21/02/2023 - 00:04)

Can't wait to give that one a go!

And now I'll take the thread onto a new tangent, holding a signal on the end of the platform at red 'just because I stop' there even though I'm next to go, I can read the timetable! 😁 By holding the platform starting signal at danger means I'll then adopt a defensive driving style and crawl into the platform.

Is it correct that the linespeed from Dorota to Juliusz heading Westbound is 30kph for the distance it is on the simulation, seems an awfully long distance. Looking at openrailmap (whether this is correct is anyone's guess!) and it shows only a small portion of 30, and the rest is 100kph which might explain why you can be ontime for the checkpoint at Dorota and losing up to 5 minutes to Juliasz, so either the timetable is too tight on the TLK trains or the linespeed is wrong. (Server EN1 - Early Access Build: 21/02/2023 - 00:04)

Haha, love the photos, I got caught up in all that earlier, I'm the EP07 on the right 😁

You'd like to think that, I did a short spell on Zawiercie panel earlier to waste some time in-between some EP08 drives I wanted to do, and whilst on there gave the signal in and the signal out for the **:37 EC towards Katowice, it came in early, and definitely stopped at about **:30, next thing I hear it roaring past the box at **:31! I just thought "well it's your score you're affecting"!

So long as the algorithm that doesn't penalise the driver too much who might be running early on a straight bit of railway, no junctions and is the next train anyway. With the EP08's on the EuroCity's it's very easy to tank along at 140kph even though you could in theory do the whole thing at about 120kph and still be ontime as the timings are very slack in places. I have been known to floor it out of Warsaw towards the CMK and then just knock the speed off as I know I can't get away any earlier from my first stop at Opoczno Południe at 2 minutes past the hour anyway.

Sometimes you need to run slightly early, especially as a lot of boxes are still AI dispatchers and they bring you down on restrictive aspects as it is, let alone a human doing as well. I look at the map, see that it's not an AI running it and think "great, I should get greens here" - Doesn't always happen that way though!

If you start your journey prior to midnight but reach the exit point after midnight then the time shown as finishing is incorrect (Server EN1 26/02/2023 - Early Access Build: 21/02/2023 - 00:04)

When you hover over any of the track sections to the right of the workstation screen, the text tooltip extends off the edge of the screen (Server EN1 2247hrs 25/02/2023 - Early Access Build: 21/02/2023 - 00:04)

The Olszamowice AI dispatcher is not correctly looping the northbound EC411** services, it clears the signal throughout meaning when the EC411** gets to Opoczno Południe it's early and has to sit and wait outside for the southbound EC141** to depart the single platform there at **:02 with northbound EIP41** stuck behind it that should have passed the northbound EC411** it at Olszamowice. (Server EN1 between 1430 and 1500 25/02/2023 - Early Access Build: 21/02/2023 - 00:04)

Ah that's fair enough, I spotted it appearing on a few of the workstations.

Oh and if you're not booked to stop, and you're next to go, even if you're early then you'll go! Some places you do have to really read the timetable as if you're using simrail.app EDR timetable like I do it won't show trains on the 'Approaching' page unless they have physically struck in on the sim somewhere (which can be trouble if you're very close to a spawn location), so what you sometimes think is a reasonable move might not be if you've got it on that page as they may be one or several trains booked before it. What I do is drop it back to the 'All trains' tab and double check. After running several rotations of the timetable you get a feel for it and what should be where and when.

When using the chat box between dispatchers, if you typed a lot of text it then goes under the blue paper aeroplane so you then can't see what characters you're typing, the text needs to start moving the characters leftwards before it get to the blue icon, so at least then if you make a typo you can then see and correct it. (Server EN1, but applicable to all servers - Early Access Build: 21/02/2023 - 00:04)

Probably not the same person, but this afternoon approaching Psary heading north towards Warsaw on an EC train, nothing for miles in front of me (I have simrail.app map on usually, good for route learning and knowing where you are) and I was running smack bang on time. Then Flashing green, single yellow, red.........okay what's this all about then, I stayed radio silent, 1 minute, 2 minutes, 3 minutes, 4 minutes, 5 minutes, cleared to substitute signal via the loop, oh great, and just as I was about to show my disapproval by going past the box with the horn blaring and the person (didn't catch the name) dropped off and it went to AI! I should of made a note of the time really and they could have pulled the server logs. But also people can make genuine mistakes, blimey I've made a few bad regulating choices (deciding which train follows which) in my time in my professional capacity as an actual signalman here in the UK over the years, but I'd never go out of my way to spoil the enjoyment for anyone else. I'd rather sit at a red and be told, or if I'm the box as a dispatcher I try and let everyone know why they are at a red, for what reason and how long I expect them to be there for. And I'm not infallible to mistakes as I found out myself this afternoon (well, yesterday now) where I messed up on Idzikowice panel, I missed one single end set of points which would have routed a northbound EC train onto the very back road of the yard and not the loop as I intended to put it. Luckily I was on the ball as soon as the route went in I instantly realised my mistake as going on the very back road you can't then get to Warsaw without some ingenious shunting. Even though the driver then got the signal and passed it nearly straight away I told the driver to bring his train to an immediate stand (train was doing about 10-15kmph), driver complied and come to a stand and I managed to blow the route on the panel, key the points for the correct movement and talked him onto the loop unsignalled. The whole intention was to get a late Pendolino past; disaster averted, everyone kept informed, everybody happy. The flip side is I've noticed Pendolino's thinking that just because they hardly stop anywhere is a god given right to run, earlier and earlier and earlier and trying to break the land speed record. Some early trains are okay, but the problem is an early train you pass onto someone else then becomes their problem and early trains can then get in the way of other stuff that is running on time and the whole timetable collapses, with that some people far up the line might not have the experience (yet!) to be able to deal with mega early trains. Ones you can get away with are early freights from Lazy direction through Zawiercie towards Myszków as after about 10 minutes they exit the sim into a black hole. If I think I can run a train early and it won't be a headache to anyone else then I will, but that's because I've tried to get round all the boxes one by one, learn them, learn the timetable a bit and know what works and what doesn't

Signal Box location shows xxxxxxxxxxxxxxxxxxxxx id (Server EN1, but applicable to all servers - Early Access Build: 21/02/2023 - 00:04)

When looking at the panel every so often the screen flashes/flickers black either once or sometimes a few in quick succession (Server EN1, but applicable to all servers - Early Access Build: 21/02/2023 - 00:04) SimRail_log_2023-02-24_15-06-36.txt

I'll PM you saves adding to this thread

Posted in wrong part of forum, move to multiplayer

Posted in wrong part of forum, move to multiplayer

When trains approach from Pilichowice or you send trains to them the ability to hover over the following track sections to identify which train is on that particular track will show either the incorrect train number or none at all 952: Hover only shows train number when occupying 968 track, which also means if you have a train sat on 952 track and one sat behind it on 968 track, hovering over 952 will show the train on 968 and not 952. If a train is stood only on 952 the hover doesn't work. (See screenshot showing where mouse was, train actually sat there was 41142 and not 4144 which was sat on 968 track) 982: Hover only shows train number when occupying 1000 track 1018: Hover over doesn't identify train 1001: Hover over only shows train that is in 1019 track, otherwise doesn't work 967: Hover over doesn't work until 983 is occupied by the same train 939: Hover over doesn't work unless 953 is also occupied by the same train, otherwise doesn't work SimRail_log_2023-02-24_00-22-18.txt

Signal W has a lower case 'w' instead of an uppercase 'W'