John, I've had this problem also in T:ANE. I don't know if this will work for you (all I've got running decently on Windows 10 is T:ANE) but here's what I had to do to ensure I had the commands I needed in my sessions.
You have to go into "Edit Session Rules" and then highlight and edit the "Driver Commands". The commands that have their box checked will be available to the AI drivers. Be sure to accept the changes when you exit "Edit Session Rules" and then save the session.
For whatever reason, the session rules don't stay the same from one time to the next when I'm working in Surveyor even when saving the "Default Session". I now recheck the driver commands available before I start any work involving AI drivers.
Hope this helps some,
Don Bennett
Evanston, WY
Hi Don,
This is correct behavior. If the session doesn't include that rule it won't be there like any other one including Quick Drive, triggers, and so on because they have to be added by the session/route creator.
As with other versions of Trainz, I never setup anything in the default session. This is the one that gets overwritten all too easy when working on stuff so I learned, after getting hit a few times in the side of the head, not to put anything in there. This became a bigger issue with TS12 and the multiple sessions saved when saving a route. I once said here Will the real Default session please stand up as a post title? There was no way of telling which was the real one without going into CM to see the date details, and then deleting the oldest ones to prune down the list.
So when it comes time to setup my sessions, I have created a generic base session which I clone, change the Route reference table to the actual route I want to use it for, and then save it. In there I ensure the Quick Drive rule, Schedule Library, custom hud and all the usual navigate commands are there.
A little background. I have a test route I call XXX-Test and I used this one originally to create my generic base session. There is no rolling stock saved, just a scribble here and there of tested textures, and various assets left over like a scratch pad. The session is cloned, edited and the route dependency is changed to my current route I'm working on. When I do the actual session editing, I use that as the base since it has all those nifty, already including things, and all I do then is put in the usual stuff that makes everything happen.
John