Asset problem: DriveToStation V2 by pguy (TS2009 SP4)

[shaneturner12]

I have installed (without any errors) and added the command into a driver session on a few of my trains.

Unfortunately, when one of my trains that has the command added (to send the train to the first available random platform) the train seems to just sit there and do nothing (not even kicking out the schedule) - the signals are working properly (to what I can see, anyway)

The really odd thing is if I use the Navigate To command (the builtin one) the train moves normally.

Any ideas? (I have even re-downloaded it)

Trainz version affected: TS2009 SP4 (build 44653)

Shane

EDIT: It's happening with any train that has this command as it's next item.

 

[shaneturner12]

I've had to bump this thread as it is an urgent problem - I cannot run my session properly until I can fix this problem (as it will take too long to revert the commands (and anyway, I prefer to allocate available platforms rather than 1 specific platform)

Shane

 

[JCitron]

I've had to bump this thread as it is an urgent problem - I cannot run my session properly until I can fix this problem (as it will take too long to revert the commands (and anyway, I prefer to allocate available platforms rather than 1 specific platform)

Shane

Is it only one driver?

Have you tried reducing the number of drivers if there are too many?

Sometimes the AI get just dumb. I've had some places on my route where all the drivers except for one will be able to negotiate through some junctions. This one particular driver will sit there and put up a message until I manually flip a junction over. Then he'll proceed until the next one.

Who knows why? I can't figure it out.

John

 

[shaneturner12]

I will have a look - the strange thing is that if I use the normal Navigate to <station> command, the train moves fine. If I use the DriveToStation command, the train just sits there - no errors, no kicking out of schedules or anything. It's as if the command isn't actually doing anything.

Shane

EDIT: It's multiple drivers that are affected, and it's both manual and portal-generated trains.

 

[Lots_Trains]

Hi Shane

Have you enter the Trackmarks into Quick SessionsVars2, its a new way of entering trackmarks for Drive to Station v2

If you are stuck on the format let me know

Cheers

Lots

 

[shaneturner12]

I will have a look - for some reason, there was no mention of that in the asset description.

Shane

EDIT: I'm a bit puzzled now - the command used to work a few months back, then I reinstalled the command and it's acting up.

 

[Lots_Trains]

I found the old version of Drive to Trackmarklist was very tempermental in 2009 so Pierre updated to V2 I've never had a problem with it since

But Version 2 uses Quick SessionVars 2

Cheers

Lots

 

[shaneturner12]

I think we've crossed wires here - you seem to be discussing DriveToTrackmarkList V2, whereas the problem I am having affects DriveToStation V2 (which I would have thought wouldn't have needed trackmarks)

Shane

 

[Lots_Trains]

One in the same mate, just a slight variation in code, but essentially they are the same, both made at the same time, I know I beta them.

Cheers

Lots

 

[shaneturner12]

Fair enough - how is the best way of getting the command working properly?

Shane

 

[Lots_Trains]

Have you entered the stations into Quick SessionVars 2, they have to be in in Andi06 naming convention.

In Quick SessionVars goto "Lists" and you will see "string table" on the right click on that if you have the naming convention correct they should show in there. You add a list and then add values to it. Its all menu driven and is much easier to use compared to the old system.

Cheers

Lots

 

[shaneturner12]

I will have a look.

Quick question: If the stations are not AJS ones, does the command still work? (I'm using Station Through 8t)

Shane

EDIT: The list is reporting as empty, even though I have stations that follow andi06's naming conventions.

 

[Lots_Trains]

Ok that should have worked. I'll get a hold Pierre for ya.

Cheers

Lots

Edit: As a quick thought just to a test using the Trackmarklist v2 just to confirm you understand the process I know thats working 100% I used it yestersday

 

[shaneturner12]

Thankyou - things do not seem to be working well for me lately with Trainz

(For some reason, I do not remember having to have the QuickSessionVars rule last time I used DriveToStation - also, I've noticed that it should be showing 2 menus, not just 1 (according to the asset description for DriveToStation)

Shane

EDIT: I will have a try with DriveToTrackmarkList.

 

[Lots_Trains]

Hi Shane

I found with the old versions of Pierre's Driveto's that if they were set up in 2006 they worked fine in 2009 and 2010. if for some reason you have changed or deleted them the old rules will not work in 2009/2010 you have use the new v2 of these rules/commands.

How does that match with what you have seen?

Cheers

Alan

 

[shaneturner12]

An update...

The trackmark list seems to be ok in QuickSessionVars V2, but the string list is still not populating itself. Is there a possibility of the problem being that there is a space in the station name (not within the brackets)

Shane

EDIT: DriveToTrackmarkList is working properly.

 

[shaneturner12]

Not sure - I am using V2 of both commands in 09 SP4.

I'm beginning to wonder if something in SP4 is interfering with the DriveToStation command or the QuickSessionVars rule.

Also, I've noticed that QuickSessionVars is not listed as a dependency, but SessionVariables (a built-in one) is.

Also, it appears that DriveToStation is using a different method, as there are already the station names in the list (but not in QuickSessionVars)

Shane

 

[pguy]

Sorry for the late answer, but I am out home with some internet forum access but no access to my script source code until next Wednesday, so I won't be able to look to the problem until Wednesday next week.

DriveToTrackMarkList v2 and DriveToStation v2 uses an internal library pglib that contains the script code for listing the trackmark list and the station list and it is the code in this library which merges the native trackmark list (using naming convention A(1) A(2) ... ) and native station list (from the stations on the route) with list definition from QuickSessionVars. So it should work with native list without QuickSessionVars definitions.

There has been no change in pglib on DLS since May 2nd, so I don't have any explanation while thing working in May do not longer work now. But I have released private beta new version of pglib with some other beta versions of other driver commands and if you have got one of this beta release it may have broken DriveToStation. If your pglib asset is not kuid2:61392:4001:2 just disable in CMP the pglib assets newer than version 2 to return to version 2 and look if you have still the problem.

In any case, I should be back home on wednesday evening CET time and will have a look to the problem on that evening.

Sorry for the delay and have a nice day.

 

[shaneturner12]

Thankyou for the response pguy.

I am using the latest (non-beta) version of pglib (<kuid2:61392:4001:2>)

To assist you in finding the problem:

The stations are appearing normally in the list (albeit in one long list - may be worth splitting the list into alphabetical groups)

When the command is added in Surveyor, it appears normally (should it simply be appearing as navtosta//rnd ? - on DriveToTrackmarkList it's got a name in between the two / symbols).

When the session is run in Driver though, any trains with the command simply refuse to do anything - they do not even kick out the schedule or go on to the next command.

Hopefully this information will help find the problem (also, as stated above, I'm using TS2009 SP4, which acts like TS2010 - I think the last working version may have been on TS2009 SP3)

Shane

 

[shaneturner12]

A quick question to other users - is anyone else sucesfully using this driver command (<kuid2:61392:7002:2>) on their route, or am I one of a very small minority?

Shane