Rather than flood the forums with all my Ai operational problems and queries, I thought I'd put them in this thread.
The thread on the passenger stations really helped me solve my problems (cheers guys), and will probably help others when they read it.
And that's what I'm hoping with this thread.
Who knows? Maybe the problem I'm about to talk about will be the only problem I ever have with Trainz again!
It could happen!
Anyway, this one seems simple but so far it's a doozy.
I have a test where I'm running a 4 unit DMU with each end car being powered, and a driver in the front.
For the test, I have him sat in a siding in the lead loco, just outside Cardiff Central.
I have orders set up in the schedule library for going from this siding to a specific platform in Cardiff.
I also have orders set up in the library for going from Cardiff to Newport Station.
Both these work fine when run on their own.
So now, as it's a DMU, and at some point it will end up at a small terminal station somewhere in the valleys of Wales, it's going to need to turn around.
Or more specifically, the driver is going to need to jump out and get in the other cab, and go back down the line and carry out the rest of the schedule.
So, in this test session, the DMU goes to Cardiff, people get off, people get on, doors close, and off we go....backwards!
I assumed (because I've been away from Trainz, and forgotten everything!) that Trainz would realize that there was a powered car on the back, and do the honours, but no.
So, I've tried the "Change Direction" and the "Change Train Direction" commands, but these didn't work.
The moment the session started, the driver was put into the back cab, so driving out of the siding into Cardiff he was going backwards.
Then, when driving the Cardiff to Newport part, he stayed there, meaning he was driving forward.
To explain how I've set up the commands, I have the Siding to Cardiff commands in one schedule in the schedule library, and the Cardiff to Newport in another schedule in that library.
Each schedule gets the train to it's destination via trackmarks, makes sure the train is fully stopped, and waits for the train to unload and load and that's the end of the schedule.
The idea is to make it modular, so when setting up trains, I can just use these schedules in the order I need in them in the Driver Setup rule, and if I need to do anything else, like play a sound, toot a horn or just wait for a bit longer, I put these in between the schedules in the Driver Setup rule.
And this is where I put the "Change Train Direction" command.
And this is the thing.
The command between the two schedules is executing immediately when the session is started, rather than waiting until the schedule has finished, and that's what the issue is.
I have no idea why.
I suppose I could put a command in there that checks for a trigger or trackmark, to try to stop it from executing (if such a command exists, I haven't looked yet), but it's clearly a bug.
I have tried the "Move to Train" command too, but for some reason it's not recognizing the back-end loco, so I don't get the option to select it when setting up the driver.
And this has eaten up a couple of hours of my day that I intended to do some building with.
Ah Trainz, we do Love you, but....pppfffttt!
Anyway, any help or suggestions welcome.
If I crack it before any replies, I will post it here, and save other Trainzers their sanity.
(And I'm now going to be late meeting my missus for what she calls a 'stupid game', so...
)
The thread on the passenger stations really helped me solve my problems (cheers guys), and will probably help others when they read it.
And that's what I'm hoping with this thread.
Who knows? Maybe the problem I'm about to talk about will be the only problem I ever have with Trainz again!
It could happen!
Anyway, this one seems simple but so far it's a doozy.
I have a test where I'm running a 4 unit DMU with each end car being powered, and a driver in the front.
For the test, I have him sat in a siding in the lead loco, just outside Cardiff Central.
I have orders set up in the schedule library for going from this siding to a specific platform in Cardiff.
I also have orders set up in the library for going from Cardiff to Newport Station.
Both these work fine when run on their own.
So now, as it's a DMU, and at some point it will end up at a small terminal station somewhere in the valleys of Wales, it's going to need to turn around.
Or more specifically, the driver is going to need to jump out and get in the other cab, and go back down the line and carry out the rest of the schedule.
So, in this test session, the DMU goes to Cardiff, people get off, people get on, doors close, and off we go....backwards!
I assumed (because I've been away from Trainz, and forgotten everything!) that Trainz would realize that there was a powered car on the back, and do the honours, but no.
So, I've tried the "Change Direction" and the "Change Train Direction" commands, but these didn't work.
The moment the session started, the driver was put into the back cab, so driving out of the siding into Cardiff he was going backwards.
Then, when driving the Cardiff to Newport part, he stayed there, meaning he was driving forward.
To explain how I've set up the commands, I have the Siding to Cardiff commands in one schedule in the schedule library, and the Cardiff to Newport in another schedule in that library.
Each schedule gets the train to it's destination via trackmarks, makes sure the train is fully stopped, and waits for the train to unload and load and that's the end of the schedule.
The idea is to make it modular, so when setting up trains, I can just use these schedules in the order I need in them in the Driver Setup rule, and if I need to do anything else, like play a sound, toot a horn or just wait for a bit longer, I put these in between the schedules in the Driver Setup rule.
And this is where I put the "Change Train Direction" command.
And this is the thing.
The command between the two schedules is executing immediately when the session is started, rather than waiting until the schedule has finished, and that's what the issue is.
I have no idea why.
I suppose I could put a command in there that checks for a trigger or trackmark, to try to stop it from executing (if such a command exists, I haven't looked yet), but it's clearly a bug.
I have tried the "Move to Train" command too, but for some reason it's not recognizing the back-end loco, so I don't get the option to select it when setting up the driver.
And this has eaten up a couple of hours of my day that I intended to do some building with.
Ah Trainz, we do Love you, but....pppfffttt!
Anyway, any help or suggestions welcome.
If I crack it before any replies, I will post it here, and save other Trainzers their sanity.
(And I'm now going to be late meeting my missus for what she calls a 'stupid game', so...