jokka83

I feel ET22 should do this with less difficulty. Can this be due to gearing maybe?

I think I was going in 142081 which was about 1600 ton and was a 120km/h train. I had several parts of the CMK where it was not able to keep its speed. I was under 110km/h at one point I think. It is not really a problem, but it can create some issues. I wonder if this is realistic? The number on the paper says it should manage this I think

The last 3 times I've played at Psary, players at Starzyny has created delayes for me at Psary. This should not happen if we want to keep trains on-time. I've reported several of these dispatchers, but it doesn't seem it helps?

AI at posts that sends trains on a detour via the siding. This happens so often that I think it is a problem. I've seen also many players quit because of it. I've done so myself.

Hi. This is not strictly timetable related, so I want to make a new thread. I like to focus on keeping trains on-time, but I will not focus on what is wrong with the timetable. First I like to say that it serves no purpose for Kozlow and Sprowa(Starzyny) to operate opposite track operation. it is just too much traffic there to do it. it can also create a deadlock I suggest to ban Kozlow from making such operation.

This is still an issue. The timetable is wrong here.

191xx is still spawning an hour earlier than what the spawnlist says. Still no room for 61xx in 4120xx timetable from WP. Sorry DazT.. 4xxx was running 5 minutes late, so it was easier to squeeze you between 61xx and 4xxx than 61xxx and 61xx.

35xxx seems still to be hard to get before 45xxx on-time at Psary 53xxx seems still to be constantly delayed

Any idea on when night services will be added? I've would be playing now if it would be available.

I don't think it would be possible with a PRO-server? Any player could join it? It would have to be some 3rd party thing ala vatsim for flightim.

regarding the timetable. I think the slot for 1320xx is a bit tight between 53xxx and 13xx from Psary.

I'm all for that. Also cutting off the map, and making the EDR more precise. And fixing the fundamental issues with the timetable.

It's hard to disagree with what you're saying. As I said, I like the idea, I just don't think it fits well for the timetable that it is now. There is no winning. You can't arrive on-time. The timetable is just wrong. There is fundamental issues here that I think that should be fixed. Personally, I do like some more slack in the timetable from a gameplay perspective on the long routes. There should also be taken into consideration the effects it has on the overall traffic. Everthing is tightly connected, so if you have a fundamental fault from the start, it will translate to much more. I don't understand why it is not fixed

I haven't driven it yet, but 53xxx is still consistently delayed. I recognize the more realistic approach it is after the EA exit. I like that idea. But I'm not sure if it translates that well in this simulator. Driving a train without any reasonable way to catch up a small delay(delays are more or less a given), isn't a good gameplay mechanic. I would also say the same thing about being a dispatcher. If I will create a delay no matter what I do, it is not so fun to try to figure things out.

Feedback after the 13.03.25 update. 4121xx is often early and out of stack with 4120xx at WP. This creates a situation where holding 4121xx to its PT is not reasonable. Sending 4121xx early is not a good option since it will likely create a mess further up the line, and holding him can create a mess at WP. It is not intuitive to hold 4121xx and let 4120xx pass. I've also noticed that AI at Olsza is not always holding 4120xx, creating delay for 41xx 31xx. Also, issues I mentioned above is still present. I think it would be better to solve those issues before adding new trains to the CMK.