No Scroll Bars when using trigger
- Thread starter rmdk
- Start date
shaneturner12
Tutorial Creator
This is a known issue with quite a few commands in Trainz. Only solution at this stage is to have less trains (unless you can get the creator to categorise the list, which they may not be willing to do).
Shane
Shane
shaneturner12
Tutorial Creator
It's command related rather than version related, so it's up to the command's creator on whether they fix this or not in most cases.
Shane
Shane
captainkman
You are reading this.
It might be worth sending the creator of the command a polite email regarding the issue and asking if they'd be kind enough to take a look at preparing and update. 
Kieran.
Kieran.
A while go, I sent off an email to the author. As yet I haven't received any acknowledgement of my email from him. Maybe he is not doing 'Trainz' any more???
Are there any other variations of this command, or work arounds? Or is there a smart cookie out there in Trainzland, who can write a similar command?
Russell
Are there any other variations of this command, or work arounds? Or is there a smart cookie out there in Trainzland, who can write a similar command?
Russell
The "Wait for trigger" command is flawed. For years I have been fighting it and can't use it. Worst, no body has ben able to come with a solution. When I add it to the list of commands available, it slows down all the other menus so much that it takes forever to do simple things. So I had to delete it. Deleting returns the speed of menu-show up, so things go back to normal. Help desk, years ago was not able to come with a solution, blaming it on the creator.
I did recently see something nifty that might be a work around for the wait for trigger but I can only tell you where I saw it. There is a route "Cattaraugus Creek & Lake Erie by msgsapper. His most recent variation <kuid2:439337:100162:10> (nice route!) has some sessions. "Cattaraugus Creek & Lake Erie Local Freight 1 Summer" I noticed has some creative uses for triggers.
There is a train sitting on a siding doing nothing. When the users train passes a specific trigger, the system will assign orders to the sitting consist. There is no wait for trigger, its more of a push.
"Msgsapper" can you elaborate further?
There is a train sitting on a siding doing nothing. When the users train passes a specific trigger, the system will assign orders to the sitting consist. There is no wait for trigger, its more of a push.
"Msgsapper" can you elaborate further?
Something like this can be done with the aid of Atilabarut's driver command: WaitUntilSVariable <kuid:131986:1006>.
A bit of setup is needed but the principle is to have the waiting train (A) execute the above command. When the user's train (B) reaches the trigger where the action is to begin, it triggers a rule that modifies the variable that train (A) is waiting for so that the conditions are met and train(A)'s schedule proceeds to the next command.
A variation on this theme is to have train (B) issue a command ChangeSVariables <kuid:131986:1005> instead.
The instructions for setting up the variable name and values in the InputTable rule are contained in the above-mentioned commands. The InputTable rule is built in to some Trainz versions.
If the 'rule' method is chosen then add a 'Trigger Check' rule and use the built-in child rule 'Variable modify' to change the value of the variable.
By default, a variable 'Score' is declared, so if that isn't being used elsewhere it will serve the purpose.
Good Luck
Trevor
A bit of setup is needed but the principle is to have the waiting train (A) execute the above command. When the user's train (B) reaches the trigger where the action is to begin, it triggers a rule that modifies the variable that train (A) is waiting for so that the conditions are met and train(A)'s schedule proceeds to the next command.
A variation on this theme is to have train (B) issue a command ChangeSVariables <kuid:131986:1005> instead.
The instructions for setting up the variable name and values in the InputTable rule are contained in the above-mentioned commands. The InputTable rule is built in to some Trainz versions.
If the 'rule' method is chosen then add a 'Trigger Check' rule and use the built-in child rule 'Variable modify' to change the value of the variable.
By default, a variable 'Score' is declared, so if that isn't being used elsewhere it will serve the purpose.
Good Luck
Trevor
Last edited:
In this thread:
http://forums.auran.com/trainz/showthread.php?95011-Turnout-Naming&p=1312126#post1312126
Pendolino uses the ~ in the names of trackmarks to force them into groups of his choice. It might be worth trying with the names of locomotives. I realise this might involve a fair bit of work renaming all the locomotives but compared to the time spent creating a route or session it should be manageable.
http://forums.auran.com/trainz/showthread.php?95011-Turnout-Naming&p=1312126#post1312126
Pendolino uses the ~ in the names of trackmarks to force them into groups of his choice. It might be worth trying with the names of locomotives. I realise this might involve a fair bit of work renaming all the locomotives but compared to the time spent creating a route or session it should be manageable.
This idea was tried and found unworkable in the above cited thread. However, I added a partial work-around possibility that might sometimes work to the scrollbar issue here in the same thread. Basically, since the software system lists all locos, including those with multiple head locos, temporarily delete the B and/or C&D units in multiple loco heads, write the session, then put them back with one of the tracking methods suggested after the session has been 'coded'. Additional locos then don't push the list. Course, you're screwed if the base list of single locos is too long, but you can't have everything! // Frank
