-
Posts
17 -
Joined
-
Last visited
Other groups
SimRail
Early Access
Reputation
14 GoodRecent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Koluszki - a preliminary guide
chromatix replied to chancellor's topic in General Discussion [Multiplayer]
I think this is one of the more modern and centralised "signalling centres" in Poland. I wouldn't be at all surprised to find three actual signalmen and a coordinating supervisor on duty in that building. One of the signalmen (probably the most junior in grade) would operate Zakowice Pld. which is in the adjacent office, the other two would operating one half of the panel each. -
Cargo Kraków-Sedziszów single mission bugged.
chromatix replied to Aero1995's topic in Bug reporting [Singleplayer]
Just the relevant end of the log: [2025-02-12 21:40:13]: RailStockResourceManager colling down prefab Prefabs/Vehicles/201E/ET22-256 [2025-02-12 21:40:13]: RailStockResourceManager colling down prefab Prefabs/Vehicles/408S/408S [2025-02-12 21:40:19]: [SRK] Ustawienie semafora 1952_KG_P101 bez pozwolenia i bez pociągu [2025-02-12 21:40:19]: [SRK] Kraków Główny - Polecenie ustawienia przebiegu: 1952_KG_P101 -> z_1952_KG_3ab-> z_1952_KG_3cd-> z_1952_KG_8ab-> z_1952_KG_8cd-> z_1952_KG_9-> z_1952_KG_320-> z_1952_KG_321-> z_1952_KG_337 -> 1952_KG_U11 Pociągowy True [2025-02-12 21:40:36]: Call pressed in trainset-Player. Call type: 3, Step: KGA, ch1 [2025-02-12 21:40:49]: [SRK] Kraków Główny - Polecenie ustawienia przebiegu: 5465_KGA_L -> 5465_KGA_Tm229 Manewrowy - inicjalizacja [2025-02-12 21:40:49]: [SRK] Kraków Główny 5465_KGA_L - Rezerwacja przebiegu. False [2025-02-12 21:40:49]: [SRK] Początek: True, Kontroler is NULL: False, DozwPrzeb: False, !środek: True [2025-02-12 21:40:49]: [SRK] Spełnienie flag dla początku: True [2025-02-12 21:40:49]: [SRK] Flagi - basic: StanPodstawowy, route: Utwierdzenie, blocking: StanPodstawowy [2025-02-12 21:40:49]: [SRK] Kraków Główny - Brak możliwości rezerwacji przebiegu dla jednego z elementów [2025-02-12 21:40:49]: [SRK] Kraków Główny - Polecenie ustawienia przebiegu: 5465_KGA_L -> 5465_KGA_Tm229 Manewrowy False [2025-02-12 21:40:55]: [SRK] Kraków Główny - Rozwiązanie przebiegu: 1952_KG_T7 -> z_1952_KG_7ab-> z_1952_KG_7ab-> z_1952_KG_4ab -> 5465_KGA_L Pociągowy [2025-02-12 21:40:59]: [SRK] Kraków Główny - Polecenie ustawienia przebiegu: 5465_KGA_L -> 5465_KGA_Tm229 Manewrowy - inicjalizacja [2025-02-12 21:41:01]: [SRK] Ustawienie semafora 5465_KGA_L bez pozwolenia i bez pociągu [2025-02-12 21:41:01]: [SRK] Kraków Główny - Polecenie ustawienia przebiegu: 5465_KGA_L -> 5465_KGA_Tm229 Manewrowy True [2025-02-12 21:41:01]: [SRK] Polecenie ustawienia przebiegu: 5465_KGA_Tm229 -> t32623kps wywołało wyjątek. Object reference not set to an instance of an object. at TrafficControl.Interlock.Posterunek.RealizacjaPoleceniaDwuargumentowego (Orders polecenie, System.String początek, System.String koniec, System.Collections.Generic.List`1[T] l, System.Byte[] isdr, System.Byte[] id_polecenia) [0x00000] in <00000000000000000000000000000000>:0 at TrafficControl.Interlock.LAN.NetworkSerwer+<>c__DisplayClass42_0.<HandleMessage>b__8 () [0x00000] in <00000000000000000000000000000000>:0 at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine] (TStateMachine& stateMachine) [0x00000] in <00000000000000000000000000000000>:0 at TrafficControl.Interlock.LAN.NetworkSerwer+<>c__DisplayClass42_0.<HandleMessage>b__8 () [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.Tasks.Task`1[TResult].InnerInvoke () [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.Tasks.Task.Execute () [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.Tasks.Task.ExecuteWithThreadLocal (System.Threading.Tasks.Task& currentTaskSlot) [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.Tasks.Task.ExecuteEntry (System.Boolean bPreventDoubleExecution) [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00000] in <00000000000000000000000000000000>:0 [2025-02-12 21:41:01]: [SRK] Polecenie do przebiegu: 5465_KGA_Tm229 przebiegManewrowy wywołało wyjątek. Trace: System.NullReferenceException: Object reference not set to an instance of an object. at TrafficControl.Interlock.Posterunek+<>c.<RealizacjaPoleceniaDwuargumentowego>b__67_3 (PrzebiegPojedynczySRK l) [0x00000] in <00000000000000000000000000000000>:0 at TrafficControl.Interlock.Posterunek.RealizacjaPoleceniaDwuargumentowego (Orders polecenie, System.String początek, System.String koniec, System.Collections.Generic.List`1[T] l, System.Byte[] isdr, System.Byte[] id_polecenia) [0x00000] in <00000000000000000000000000000000>:0 at TrafficControl.Interlock.LAN.NetworkSerwer+<>c__DisplayClass42_0.<HandleMessage>b__8 () [0x00000] in <00000000000000000000000000000000>:0 at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine] (TStateMachine& stateMachine) [0x00000] in <00000000000000000000000000000000>:0 at TrafficControl.Interlock.LAN.NetworkSerwer+<>c__DisplayClass42_0.<HandleMessage>b__8 () [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.Tasks.Task`1[TResult].InnerInvoke () [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.Tasks.Task.Execute () [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.Tasks.Task.ExecuteWithThreadLocal (System.Threading.Tasks.Task& currentTaskSlot) [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.Tasks.Task.ExecuteEntry (System.Boolean bPreventDoubleExecution) [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00000] in <00000000000000000000000000000000>:0 [2025-02-12 21:41:12]: U tunel_krakow_terrain_x113_z-37 [2025-02-12 21:41:12]: L tunel_krakow_terrain_x103_z-36 [2025-02-12 21:41:12]: U tunel_krakow_terrain_x112_z-39 [2025-02-12 21:41:12]: L tunel_krakow_terrain_x103_z-37 [2025-02-12 21:41:12]: U tunel_krakow_terrain_x111_z-40 [2025-02-12 21:41:12]: L tunel_krakow_terrain_x103_z-35 [2025-02-12 21:41:13]: U tunel_krakow_terrain_x109_z-41 [2025-02-12 21:41:13]: L tunel_krakow_terrain_x104_z-33 [2025-02-12 21:41:13]: U tunel_krakow_terrain_x112_z-38 [2025-02-12 21:41:13]: L tunel_krakow_terrain_x103_z-38 [2025-02-12 21:41:14]: U tunel_krakow_terrain_x112_z-34 [2025-02-12 21:41:14]: L tunel_krakow_terrain_x103_z-34 [2025-02-12 21:41:14]: U tunel_krakow_terrain_x108_z-41 [2025-02-12 21:41:14]: L tunel_krakow_terrain_x105_z-32 [2025-02-12 21:41:18]: U tunel_krakow_terrain_x107_z-41 [2025-02-12 21:41:18]: L tunel_krakow_terrain_x107_z-31 [2025-02-12 21:41:18]: U tunel_krakow_terrain_x110_z-40 [2025-02-12 21:41:18]: L tunel_krakow_terrain_x106_z-31 [2025-02-12 21:41:19]: U tunel_krakow_terrain_x111_z-39 [2025-02-12 21:41:19]: L tunel_krakow_terrain_x108_z-31 [2025-02-12 21:41:19]: U tunel_krakow_terrain_x109_z-40 [2025-02-12 21:41:19]: L tunel_krakow_terrain_x104_z-32 [2025-02-12 21:41:19]: U tunel_krakow_terrain_x105_z-40 [2025-02-12 21:41:20]: L tunel_krakow_terrain_x103_z-33 [2025-02-12 21:41:20]: U tunel_krakow_terrain_x112_z-37 [2025-02-12 21:41:20]: L tunel_krakow_terrain_x105_z-31 [2025-02-12 21:41:20]: U tunel_krakow_terrain_x106_z-40 [2025-02-12 21:41:20]: L tunel_krakow_terrain_x109_z-31 [2025-02-12 21:41:29]: [SRK] Kraków Główny - Rozwiązanie przebiegu: 5465_KGA_L -> 5465_KGA_Tm229 Manewrowy [2025-02-12 21:41:53]: [SRK] SetTimeParameters: 0 -
The first switch actually turns off the "setting voltage", which is code for the power to the points motors. You're supposed to do so as part of preparation for an Sz signal, to ensure that points are not accidentally changed under the train since there is no interlocked route to ensure this the normal way.
-
Actually, it was worse: the air intake to the pneumatic system compressors was not only inside the toilet compartment on a particular batch of units, but in such a position that it could be mistaken for a urinal! The problem was quickly noticed, not only due to the foul smell that rapidly permeated these units, but the rapid equipment failure that resulted from such abuse.
-
chromatix started following Summary of the week
-
The long freight trains don't work correctly with the automatic-dispatch version of the scenario. This is probably because the tail of the train is still occupying a section at the moment the script tries to set one of the routes to it.
-
The radio splitter is a new device in the locomotive, which wasn't modelled before. Since shunting is now possible, all the mechanisms associated with changing cabs had to be put in.
-
I think, though I could be wrong, that this is the permissible current to regenerate into the overhead line when braking. This does differ between countries, even those that nominally use very nearly the same electrification system (eg. Austria vs Germany).
-
[Guide] How to operate relay line block equipment
chromatix replied to oli806's topic in General Discussion [Multiplayer]
OK, I think I can interpret that in terms of Absolute Block operations. If the interlock is presently set for trains towards you, you need to ask for line clear (aka "offer the train"). If accepted, the receiving station presses Poz to set the interlock direction towards them ("line clear"), analogously to semi-automatic block. Thereafter, the sending station only needs to press Po to signal "train entering section". The Ju-SDn section does not work like that, however. I tried it just now, and it looks basically broken to me. Or have I got it wrong, and it's the sending station that needs to press Poz for some reason? -
[Guide] How to operate relay line block equipment
chromatix replied to oli806's topic in General Discussion [Multiplayer]
There's one small point I'm still confused about, after reading the above and trying a number of different panels. Suppose you have a double-track line with manual block. Here, the Poz fields will normally remain white on the right track and red on the left, corresponding to the usual directions of travel. To send a train on the left track, obviously this must be changed, but there is no Wbl button to do it with, and the replacement Po button of course cannot be used until Poz is in the correct state. What is the correct procedure? Then, would this procedure be different in any way on a single-track line with manual block? I've noticed that the interlock is typically released after each train on single-track lines with semi-auto and automatic block. I haven't yet encountered any examples of this with manual block. -
It's more that there's a fundamental difference between a "notch step" and advancing through a continuous range. In the former case, one keypress advances exactly one notch. In the latter case, the time the key is held down determines how far the control moves. A solution here would be to make the input system more independent of the graphical framerate, ie. in a separate thread so that it can monitor the precise time keys are held down for. This would also help normal keyboard players by making their control responses more consistent, so it doesn't immediately become redundant when joystick-type inputs for custom controllers are implemented.
-
Grass isn't visible - Linux
chromatix replied to RelaxXio's topic in General Discussion [Singleplayer]
The Steam Deck internally runs Linux on AMD hardware. So there's your access! -
Grass isn't visible - Linux
chromatix replied to RelaxXio's topic in General Discussion [Singleplayer]
Lots of people run Linux with AMD GPUs, specifically avoiding Nvidia GPUs because they require the extra step of installing the proprietary driver to work at all. AMD GPUs just work out of the box because they have open-source drivers, but it seems to be with AMD GPUs that the grass is missing. It would be interesting to know how the grass is implemented. It could be that there's an Nvidia-specific feature being used (which would also be a problem on Windows, presumably), or maybe it's just an obscure but standard feature that the open-source devs have somehow missed and could use reminding about.