Cannot get an AI train to wrk i.e. to drive

[MartindeGroot]

Driving a train under Manual Control works OK, but when I set a number of driver commands in Edit Session and choose Autodetect the train in the session is still under manual control although the Help about Autodetect says if there is a set of drvier commands Autodetect should make this an AI driver.
Even when I select AI Driver in stead of Autodetect in the session, in the driver control center, the train is mentioned as Manual Control, but when I select the train in the bottom right corner the two messages appear: Not a Controlling traom and "Selected train is not under user control" When I click on the blue "View Driver"I see the command status "Manual Control"but the driver commands which I set are still persent .
I am using Trainz PLus, which basically means TRS22. A video with TRS19 shows that a train with drver commands and set to Autodetect starts executing the driver commands as soon as the session starts. Am I overlooking something? Any help will be much appreciated.

 

[marmalade32]

huh, odd.

 

[marky7890]

"Selected train is not under user control" usually means its loading at a station / industry

 

[pware]

I don't know why you are focusing on "Autodetect". All my trains in the Driver Setup rule are set to Autodetect regardless of whether they are under Manual or AI control. I have never had to change that setting. The main purpose of the options under Autodetect is to allow or disallow the control of individual trains when using Multiplayer or the TLR.

I just ran a session using driver commands set in the Driver Setup rule and it worked without any issues.

 

[pware]

I am using Trainz PLus, which basically means TRS22. A video with TRS19 shows that a train with drver commands and set to Autodetect starts executing the driver commands as soon as the session starts.

usually means its loading at a station / industry

If, as @marky7890 above suggests, it is an active industry track that is the culprit (i.e. the trains is starting on an active industry that is seizing control to load/unload) then try moving the train to a new starting position away from industry tracks then run the session. An industry track can seize control for a length of time that is set in the industry properties. For example: For a major regional station I often set the "dwell time" for a minute or more.

 

[MartindeGroot]

I don't know why you are focusing on "Autodetect". All my trains in the Driver Setup rule are set to Autodetect regardless of whether they are under Manual or AI control. I have never had to change that setting. The main purpose of the options under Autodetect is to allow or disallow the control of individual trains when using Multiplayer or the TLR.

I just ran a session using driver commands set in the Driver Setup rule and it worked without any issues.

Somehow I managed to get a train driving under AI. With setting Autodetect and a series of driver commands. Then after some time using the same tesstion, editing it and driving the session again, I definitely came to a situation where after startup of driving the session I found the train now was under Manual Control. It is not a matter of industries, for I have none. I really don't know why suddenly tjhe AI train refused to drive. The way I finally succeeded to get the train driving again under AI was to remove the driver, add a new driver, select the train, set new driver commands and leave cotrol mode to Autodetect.