jeroezie

The current singleplayer 'paper' schedule is a number of png files stored in the scenario folders. I don't know how it works for multiplayer. The current ET22 singleplayer heavy cargo scenario does already containe some instructions on how to performe cab changes.

When you have a cargo train coming from DGW on tracks 3a or 4a (the electrified sidings, not the main line tracks), the train route coming from the entry signals K and J will stay in place instead of releasing when the train is behind the signals H3 and H4. Their is no track occupation on the tracks behind the H3 or H4 signals. I experienced this with train 424070 and 424068 while playing on server int4, date 20-01-2025. Images of the situation are attached. SimRail_log_2025-01-20_10-19-06.txt

SimRail_log_2025-01-16_22-38-17.txt

If you spawn a Ty2 steam locomotive in an self made LUA scenario, it won't turn on its headlights (no matter its a moving train or shunting move).

Multiple players (myself included) and sometimes even the AI had trouble setting up train routes from Sosnowiec Południowy towards Sosnowiec Dańdówka. The train route from track 1, 2 or 3 (signals C, B and D) could not be set up towards Dańdówka, the Dańdówka dispatcher send line clear message and the lineblock was set up currently). When setting up the route, the computer seems to accept the route, it lines up the switches as expected, then nothing happens for a bit and later it will display a order rejected message. Full details here: https://discord.com/channels/1067073812560093264/1329535955752845356

Its probably a bug. You can best report it.

In an EP07, EU07 or EP08; the tooltip for the passive driven switch, light up red when you hover the mouse over it, if it is flipper upwards (Jazda Pociagowa). For the ET22, it lights up red when flipped downwards (Jazda Ciagniona).

The train brake handle of loco EP08_013 can get stuck in the running position when being towed by another vehicle. It can happen after changing from towing the loco to being the towed locomotive (changing directions with the set of two loco's). I tried to replicate the problem with EP08_001 but that one worked fine. A custom scenario with this problem is provided. Start up the EP08_013 loco first, then drive to the ET22_664, prepare the ET22 for towing (set passive drive switch to jazda Ciagniona, activate the battery, set direct/loco brake handles s to release, set indirect/train brake handles to disabled and release the handbrake), couple up and drive. You can follow the signals, and stop behind the signal on an dead end track or when the stop pop up appears, the shunting signal in rear will clear and you can switch loco until the bug appears. With my test run (log attached), the bug appeared after departing from the Id_Tm62 signal. loco_test.zip SimRail_log_2025-01-13_23-09-27.txt

Before the 13-12 update, the regional trains runnel was not build exept for the parts visible from the mail line. Ochota, where the player is forced to leave, was build. Also, trains could travel across the unbuild tunnel already. I don't know how much is actually built in the current game version, but considering the player despawn point, I am guessing not much has changed.

I know, but tbe ai trains run on a schedule, als all schedules are timed using seconds since start time of the scenario. I can not simply change the start time of the scenario, that would be way to much work. I hope the bug with the shunting route gets fixed.

Temporary mission.lua file for the EU07 variant: Dandowka_Towarowa_EU07.zip

Could you discribe what happend? And show your missio.lua after the edit please? I also noticed, that I made a typo. The correct signal discription is SDn_T, not SDN_T. (The whole line of code that I posted was correct, the part where I discribe the instructions was not.)

The stuff down here won't be of any help completing the scenario, because the bug with departing from DGZ is still prevalent in my test run. I will do more testing soon. I had already typed the whole thing in, so I am sending it anyways. It seems like, a bunch of shunting routes at Dandowka have disappeared/been removed in the current game version. You could circumvent this issue by changing the signal the players train spawns at, to the SDn_T signal, where the train departs after shunting. You will have to wait for the planned departure time still, and in my trail run the bot 42948 showed up a couple minutes late (15:09) and the signal trigger needed in order to depart, is only created when bot 64948 has reached about halfway the platform. Only then you can call the signaller successfully. Manipulate the mission.lua file the following way: Look fore line 20, replace "SDn1_H" with ("TYPO -> SDN_T") CORRECT -> "SDn_T" The result should look like this: PlayerTrainset = SpawnTrainsetOnSignal("Treintje", FindSignal("SDn_T"), 36, false, true, false, true, Please let me know, if this is successful. The trick should work with all three version of the scenario.

It could be a bug in the new version of SimRail. I have not done a test since the 13-12-2024 update.

I wonder, did the dispatcher provide both reason and warning to the driver of the train send to occupied tracks between between Kozlow and Sprowa? Not that it should be done, driving on sight for such a distance is nog workable at all.

Sz is not checked by the system like train routes are. The dispatcher is responsible for the correct giving of the substitute signal.

Their also was a bug, that is fixed now.

Its because the radio splitter was added later to the EU07 then the tutorial was made. Turn on the radio equipement on the back wasof the front cabin and set the proper cabin, then it should work.

Compared to a fancy 200 pound one, it will probably have a better prise/quality ratio, even when it is garbage. 200 pounds for some DIY electronics, insane.

Where tou running on time or where tou late? It should not matter buf its usefull information to recreate the problem. Do you rembrr, if the 141xx train passed you when arriving at DGZ DZA and sid the pendolino heading to Warschaw show up?

I spotted the Lazy LB Ai making dump decisions today, when handling 406xx when it arrived before an 14xx train. First train 1417 was routed via Lazy LB track 3 and then track 3 from LB to Lazy LC in order to 'overtake' train 40619, which was held at Lazy LB track 1. Later a similar thing happened to train 40621 and 1419. 40621 was held at Lazy LB track 1, 1419 was send via Lazy Lb track 3, then track 3 from LB to Lazy LC, where it continued via the slow cargo trains track number 3 to DGZ (instead of main line track 1). 19-11-2024, 1417 around 10:15 and 1419 around 11:16 in game time.

Please check if the game has not dome something odd with the reverser handle in the unused cabin, I havd had som weird behavior when walking trough it, where the reverser/direction lever got set up in the deactivated cabin.

No its not an bug. Its a side effect of the used trics to send the train where setting nornal routes is not possible, because the Towarowa yard does not exist. Something similar happens, with some of the Dandowka shunting signals, where not all needed shunting routes are settable the normal way.

I uploaded a 1.1 version for the EU07 scenario where this is fixed. I must have forgotten to turn the developer mode of somehow in the EU07 version of the files.

Hallo all, For the scenario I am working on, I would like to have the player bring a train, lets call it train A, to a station and leave its train their to be taken over by another (bot) driver. Then, I would like a bot to bring a train (lets call it train B) to the station, where the player takes control of train B. The bot driver then should drive train A further. I have no idea for to code the switching between player and bot driver, is their someone who can help me with this? I am aware that their is an TakeoverTrainset(trainset) function, but the wiki does not explain what it does or how it should be used.