Calling at stations (or not)

P

pfx

Well-known member
I'm using AJS stations on a route and on trying to do an AI test run to make sure everything is okay, found an error I haven't seen listed in the station kit FAQ. I don't think the error is with the stations though. Here is an explanation.

There are currently 4 stations on the route, a terminus and 3 through stations. Trains will travel between the terminus and outermost through station without any problem (and also to these 2 stations from any point on the route) so I know it's nothing to do with track connections. The problem occurs if I instruct a train to Call At or Drive To any of the intermediate stations. On doing so, a red circle with an X appears on the driver command list. I don't get any warning other than that.

As I said, there's no mention of something similar in the Station Kit FAQ so is anyone able to shed light on this problem at all?

Thanks.
 
It's all in the name

Pfx, Have you set the instuctions in the session? If so it sounds like you may have changed the name of the stations since you set the instuctions as this is the only time I have had this happen with any industry.

HTH

Andi
 
Thank for the responses guys.

@ honeymonster1971 - I haven't made any changes to the session since I created it. The stations were all added and named within the session and I haven't got as far as setting up AI trains other than the one I used to do the failed test. I haven't done anything different from previous routes I've built but it's the first time I've seen this error.

@ FrankZ - All I get is "Call at 'station name', track_1"

I can drive to all stations manually and everything works as it should. Passengers get on and off. It's just the AI that's up the left.
 
I think the error you're getting is that Call At might be shown as available in the orders list because the stations require that rule to function, but you haven't downloaded the rule? Or perhaps the rule has been updated since and the stations you are using require the update.

If the above isn't your case, try placing a track mark a few hundred metres before the station you want to Call At and tell the driver to Navigate Via Trackmark before Call At. The problem might be that the range between stations is too far for the Call At function to find.

I had a similar situation where stations were around 5km apart. I tried sending the driver Call At S1, Unload, Load, Call at S2, Unload, Load, etc etc, but because the distance was too great between stations the driver would just sit at S1 after Loading and do nothing.
 
@ FirstSoloFlight - I'll give that a bash though as the first and last stations on the route are well beyond the 5k mark, it would be an odd issue given it's the intermediate stations I can't get the consists to 'call at'. Tis most frustrating.
 
The stations do NOT require Call-At to be installed, and in any event it won't be available in the command list unless its installed. Call-At is effectively a wrapper for the built in Drive-To and distance will not be a factor either.
 
Actually, the problem is not related to the Call At or Drive to commands - this usually happens if you change the name of a station (or even use a smaller/different station without naming it) without updating the schedule.

Example (using Drive To or Call At)

Schedule: Station A>Station B>Station C>Station D

If you then change the name of Station C to (for example) Station 3, this is the result you get:

Schedule: Station A>Station B>Station C>Station D

What should be done is to change the schedule (which in this example, would be):

Schedule: Station A>Station B>Station 3>Station D

Hopefully this example answers your question.

(The same applies if you change the amount of platforms)

Shane
 
@ andi - I was pretty certain that the problem wasn't related to any of your assets from the start as it looks like a Trainz error.

@ shane - I hadn't changed any names at all or created a schedule prior to the first test run.

I've tried removing the stations and replacing them without success. I've also tried creating a new session, again with no success.

The only pointer I have so far is for a working station. In the driver command schedule, the tooltip shows 'Call at Someplace, platform 1' and for a non-working station it displays as 'Call at Otherplace, track_1'. This track_1 error is the thing that looks most likely to be the problem. if I could track the reason for it down (no pun intended) I would probably have the answer to the problem.
 
I remember having a few problems myself involving AJS stations - it may be worth checking that you have all the required dependencies, and to see if using Drive To instead of Call At or vice-versa helps.

To be honest, the only time I've seen that problem is if I've changed a station without updating the schedule, or if I've used a station with a faulty or missing station script.

Shane
 
@ Shane - Thanks for the sugeestions. First thing I tried was Drive To but no joy.

I've tried the same rule in another route I have which uses the AJS stations and it works fine so I don't think any dependencies missing unless they've gone AWOL in a non-Van Damme sort of way since my last route.

If I can't get this fixed, I will probably have to bin the route which would be rather annoying given the time I've spent on it.
 
I have had this problem a few times over the years, only solution was to swap the station. There are two types of AJS station (AJS invisible and AJS station. Can't remember right now but something like that) and the older of the two throws this up at random. I just lay a new station on top of the old one, line it up in place, delete the old one, reconnect the track and rename it, hey presto.Only takes a couple of minutes. Have never figured out what causes it though.
 
Deano5 is correct - that should fix the problem.

I believe the issue affects the AJS Passengers asset(s) - the problem should not happen if you use the AJS Invisible Station (number of tracks)T.

Shane
 
Thanks for the help folks. I was trying not to use the invisible station as the passengers all stand in a clump when I use it but it looks like that's going to be my only option (that's if they work, I'll maybe find out later).

Cheers.
 
If he uses AJS Invisible Station it, unfortunately, does not. Length setting in AJS Inv. Sta. only affects door animation of the train, not the spreading of the passengers.
 
I'd better start TS09 bashing like some people do when it doesn't work or some people who haven't even used it in some cases do! Hehe. I'll let the hare sit for a while and come back to this.

Thanks for the suggestions though.
 
testing?

pfx, Would you like me to test this route/session for you to see if I'm getting the same problem?

I've got 09 & 10 installed at present.

Andi
 
Last edited:
Thanks for the offer Andi. Most appreciated. I'll have to go through it and remove a load of payware items that are included. I'll give you a shout once I get it sorted.
 
no problem, just PM me your email addy when your ready and I'll drop you an email in return

Andi

P.S. PM what payware is used as I might have it and it'll say you deleting it :)
 
Last edited:
You must log in or register to reply here.

Similar threads

A
how to change passenger height on invisible stations?
Replies
3
Views
124
AntonyVW
A
P
How do you change the platform numbers for AJS Invisible Station?
Replies
2
Views
232
PhilChorusch01
P
D
Has this stopped working? FIXED!
Replies
0
Views
322
davesnow
D
P
Un-Portal 3 Extended rule - 'Consist 1' not appearing
Replies
0
Views
123
paulper
P
R
JTG xStation in Schwaninger Land
Replies
2
Views
187
RobWed
R
Back
Top