In TRS 2019, I can stack trains on a trackmark, ie I can navigate a train to a certain trackmark, it will go there and stop. When I navigate a second train to the same trackmark, it would pull up behind the first train and sit there until the first train leaves, then it would pull up to trackmark. But in TRS 2022PE, navigate to the trackmark, it will avoid the train and bypass the track. If I use "Drive to" it will pull up behind the first train, sit there for a few minutes and then reverse away. Is there a way to get 2022 to do like 2019 does? Thanks.
Stacking tarins on a Trackmark
- Thread starter Mouse84
- Start date
I'm surprised no-one has responded to this post. I have developed several extensive routes over the years with lots of timetabled movements and it seems that whenever there is a new version or an update, SOMETHING goes wrong and screws everything up. The Call at command has now been fixed but why did that break in the first place and why did it take so long to be fixed? This problem of changed "Drive to Trackmark" AI behaviour is a major problem in an AI controlled siding or engine shed. On a different note, is there no way with AI to reduce the spacing between engines parked in a shed, rather than have to take over manually?
Bob
The code has changed with the Navigate to and Drive to commands. I've run into the same situation and have had to modify my driver schedules to reflect the change.
KotangaGirl
Pre-Grouping Railways Nut
That's the reason why so many of us are still running TS2019/TRS19.
Thanks - that's interesting to know John. So you're saying that the coding has been changed deliberately with no regard to those of us who have paid up and spent hours and hours developing routes over the years? Why should we have to change our "codings" and spend a lot of time to try to get things working again? No warnings/no explanations? I have gone through periods of exasperation with N3V in the past and here we go again. Don't know what you think John, I know you're a lot time member, but I'm wondering why I'm paying monthly for an "upgrade" rather than sticking with TRS19
I'll leave my non-G-rated comment out of it. I know how you feel and my feelings are mutual.
To be fair, it could be that the crew finally fixed the commands to work properly. The problem is their fix, if you want, we can put the air quotes are around it " ", broke what we had already created. Not in all cases, but enough to be annoying.
The Drive to command is supposed to make the driver toe the line and wait patiently rather than find the quickest, but not always the most direct, path to their destination. The Navigate to command does just that and for the most part it works fine, especially out in the countryside where there's not a whole lot going on.
The problem is we've already built everything around the old behavior. On my very large route, I have about 200 miles if not more of mainlines, branches and yards. I have found that drivers tend to sit in some locations and back up rather than head to their next destination like they did before. To get around that, I had to put in extra track marks and use the Drive to track mark then Navigate to the next station instead of using Navigate to the next station directly. To make matters worse, it isn't all of the driver routes on this massive route. Some do it, some don't and I can't tell who has the problem until I take a ride with them.
On my very small but busy Gloucester Terminal route, a tram and freight operation about 7.5 miles long end to end not counting the docklands and branches, drivers will back up rather than sit patiently and wait in the queue to pull up to a station like they used to. In real life, this is quite common with trams as you know. I remember seeing this when I used to take the light rail in Boston for many years.
Now, I understand fixing bugs and whatnot to make operation smoother. That's what we pay them for through our purchases and subscriptions. What would be nice is if they could tell us that changes have been made or are going to be made before an update is released. This has been a common problem with N3V all along. The developers will "fix" something and tell us after the fact that they made the change with some cases being quite severe such as the most round with the throttle positions for electric locomotives that many of the Eastern European and Russian content creators are running into. The previous headache has left the Content Repair Group with a mess due to broken scripts. Without telling the community, signals, some MO-crossing assets, iPortal, and coupling scripts no longer work just to name some of the assets. To make matters worse, many of the original authors are no longer with us, sadly due to many reasons, and they had encrypted their scripts.
It would be nice if they used the "Announcements" thread for something other than Itrainz server maintenance. Think of all the announcements they could make!
I spent a long long long time a few years ago building a complete all day AI working model of Heathrow Airport which I have not yet transferred to TRS22 and I am now expecting that aircraft lining up for take off are now going to back up into the path of aircraft that have landed and making their way to gates. Expect it will be a complete shambles but can't even check it out now. Tried loading it to TRS19 just now to see what happens and the whole of the driver set up is missing - a "script error".
I really do despair .......
I really do despair .......
It's not. They have a new help-me form. They still get the messages. I sent them one regarding the DLS outage and they responded back to me the next day.
Post that in a different thread along with the error and we can take a look at it.
It is the weekend. Wait until Monday morning Australia time.