Skully

@SurvivorSean Yes, this was Łazy station AI. @DiscoBreak I would assume late trains get prioritized, not? And yeah, 120 km/h coaches.

I would love to see a hi-res version of these timetables on each station. If not in-game then maybe in documentation? PS. What year schedule are we going to run?

The Graph correctly shows me taking the service at 11:11:48Z. While the Summary starts at 11:36 which is weird to me. Notice also this squiggle after Zawiercie. Physics and speed indicator goes a bit wild there. Do wish to have a separate report for that? (It could be simulation slippery track.)

As I took over the 24129 it was riding extremely late and I tried to do my best to make up for it. I thought the ride down south had a speed limit of 125 km/h but it kept showing 120 km/h. Passing the 644034 as I raced to Zawiercie. And thus I was making up time as I rolled through Łazy station... Onto ... The goods line!? Which has a 20 km/h limit to boot... oh well.

On Dąbrowa Górnicza the sorting in the traffic preview for 1DZ is broken. Train 40141 is followed by 1439.

As I was coming out of Łazy Łc in the regional service to Katowice I was looking at red signal before the last block into Dąbrowa Górnicza Ząbkowice. Apparently it was occupied by a Pendo which was unable to get through. Since no one was manning Dąbrowa Górnicza I took control of the board there. It looked like the AI at Dąbrowa Górnicza Ząbkowice was not allowing anybody through southbound. Making a quick inventory of everyone waiting at DGZ I gave clearance to DGZ for 40141. Weirdness ensued. Apparently DGZ AI was waiting for 644046 to appear (maybe even on track 1). However 644046 had already passed through both DG and DGZ. The AI informed me it was cancelled and things got moving. Now the AI was on a roll and let the Pendo I was trailing earlier go through after 40141. Thinking to bring 40141 to the opposite side of the platform I forgot DG does not have a crossing on the right side. 🤦‍♂️ I also got further confused by the red traffic list order... Anyway, I had cancelled the incoming for 40141. Which gave me time to contact Będzin to setup a left track run for 40141 freeing up the right track for the 1439. With the left track in play for 40141 and 1423 making a fast pass, I kept calling out DGZ to give me the rest of trains. And thus we managed to get DGZ cleared up and everything up and running again. Except for 644048 when I found a new button play with. Oh well, more on that later... 😄

So far I've only seen "we are aware of issues related virtual dispatcher" and my own issue on Zawiercie AI got deleted. I'm going to try something different which might provide some entertainment and isn't a waste of my time. The vagueness around the AI issues and not getting the ability to run a private server (on release) is a bit fishy. I'm beginning to suspect this AI is written in Python or LUA which could lead to a false fear of an IP leak. Or the thing could just not be ready for any full fledged testing yet going through too many rewrites. It's anybody's guess at this point. 😄

And sometimes only luck will save you. 😄

Yes! 😁

The root cause is the incapability for the AI to deal with badly routed trains. Your proposal will again leave badly routed trains in stations. I do agree that the current warning is limiting the simulation. It feels like auto-braking the train when facing a speed restriction. So like you say a points penalty might be better. As for the AI trains they should always default to moving forward. 😁

How about some external views under the number keys? We can walk about and the trains have external view. Maybe some predefined views as such would work?

You're not a fast enough reader as it does show for 1 frame or so. 😁

Same bug happens here: While tuned to R1.

Since this is punishment for the uninitiated it needs to be made clear how to resolve this. Note that leaving the station to the AI and coming back immediately clears the occupies.

After cancellation 2P remains occupied.

To expect a clean run on a public server with randoms is an unrealistic expectation. It can happen sometimes, it probably won't happen most times. Early services tend to be clean ones, the late evenings are usually a mess just as in real life. 😁 As long as a dispatcher makes the traffic flow it should be fine. We should have a proper scoring system for dispatchers so only the experienced ones can do alternate things (risking losing experience). Low level dispatchers should be guided by the AI to get points. Losing time on the board or bad routing should mean penalties. Losing too many points in one session could mean a temporary ban.

I noticed: As it interacts with Dąbrowa Górnicza and Katowice I thought it would be nice if we can drive it. 😄

It can happen when DGZ gets busy. Don't expect Łazy Łc to be straight through. 😃 For those who like pictures: Make sure you reset NP3 as you do not wish to accept anymore incoming traffic. The objective here was to clear the trains as fast as possible. I think I can do better. 😁

While not realistic I think it's okay to backup if you have not cleared the signal yet. If you have cleared the signal and you backup a trailing train may either be in the block or get thrown a red. Don't backup if you have cleared the signal. You may contact dispatcher and see if you can get back 50 pts.

Well backing up at least nets you 50 pts. 😁

Now parking 42186 on EN1 in Będzin.

Another example just on EN1. I think it's more because people don't know how railways operate but the cargo train was driving just 20 km/h because it was ahead of schedule...

😄 Oh ah, been doing that a bit on the discord. I also filed a report for traffic stuck at Zawiercie but the message is stuck at moderator. 😁

What exactly do you wish to test? Stuffing all trains onto line 1?