How does the virtual dispatcher work?

[lars.oj.lindner]

Hi,

 

I´m creating av single player scenario where a bot train is driving from signal LB_R1 to LB_G2kps at the same time as the player train should move from LB_R3 to LB_H308.
One of the routes will obviousle not be set since these route are overlaping. But I´m not able to set the failing route even after a while when the bot train is gone and the route should be clear.

It looks like some thing with the virtual dispatcher has been locked. When using the developer menu (F8) there is no route from signal LB_R3 after that the bot train has left.

The log file for the actions above can be seen below. 
I don't understand all of it, for instance what does "[SRK] Lazy - found route LB_R3 -> LB_H308 Shunting in reservation - fixing" mean?

Does anyone have a clue of what is going on with the Virtual Dispatcher? Why can't I set the route LB_R3 -> LB_H308?

 

[2025-12-09 20:27:39]: [SRK] Łazy - Route setting command: LB_R3 -> LB_H308 Shunting - initialization
[2025-12-09 20:27:39]: [SRK] Łazy - Route setting command: LB_R1 -> LB_G2kps Substitute Signal - initialization
[2025-12-09 20:27:39]: [SRK] Łazy l1_lb_iz1080 - Route reservation. False
[2025-12-09 20:27:39]: [SRK] Łazy l1_lb_Iz1058 - Route reservation. False
[2025-12-09 20:27:39]: [SRK] Łazy l1_lb_Iz1057 - Route reservation. False
[2025-12-09 20:27:39]: [SRK] Łazy l1_lb_iz1056 - Mileage reservation. False
[2025-12-09 20:27:39]: [SRK] Łazy - Unable to reserve a route for one of the elements
[2025-12-09 20:27:39]: [SRK] Łazy - Cancelled creation of route LB_R3 -> LB_H308 Maneuverable
[2025-12-09 20:27:39]: [SRK] Łazy - Route setting command: LB_R3 -> LB_H308 Maneuverable False
[2025-12-09 20:27:39]: Error received for order 1
[2025-12-09 20:27:39]: Error for route LB_R3 -> LB_H308
[2025-12-09 20:27:48]: [SRK] Łazy - Command to set the route: LB_R1 -> LB_G2kps Subsidiary Signal True
[2025-12-09 20:27:48]: [SRK] Łazy - Command to set the route: Subsidiary Signal Confirm LB_R1 -> LB_G2kps True
[2025-12-09 20:27:48]: VD order 2 accepted. [2025-12-09 20:28:24]: Retrying order 1
[2025-12-09 20:28:24]: New order 3 From LB_R3 to LB_H308 type 1
[2025-12-09 20:28:24]: [SRK] Łazy - found route LB_R3 -> LB_H308 Shunting in reservation - fixing
[2025-12-09 20:28:24]: Error received for order 3
[2025-12-09 20:28:24]: Error for route LB_R3 -> LB_H308
[2025-12-09 20:29:09]: Retrying order 3
[2025-12-09 20:29:09]: New order 4 From LB_R3 to LB_H308 type 1
[2025-12-09 20:29:09]: [SRK] Łazy - found route LB_R3 -> LB_H308 Shunting in reservation - fixing

 

Edited Tuesday at 09:10 PM by lars.oj.lindner

[jeroezie]

I have never seen anything like this before. Could you maybe send over the scenario? I am curious to take a look.

[mateusz424]

I'm having the same problem in a different scenario. Normally, the route (switches, turnouts) should be released immediately after a bot-controlled train passes. However, this isn't happening now, or at least not always. One of the switches or turnouts remains blocked and can't be set even manually from the DevMode menu. For me, the route appears in the list, but after selecting it and clicking button "Enable selected route," I get [VD]: Error in the chat window.

[lars.oj.lindner]

 

In my case it seems to be a question of timing. From my previous log one can se that the overlaping routes have been set at the exact samt time.
If I set one of them a couple of seconds after the other I obviously still get an error for one of them but when the route is clear and I try again with the failed route, it works.

So it looks like the virtual dispatcher can be stuck in an unresolvable lock when calling VDSetRoute multiple times at the same time.

I don't know if calling VDSetRoute a couple of seconds after one another is the correct solution or how many seconds is enough, but for me it's working right now and for now I'm happy with that.

 

Edited yesterday at 10:13 AM by lars.oj.lindner

[mateusz424]

W dniu 11.12.2025 o 16:43, mateusz424 napisał(a):

I'm having the same problem in a different scenario. Normally, the route (switches, turnouts) should be released immediately after a bot-controlled train passes. However, this isn't happening now, or at least not always. One of the switches or turnouts remains blocked and can't be set even manually from the DevMode menu. For me, the route appears in the list, but after selecting it and clicking button "Enable selected route," I get [VD]: Error in the chat window.

The problem has been solved for me.
The author of the scenario I was trying to revive – was calling the same Triggers() function in two different places in the scenario's lua code. This caused the VD to attempt to set the same routes twice, ultimately blocking itself. I figured this out when I fixed the Comms function and the train manager's ready-to-departure messages started appearing twice for each stop.