Hemiptera Bugtracker at bugs.linux-forks.de

From the server log:

2019-02-06 23:49:50: WARNING[Server]: [advtrains]372286 overrun LZB 0 restriction (red signal) (786,12,27)

2019-02-07 00:04:18: WARNING[Server]: [advtrains]372286 overrun LZB 0 restriction (red signal) (227,17,-1096)

2019-02-07 00:10:29: WARNING[Server]: [advtrains]401407 overrun LZB 0 restriction (red signal) (1526,7,1971)

2019-02-07 00:23:03: WARNING[Server]: [advtrains]757495 overrun LZB 0 restriction (red signal) (786,11,-193)

2019-02-07 00:25:01: WARNING[Server]: [advtrains]757495 overrun LZB 0 restriction (red signal) (786,12,27)

Turns out, the signal is red, because the section ahead is blocked by

the train that overran the red signal itself. The behaviour should be

different: The signal should check if the train blocking the section is

the train trying to pass the signal itself.

I think the reason for this is that the influence point of the signal

was too close to the TCB position.

Also happens on the Neverbuild Shuttle, as was reported by Smacker.

i had pushed a possible fix lately. Did the bug reappear?