tanawat8814

Within a few seconds of taking over any train, the Driver alertness system will typically activate (red warning on control panel and in the HUD; top centre). You need to acknowledge it by pressing the space bar, otherwise the Emergency Brake will be applied. Sorry if I'm telling you something you already know, but your description pointed to that being the issue.

No, I just tried again. You can check yourself without having to do the whole scenario. I set up the cab, double checking that converter and compressor were on. Rather than starting to drive, switch to outside view (move to see all pantographs). Then: F to raise front panto (works correctly) Ctrl F to lower front panto (works correctly) Repeat above sequence a further 3 times (all work correctly) Now try a fifth time to raise the front panto (F) > causes lower pantos to drop with no obvious way to recover. In case you are thinking it is unreasonable (too much air load) to test in this way, I should add that when I came across the problem originally, it was after trying to raise the front pantographs at a station stop. There had been plenty of time for the air pressure to replenish.

I'm pretty sure I did, but will re-check.

A further follow-up after more testing. The issue seems not to be related to the location, but rather to how many times the front pantographs have been raised / lowered. 2 or 3 times seems fine but on the next attempt, the rear pantographs go down and there seems no way to recover.

A follow-up on this as I believe there is a bug, but it arises from a specific action. When stopped for an extended period, I believe it is common practice to raise the front pantograph. I followed that procedure at Katowice with no issue. However, doing so at Sosnowiec Glowny is what caused the train failure. I repeated the procedure today and, viewing from the outside, observed that attempting to raise the front pantographs (F key) actually caused the rear pantographs to lower. There is something specific to Sosnowiec Glowny that causes that anomalous behaviour since, as stated, the same action at Katowice resulted in the front pantographs being raised as expected.

After stopping at the station and opening the doors, the pantographs somehow lower and cannot be re-raised. Hence it is impossible to continue the schedule. Disabling / Enabling the battery, de-activating / re-activating the cab, etc. all have no effect.

Confirming I have a similar problem on the multiplayer servers. For info: In the main SimRail menu (sounds tab), I see the microphone level responding to my voice input, after a short delay. After connecting to the multiplayer API, if I return to the Sounds configuration menu, the microphone level bar no longer responds. Checked on EN1 and EN3 servers. Log attached in case it helps. Looks like a timeout problem perhaps. SimRail_log_2023-06-11_13-13-41.txt

For me, relay based boxes worked fine until 2 days ago (April 25). Now I notice that after loading into any dispatch station, it takes several seconds for everything to initialise - setting correct local time, weather, etc. For computer based stations, this doesn't seem to cause any permanent issues, but for the relay based ones, it seems that they never initialise properly; perhaps a timeout issue. I attach a log based on the Dorota station on EN1 server, 0500 local on 27 April as an example. However, the issue persists at all relay based stations across all EN servers with Dispatch enables (I would presume it occurs on other servers also). SimRail_log_2023-04-27_11-59-14.txt

Found on EN3 server 28-03-2023 between 11pm and around 12:40am. During that period I had 2 passenger trains to route from Psary to Czarnaca. No problems with routing either train. As they passed the dispatcher station, I attempted to confirm their crossing time on the timetable. In both cases, I received a message stating the the train is too far away to confirm the data. The same message was posted if I attempted to enter the time manually. There were no such problems confirming crossing times for all other routings, including from Czarnaca to Psary. SimRail_log_2023-03-29_13-59-14.txt

Thanks, I'm fairly sure I did this, but will try again. It's possible that, to paraphrase the late Eric Morcombe, I did all the right things; just not necessarily in the right order.

Can anyone advise the correct sequence to be followed in order to get going again, following an emergency stop in the Pendolino? Muggins here went and hit Numpad 1 instead of Keyboard 1 to get back in the cabin. After coming to a complete halt, I tried all kinds of combinations (including a full power down / start up), but I couldn't seem to get any pressure into the brake reservoir. I'm presumably missing a critical step but am at a loss to know what it is.