Repositioning AI trains after session leaves a residual movement.

[Orpheus2000]

I have a TRS19 route with an AI session using 20 or so trains which are all at their various "start" locations to begin with. If I run the session and it eventually fails I exit Driver mode without saving.

Occasionally when I have corrected the problem and restarted the session, I find some of the trains are not at the start positions - why, I don't know, maybe I did save the interrupted session, no matter. So I stop, move the particular trains to where they should be, save the session and then restart it.

The trains that have been reset immediately move briefly, as if they don't realise for a moment or two that they have been reset. So far I have only been able to fix this by deleting the train and then reinstating it, which is a bit of a faff if several trains are involved. Anyone know of a neater way to clear this "residual movement"?

 

[stagecoach]

Did you select edit session from the drop-down menu in Surveyor and click on reset at the bottom?

 

[Orpheus2000]

Did you select edit session from the drop-down menu in Surveyor and click on reset at the bottom?

I think you are referring to the "restart all rules" button. I have used that when it's not "greyed out", but it's not the solution in this case.

 

[Lewiscc65]

I had the same problem for some time and have not been able to find a solution yet either. I know it is a pain in the a** to move all the trains to their original location and I put a stop command in the driver set up menu of all trains, so they do not go too far.

 

[Orpheus2000]

I had the same problem for some time and have not been able to find a solution yet either. I know it is a pain in the a** to move all the trains to their original location and I put a stop command in the driver set up menu of all trains, so they do not go too far.

I don't mind putting them all back so much. It's just that irritating bit of movement on subsequent restarts. Glad to hear it's not just me, anyway.

 

[Orpheus2000]

I have a TRS19 route with an AI session using 20 or so trains which are all at their various "start" locations to begin with. If I run the session and it eventually fails I exit Driver mode without saving.

Occasionally when I have corrected the problem and restarted the session, I find some of the trains are not at the start positions - why, I don't know, maybe I did save the interrupted session, no matter. So I stop, move the particular trains to where they should be, save the session and then restart it.

The trains that have been reset immediately move briefly, as if they don't realise for a moment or two that they have been reset. So far I have only been able to fix this by deleting the train and then reinstating it, which is a bit of a faff if several trains are involved. Anyone know of a neater way to clear this "residual movement"?

I'm raising this item again hoping that someone has discovered what's going on. In the meantime I have moved the route and sessions to TRS22, although that makes no difference here.

There must be a file somewhere that retains the information on the trains' movements as they were immediately before the Exit Driver (without saving) command, and if so it might be possible to fix the problem. And I wish I knew how this problem arises in the first place.

The only way I know to straighten it out is to delete and replace each loco, which is a bit of a fag when you have a lot of trains in the session.

 

[JCitron]

I'm raising this item again hoping that someone has discovered what's going on. In the meantime I have moved the route and sessions to TRS22, although that makes no difference here.

There must be a file somewhere that retains the information on the trains' movements as they were immediately before the Exit Driver (without saving) command, and if so it might be possible to fix the problem. And I wish I knew how this problem arises in the first place.

The only way I know to straighten it out is to delete and replace each loco, which is a bit of a fag when you have a lot of trains in the session.

In TRS22 and its relations including Plus, there's UDS or Universal Driver Surveyor. UDS allows us to go in and edit a session and route on the fly to fix things such as adjusting trees that are in the way of the track, or fixing a driver's command because we've somehow put commands in the wrong order.

This is well and good, but the problem is when saving a route or session on the fly, this saves the current position of the AI. It makes sense why this occurs but the problem is there's no way to reposition the AI back to their starting position.

In the past, I've made a suggestion for an option to not only reset the driver commands, which we can do when things get messed up, but to also reset the AI back to their starting positions. This would in effect reset the session.

This option could be offered all the time for private routes and sessions but can be optionally disabled for DLC routes should the author decide that this option shouldn't be allowed just as they enable award points and route navigation points in their sessions.

When I made this suggestion, the thread died and the only people or critters visiting were crickets. It's as if I put something down that scared everyone away as typically happens when I've pointed out a glaring bug or something that might make sense such as this.

 

[stagecoach]

If trains are in the wrong position, then a save while in or exiting driver mode has taken place. Reset all trains and reset the rules, and then save as a new session. This should erase the session memory of where those misplaced locos were. Keep a base session that has everything in its start position.

 

[Orpheus2000]

In TRS22 and its relations including Plus, there's UDS or Universal Driver Surveyor. UDS allows us to go in and edit a session and route on the fly to fix things such as adjusting trees that are in the way of the track, or fixing a driver's command because we've somehow put commands in the wrong order.

And yet I've always tried to make sure I choose the "do not save the session" option whenever I've exited Driver Mode, either by the direct "Exit Driver" route or after editing the route during a TRS22 session.

n the past, I've made a suggestion for an option to not only reset the driver commands, which we can do when things get messed up, but to also reset the AI back to their starting positions. This would in effect reset the session.

Yes, this type of session reset would be most useful.

When I made this suggestion, the thread died and the only people or critters visiting were crickets. It's as if I put something down that scared everyone away as typically happens when I've pointed out a glaring bug or something that might make sense such as this.

Why am I not surprised?

 

[Orpheus2000]

If trains are in the wrong position, then a save while in or exiting driver mode has taken place. Reset all trains and reset the rules, and then save as a new session. This should erase the session memory of where those misplaced locos were. Keep a base session that has everything in its start position.

I tried this, but the new session seemed to contain exactly the same problem, but I will try again.

The idea of keeping a base session is sensible, of course, but in the past I've found the backup gets out of step eventually - I make very frequent changes to a session and sometimes forget to update the base version.

 

[Lewiscc65]

I have run into that problem more than once, LOL. What I did was enter the "STOP" command as the first entry in all the trains commands. This seemed to fix the problem.

 

[JCitron]

The idea of keeping a base session is sensible, of course, but in the past I've found the backup gets out of step eventually - I make very frequent changes to a session and sometimes forget to update the base version.

I've done the same with a base session and I also ran into the same situation. I ended up creating a base session from the current session and then that led to another and another. One time I forgot and ended up going back to the older one and had to redo my new driver setup all over again.

This shouldn't require a master's degree and a retired brain on full steam just to play a video game. Oh, sorry it's not a game, I shouldn't've said that.

 

[stagecoach]

It would seem that the session has come from a save while in driver mode or exiting from driver mode. This would include a save while using UDS. You can start a new session and copy all the different setup rules to the new session.

How to Use Driver Setup Rule - TrainzOnline

online.ts2009.com

 

[JCitron]

It would seem that the session has come from a save while in driver mode or exiting from driver mode. This would include a save while using UDS. You can start a new session and copy all the different setup rules to the new session.

How to Use Driver Setup Rule - TrainzOnline

online.ts2009.com

Yes, but that's yet another step to doing something that should be so simple. To put it bluntly, it's the N3V devs over thinking and making things more complex than they should be because they don't use the product.

 

[OddRails]

The easiest solution is to never edit in a session that has been running. That invalidates the usefullness of UDS though.
It would be better to use a session you don't care about when bouncing between surveyor mode and driver mode.
I guess I should try some of the suggestions, but I've never been able to properly restore a session after using UDS.