Jump to content

jokka83

Member
  • Posts

    36
  • Joined

  • Last visited

Everything posted by jokka83

  1. Running passengers would be a sight. Some guy running his a** off only for you to disable the doors and drive off right infront of him/her
  2. I'm not convinced that player hours as a requirement will solve some of my issues that makes me want a pro server. I don't have the answer to this, but I think a third party server can be the answer, but no such solution I think is realistic.
  3. Do you really need the passengers to be a server thing? I think it would be fine if the passengers was just a local thing and the player can adjust it as what fits.
  4. 2 hour delay at DGZ 😂 Sorry for the spamming. All in all I like this, but I think some of it seems a bit out of place.
  5. Further, look at how the times changes form hour to hour between same train number. 1320xx. Psary I like that. However, some of these PTs are just too long for any player want to hold or drive them. 132077: 132081: This is not really a complain. I like the new timetable. But I'm not sure if it will be that popular with these many and/or long PTs
  6. Hi again. 🙂 Not sure if it is intentional or not, but I feel such a long PT is wrong(INT5).
  7. Further on the previous point, I think this timetable from WP shows an issue here. I think it is a good idea to have 53xxx wait for 13xx/53xx at WP, but then the EIP has to cross at time. If he is early, 53xxx is just gonna stand and do nothing. As a dispatcher at WP, I want 53xxx to follow right after so he can be more or less "trailing" the pendo for the Sprowa signal.
  8. I think it makes more sense if 53xxx does let 53xx/13xx pass at WP than at Psary.
  9. What happened to the cool night services? 12 car EP08 140km/h 600 ton.
  10. DLSS and FSR is not good most of the time. In most games I play I find it more reasonable to disable it. Not saying it can't be good, though.
  11. I've done some dispatching on INT5 and the new timetable. I know this is not the final product, but I like to come with some thoughts. I think this is a good change for drivers. It will not be constantly stupid delays as I think have been the norm for a long time. Now the traffic is going more as you expect. However, I have seen some delays that I don't like. some 35xxx have I seen crossing Psary late. Also 344xxx have been delaying 31xx/35xx several times. I suggest forcing Kozlow holding 344xxx
  12. I think the "loose" timetable for the pendos aren't needed when everyone else is on-time. I have seen the AI held some trains it should not hold for an early pendo. Keep the timetable for the pendos tight when other thing are going as planned.
  13. On the new timetable at INT5 1903 seems to have PT instead of PH through Warsaw
  14. I feel ET22 should do this with less difficulty. Can this be due to gearing maybe?
  15. 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
  16. 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?
  17. 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.
  18. 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.
  19. This is still an issue. The timetable is wrong here.
  20. 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.
  21. 35xxx seems still to be hard to get before 45xxx on-time at Psary 53xxx seems still to be constantly delayed
  22. Any idea on when night services will be added? I've would be playing now if it would be available.
  23. 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.
  24. regarding the timetable. I think the slot for 1320xx is a bit tight between 53xxx and 13xx from Psary.
×
×
  • Create New...

Important Information

Terms of Use Privacy Policy