Thistle Whistle

It hides it but it also then hides the tooltips for in cab controls, meaning, unless you know every switch, you're stumped. I would also like the ability to hide the alerter in the HUD for the exact reason as the OP. I'd like to just use the in cab lamps. The only gotcha with this method is that you'll no longer get the notification if you happen to be in an external view, but you just need to be vigilant when popping out the cab, and there's still the audible warning.

Pleased to hear you figured it out. As noted, you need to hold num- until you reach zero throttle. THEN press num- again to switch it to off. I took it for granted that everyone knows about that final click, but it's probably what is catching people out. As I mentioned, I've seen people in chat saying they can't get their Pendo to take power again and then come up with all kinds of reasons to why that might be. I try to help in chat but with little success. However, it hadn't occurred to me that I need to mention that extra position on the lever, I'd just say make sure it's all the way back. There's only so much you can say when you're trying to drive you're own train. But it lead me to wonder if there is actually a bug, but in all my driving of the Pendo I've never encountered such a case. You just gotta be aware of the final click! 😅 And this procedure wasn't necessary until a recent update, so that's also contributing to catching people out. I'm guessing it's prototypical, eliminating the risk of surging forward should a driver forget they still had throttle applied upon releasing the brakes.

Going by in game chat this is an issue that is often affecting people. The only thing I can say to be sure of, and I think this is a change that has been made recently to the Pendo, but once you have made any brake application, you now need to return the power lever all the way to its clicked back off position before reapplying power once your brake application has fully released - denoted in the warning panel with an amber lit symbol. Only after the warning light has gone out can you reapply power. But you must have brought the power lever all the way back, first. You've probably done all this, but it's worth a double check.

Never assume anything.

Yeah, definitely not happening on the stopper services either. At the minute, to amuse myself I even hit the Open Doors button just to hear the sound. I hope we get our passengers back soon.

Another very good point! Also the point about TrackIR is another very good reason why this really needs to be optional. I too want as much realism as we can get regarding lighting, but this dynamic auto HDR weirdness isn't the way to do it, in my opinion.

Totally agree and well written post to cover the issues with this. If we had the option to turn it off, I'd be turning it off. 👍

But there is no dilemma here. You don't decide a train goes before another train when it's scheduled AFTER it. The only thing to have any influence on priority in this case is the schedule and not the train number. In my example above, the Bedzin dispatcher caused a significant problem by deciding they knew better than the schedule. If the Sosnowiec Glowny dispatcher hadn't been on the ball, or the currently unused platform was actually in use, which we'll hopefully get trains for one day, then Bedzin's decision would have caused major problems, which it did the very next day because the dispatcher at SG on that day didn't know how to deal with it. If a train is early, it doesn't matter what priority it has, it doesn't have priority to jump in front of trains scheduled ahead of it. It simply starts running into reds at some point.

Whilst I can fully understand your point, I'd say this is a driver problem, not a dispatcher problem. As the driver, you will know where that signal is, and will know it's beyond the platform. This is obviously a route knowledge issue, but if you don't have the route knowledge then the HUD is a simulation of that, and will show the signal is beyond the platform. And once you're armed with the knowledge that the signal is beyond the platform, there's no need for the defensive drive style.

The way I do it is to keep the red until the train has stopped, but always try to ensure I've switched to proceed about 30 secs before departure, then it's the driver's responsibility to leave on time. If you hold the red until actual departure time, you're leaving the driver unsure as to whether they will be leaving on time. Give a clear indication that they'll be clear to go on schedule and they can begin preparations for departure. And as mentioned, it can pay to not open the route earlier. As for priority for Pendos, some people are taking it too far. The other day I was driving a regional into Bedzin, and the entry signal was at 40kph. I didn't realise straight away why that was, but I obviously crawled into Bedzin to find myself routed onto the left track. Moments later a Pendo came by on the right track. The problem is, that Pendo was scheduled AFTER me. And to make matters worse, it has a stop at Sosnowiec Glowny. The dispatcher at SG had the foresight to route the Pendo onto the currently unused line, and my now delayed service (which was bang on time before Bedzin) at least managed to get back in front. But unfortunately it doesn't look like the Bedzin dispatcher learned anything from the resulting radio chat sorting out the problem they caused, because the very next night I saw the same dispatcher pull exactly the same move. Only the SG dispatcher seemed similarly useless because after holding the now delayed regional behind the Pendo that was sitting at the platform, they must have got bored because they eventually just sent the regional into the sidings! It ended up being over 10 minutes late and didn't stop at SG. 🤔

Thanks guys. The signal enhancement setting at 100% does exactly what you're all describing, which I completely agree with. At night, you can see the signals distinctly. In the day, it's much harder. It's very natural. But I just think what would be even more natural is that the signals are still drawn at the longer distance and allow them to resolve into view, both by your screen and your eye. They will still be hard to distinguish against the brightly lit scenery until they get reasonably close. Some locations it may be easier to see them than others. This approach would also mean there would no longer be the need to have the signals suddenly be longer reaching when the clock ticks an arbitrary x o'clock. As the night gets darker, the signals get more distinct. Again, all very natural. What isn't natural is them popping in at 0.6km every single time, which is especially noticeable when it does start getting darker, but it hasn't switched to the longer draw distance. Surely this alternative would be a good way to approach it? Granted, any signal enhancement over 100% is going to be even more of a 'cheat' with this setup, but there's not much we can do about that other than not use it.

Thinking further and I'm wondering if it's linked to time of day i.e. draw distance is further at night. My journey was at night, but maybe started in twilight hours then part way it switched to 'night mode' longer draw distance? If that's the case, I wonder if that method is necessary, as during the day, even with a longer draw distance, it would still be harder to make out the signal, though not impossible - therefore more realistic. The signal will still come 'naturally' in to view. And I'm talking mainly about this coming from the point of view of having the signal visibility enhancement setting at minimum (100%), though as far as I can tell, that doesn't affect draw distance.

Well not really. Private servers don't fix the problem on public servers.

Hi, Difficult to know whether I'm right on this, but what I seem to have found is that some signals are visible from a longer range than others. During the initial playtest I took a mental note that on a straight section of track I could see signals from around 1.1km away. On Early Access launch I first ran an ED250 from Warsaw, and on that new section of route while travelling along the straight sections I noticed that signal visibility was down to 0.6km. I thought I must have just been mistaken about my initial recollection. But yesterday I was lucky enough to jump into an ED250 departing Warsaw and ran all the way to Katawice and a fabulous un-delayed service, but on that one journey I did indeed appear to find that signals up at the Northern end of the route were only visible from 0.6km but later down the line were visible from 1.1km. Have I noticed something unusual or is there a reason for this? Cheers.

As said, this is simply a report. It's not an instant action, rather someone who builds up a lot of negative reports may receive some kind of punishment. I have no idea whether it is being utilised. There is no perfect solution to this problem.