I need help with AI trains

[Isegrinns]

Hej,

I recently switched (somewhat) to TANE (build: 88364) and I want to set up a session which involves some AI trains coming into the yard and stopping at a trackmark.

No matter what I try, the AI trains drive to said trackmark, stop for a microsecond and continue on driving.

This is most obnoxious and I´m really out of ideas here. In earlier versions of TRS, its has always been complicated to set up the AI, but it has never been impossible.
So whats the the story here? Bug or feature?

Things I´ve tried:
- all assets in same layer
- assets in seperate layers
- "drive to trackmark" command
- "navigate to trackmark" command
- another train
- another trackmark
- different radius of the trackmark

I´m getting desperate.
So plz haalp, maek it staaaahp messing with me!
KKthxbye

 

[shaneturner12]

It's actually a feature if you have another command after it. If you haven't though, then something isn't right.

Shane

 

[pware]

Have you tried putting a "Halt" or a "Wait for" command after the "Drive to" or "Navigate to" command? I agree, this was never or seldom a problem with earlier versions of Trainz.

 

[Dap]

I'd use the <kuid:32711:100025> Wait Until II command.

 

[MTH_ELECTRIC_TRAINS]

Remember to use some sort of wait command. If you are not using one, then that is the reason why the trains stops and continues after a few milliseconds. The AI system takes some refinement, believe me. I have had so many problems already and I have known how the system works for years! The AI is NOT perfect, nor is it complete (at least in my opinion) but it works most of the time.

 

[Isegrinns]

Its solved. A trackmark radius below "1" causes the mess. Fine, I´m not going below that again, as it is the equivalent of dividing by zero!

 

[pware]

Thanks for the update. All too often possible solutions to problems are provided in the forums and we never hear any result.

 

[Mick_Berg]

Its solved. A trackmark radius below "1" causes the mess. Fine, I´m not going below that again, as it is the equivalent of dividing by zero!

Is that true? Could someone verify that?
Mick

 

[pware]

I just tried it and was not able to reproduce the original problem in build 90945 (HF1) using the normal trackmark radius of 20 or using a radius of 0.5.

It may have been a build 88364 problem.