Jump to content

Snowpig

Member
  • Posts

    20
  • Joined

  • Last visited

Everything posted by Snowpig

  1. took over DGZ on DE1 with signal K1/2 set to green. Train 42126 which I sent to/over that signal showed signal red in the overview on left side. Could resolve the issue by revoking the signal and setting it again.
  2. Zawiercie: when Lazy La is asking to send ROJ/RPJ or MPE via track 4 and you want it not to do, just ignore the request until your track 2 coming from Lazy La is clear again, Lazy La will automatically cancel the request and send the train via track 2.
  3. because it is working as intended maybe?
  4. Usually if you have already established incoming lock on track 4 Zawiercie, the next time Lazy La wants to send you a train via track 4 it just asks and when you give it permission, then the train is simply sent. To make sure, the AI did you understand correctly, i strongly suggest to tell it the track number as well.
  5. Nevermind - Dandowka interlock is type C. Can be deleted
  6. So i set up a route with signal A. Then I used za to revoke the signal. Everything went fine until that. When I tried to set route A again, nothing happened. Button animation was correct etc. but no route was set. Best Regards Snow
  7. Been playing Katowice on DE1 yesterday afternoon/evening. Have been spontaneously disconnected - together with the dispatcher of Katowice Zawodzie - with "Server disconnect for unknown reason". Managed to jump into Katowice right after the first disconnect - just to be disconnected less than two minutes later again. Since the situation around the rail station was very quiet (1 train parking, 1 arriving) I suspect a new iteration of disconnect-bug abuse. Logs attached. From the length of the log you can see, that hours before this disconnect everything was running fine. I can also provide logs prior/after this one, if necessary. SimRail_log_2023-05-28_16-49-35.txt
  8. I just had a "perfect" run on DE1 driving the S41 from Katowice to Myszkow: - no errors (full 7125 points), no interference by player/AI dispatchers - always started on countdown 0:00 and used the cruise control on 100% power. - for braking at stations I used cruise control as well. Since I have already memorized the optimal distances for braking I had perfect stops at the correct positions for all stations on the way Still did not get the steam achievement "on time". Reason for that: the timer let me depart almost always one minute after the correct departure time. Therefore: please either fix the timer for correct departure time or change the rules for the steam achievement as atm you can get it only by accident / higher powers / dark magic.
  9. When driving an TCE 2405** from Sediszow to Myszkow you pass a speed-40 sign on the entry of Bukowno. Unfortunately it is not shown on the speed warning overview (top right), so usually you drive at 60+ into the sign and immediately start collecting speed penalties.
  10. additional log SimRail_log_2023-03-12_17-53-11.txt
  11. had several disconnects on DE1 while driving through Warszawa - especially around W. Wschodnia (just after train is available) and W. Zachodnia (on approach - first half of the peron) log is attached. Haven't had any disconnect issues prior the last patch.SimRail_log_2023-03-12_17-53-11.txt SimRail_log_2023-03-12_17-29-04.txt
  12. DE1: Zawiercie: player of TME 421060 was too fast when approaching Zawiercie and shot over the red signal C. The game did not reset him back to front of signal - instead he was already inside the station area (first five line segments red). He could then continue to peron II as - according to his claims - his signal was orange. I had a EIP just passing G1 so the TME shot over the track switch 21/20 which was not set in his direction.
  13. yeah, you are happily throwing edge cases together. Let me untangle your arguments into proper cases: 1) no train, dispatcher reads/goes to toilet/kisses his wife -> nothing happens 2) train at red signal, dispatcher is waiting for other train (which usually means: he checks the table/screen, the schedule, talks to the trains) -> nothing happens 3) train at red signal, dispatcher is sleeping - thus no input comes to the game at all for more than 5 minutes: -> message and then kick, when no reaction this is the core of my idea - nothing more.
  14. I am quite sure that you do not sit around doing nothing while waiting for that other train. The idea is that the silly message pops up when you have a train waiting and doing no other inputs to the game at all.
  15. I would let that depend on arriving trains. As soon as you have a train arriving at your inbound signal, start counting the time. After 5 minutes without any mouse movement/keyboard input -> request visit of the coffee maker.
  16. Playing Idzikowice atm, its timetable shows all trains to send along line 4, which is - at least for the 423*** and 223* trains - incorrect.
  17. same for Dabrowa Gornica DZA for 6440** cargo trains: unnecessary track switches when no other trains at station.
  18. maybe a more modern approach by using surveillance cameras?
  19. So, several times I have witnessed dispatchers falling asleep when playing late in the evening - well, once fell asleep myself during a period with no activity around my station. My issue with sleeping dispatchers is: not only they do not play, but they also affect the train drivers who clog around the station with the time. And I think you - as developers - have much more important things to do than waiting for complaints in forum/discord and logging off sleepy players. Hence my idea: You add a coffee machine to each dispatcher room. And between 00:00 and 06:00 AM a system similar to the awareness system activates: The player gets a message like "You get sleepy. Please get a coffee" So the dispatcher needs to actively turn around and click on the coffee machine - maybe with some nice animation of drinking coffee. If the player does not respond to it after 1-5 minutes, he will be logged off automatically. Any thoughs on that? 🙂
  20. still no timetable visible on DE1 for Katowice Zawodcie. "Retry"- does not seem to work. Update: now it's working - after second relogging.
×
×
  • Create New...

Important Information

Terms of Use Privacy Policy