Kimby wrote:I'd like to report a few issues I noticed with this patch in the version present in the latest ChilPP (sorry if you already fixed the problems in later versions)
The easiest issue:
I play with both the train name and the group name showing on the board. However, it seems there's no space at all reserved between those two fields, resulting in the groupname being behind the train name without any kind of separation for the longest train names on the board. For now I fixed it by starting all my groupnames with a space, but it would be nicer if the patch could handle that
The other issue:
I play with "Handle conditional order jumps by assuming they will not be taken". Mostly, that works fine, but I get the feeling something weird happens when an unconditional jump is encountered. Could it be that the patch still thinks it will not be taken ?
My orders are roughly like this (simplyfied, but the essence remains)
Everything works fine for the jumps in lines 2 and 5, but the jump in line 7 seems to ignored even when it's unconditional.
Code: Select all
1 Go to A 2 Jump to 8 when requires service is true 3 Go to B 4 Go to A 5 Jump to 10 when requires service is true 6 Go to B 7 Jump to 1 8 Go to Depot 9 Jump to 3 10 Go to Depot 11 Jump to 6
In fact, my timetable seems to be consistent with assuming unconditional jumps will not be made. Once the jump is actually made, the correct information suddenly appears on the board.
from what i can tell you have Go to A and Go to B
a-b-a-b-a-b the only reason you have 2 jumps is because you want "nearest depot"
a-ifservicerequired(gotonearestdepot) - b - ifservicerequired(gotonearestdepot)
see example image