derznovich
Active member
Personally I find the back and forth about whether illogical or unrealistic AI behavior is “user error” to be an exercise in absurdity. I think we can move on and discuss adding more commands to the default set so that users get a better experience, are not forced to creating ridiculous solutions to make the AI behave more realistically.
For the OP, I suggest Trainz should have a selectable driver command, “no reverse” which can remain in effect while other commands execute or until deactivated. If the user wants a direction marker to be absolute, Trainz should have a setting for that, either session rules, driver commands, or an option when placing the marker. Or portals could have more option — like trains from portals do not reverse. (I’m not too familiar with portals.)
AI throwing switches under driver-controlled trains or throwing switches under trains when user takes control? Trainz should add commands, session rules, or pop up check boxes to prevent this, and probably set them as the default. Is that so hard for N3V to program? I wouldn’t think so.
Ideally such mods should be an available depending on user creativity, and not relying on N3V to do it all centrally. I know there are a few session rules on the DLS, but it’s not easy to find those or search them for solutions.
For those who miss the old ways, when trains would back up to the end of the line and stop, or engines that start to “run around” and then just keep going to the end of the route, there could be a “restore legacy settings” option. For those extolling the predictable logic of present AI behavior, which by definition simply follows the program, I say the advantage of programming is supposed to be the ability to modify the program to suit user needs. Maybe there should be a greater effort to collect suggestions or poll users about how they’d like AI, driver commands, and session rules improved.
I don’t find it helpful to bash users for critiquing the absence of such features. I do find it helpful and creative to hear ideas for changes to AI behavior and improved user options that could make Trainz more fun for all. Even if they are not implemented.
For the OP, I suggest Trainz should have a selectable driver command, “no reverse” which can remain in effect while other commands execute or until deactivated. If the user wants a direction marker to be absolute, Trainz should have a setting for that, either session rules, driver commands, or an option when placing the marker. Or portals could have more option — like trains from portals do not reverse. (I’m not too familiar with portals.)
AI throwing switches under driver-controlled trains or throwing switches under trains when user takes control? Trainz should add commands, session rules, or pop up check boxes to prevent this, and probably set them as the default. Is that so hard for N3V to program? I wouldn’t think so.
Ideally such mods should be an available depending on user creativity, and not relying on N3V to do it all centrally. I know there are a few session rules on the DLS, but it’s not easy to find those or search them for solutions.
For those who miss the old ways, when trains would back up to the end of the line and stop, or engines that start to “run around” and then just keep going to the end of the route, there could be a “restore legacy settings” option. For those extolling the predictable logic of present AI behavior, which by definition simply follows the program, I say the advantage of programming is supposed to be the ability to modify the program to suit user needs. Maybe there should be a greater effort to collect suggestions or poll users about how they’d like AI, driver commands, and session rules improved.
I don’t find it helpful to bash users for critiquing the absence of such features. I do find it helpful and creative to hear ideas for changes to AI behavior and improved user options that could make Trainz more fun for all. Even if they are not implemented.
