Decouple driver command not available in driver setup
- Thread starter belgian46
- Start date
shaneturner12
Tutorial Creator
I think I know what has happened here.
If you are using the default Decouple command (not Uncouplez or one of the other decoupling commands), this cannot be added to a driver schedule within Surveyor as the script it uses doesn't support it and hence doesn't appear in the selection menu (from what I remember it doesn't know what to decouple and there is no option to specify exactly what to decouple outside Driver anyway for that driver command).
The workaround/solution is to use a different decoupling command.
Shane
If you are using the default Decouple command (not Uncouplez or one of the other decoupling commands), this cannot be added to a driver schedule within Surveyor as the script it uses doesn't support it and hence doesn't appear in the selection menu (from what I remember it doesn't know what to decouple and there is no option to specify exactly what to decouple outside Driver anyway for that driver command).
The workaround/solution is to use a different decoupling command.
Shane
Hello John,
When looking in the driver command properties - it is available and a checkmark is visible. Decouple is not available as an add-on rule.
Kind regards
Kurt :wave:
Hello Shane,
Do you happen to know the difference with the couple driver command rule. As couple is available in the list.
Kind regards
Kurt :wave:
shaneturner12
Tutorial Creator
The coupling one normally appears because it has the option to specify what it's being coupled to from memory (via a sub menu). The default Decouple one doesn't.
Shane
Shane
MTH_ELECTRIC_TRAINS
7 Year Trainz Vet
The couple command usually appears because if you have consists to counple to on the route, then it can do so because they already exist on the route. The decouple command does not appear because the AI will not know what car to decouple from. For example, an AI train coming out of a portal can't know what cars to decouple from if those cars don't even exist on the route yet.
Hello Shane,
Ok thank you for the extra info.
In my case, uncouplez doesn't work either.
Kind regards
Kurt :wave:
Hello MTH_ELECTRIC_TRAINS,
Ok, thank you - I will have to find another solution.
Kind regards
Kurt :wave:
shaneturner12
Tutorial Creator
That's interesting as Uncouplez should appear in the list.
Shane
Shane
Hello Shane,
It is in the list but the train doesn't uncouple when I use it.
Kind regards
Kurt :wave:
shaneturner12
Tutorial Creator
That's unusual although it depends on the train involved. Have you tried one of the Decouple From commands?
Shane
Shane
Hello Shane,
Yes, I have tried it and with the same result, train doesn't decouple. I'm trying to figure it out at this moment
Kind regards
Kurt :wave:
shaneturner12
Tutorial Creator
OK - I need to check what build you are using in case there's a bug involved.
Shane
Shane
Hello Shane,
My build 88364 -
I did a test with uncouplez from and this works.
Kind regards
Kurt :wave:
shaneturner12
Tutorial Creator
Might be worth sticking with that one at the moment if it's working in case there's a bug affecting the others that may have been fixed in Hotfix 1.
Shane
Shane
Hello Shane,
It could well be my version of Tane and the route's/sessions I create in it.
Decouple head and decouple tail are functioning OK in a route which was installed
I will do some other tests
Kind regards
Kurt :wave: