.
Results 1 to 9 of 9

Thread: WaitForTrigger greyed out...

  1. #1
    Join Date
    Jul 2011
    Location
    Netherlands
    Posts
    263
     

    Default WaitForTrigger greyed out...

    Hi,

    I'm adapting an older session with various trains/drivers waiting en route until some other trains pass triggers.
    Driver Setup has for each driver/train various Navigate Via commands, preceded by WaitForTrigger, except this WaitForTrigger command is greyed out when selected.

    I've set up a test track with some trains/drivers and triggers, and then WaitForTrigger can be used in Driver Setup without problems. So what would cause this command to be greyed out in my older session?

    Thanks for any assistance.

  2. #2
    Join Date
    Nov 2006
    Location
    Australia, NSW, Sydney
    Posts
    8,218
    Blog Entries
    3
     

    Default

    One possibility: How many triggers and/or locos are in your older session? Some driver commands will "time out" because they have too many target objects (e.g. triggers or locos) to search through to find the one they need.
    Trainz Plus (TRS19) build 114800 (SP4)
    Trainz Plus (TRS22) build 115373 (beta)
    Trainz Simulator 3 (Mobile)

  3. #3
    Join Date
    Jul 2011
    Location
    Netherlands
    Posts
    263
     

    Default

    You could be right about the number of target objects.

    BTW, my old session had 9 portals (part of UnPortal2) each emitting a single train with CPC:Emit Train, activated with TriggerCheck and Check Trackside rules.
    Unfortunately, the CPC:Emit Train command does not work in 114800/114841 (bug reported weeks ago), so now I try the workaround of placing these trains on the route, only to be released by the WaitForTrigger command. The triggers are in place (show up with Find Object), but don't show when entering the WaitForUser command in Driver Setup. I checked all the applicable layers are open; and of course those non-working portals and TriggerCheck/Check Trackside rules have been deleted.

    Still stumped...

  4. #4
    Join Date
    Nov 2006
    Location
    Netherlands
    Posts
    842
     

    Default

    hoi, Heb ooit eens een gerepareerde versie gemaakt
    https://www.mediafire.com/file/33vjk...er_v2.cdp/file
    werkt bij veel treinen en grote route, wel eerst toevoegen aan de driver commands

    english: made a repaired version

  5. #5
    Join Date
    May 2018
    Location
    Australia, NSW
    Posts
    2,006
     

    Default

    I found that problem in the Port Tillamook route as it had in excess of 1,000 triggers and a dozen or more built-in locos. Reducing that number solved that problem.
    Working on Trainz.

  6. #6
    Join Date
    Jul 2011
    Location
    Netherlands
    Posts
    263
     

    Default

    @G.M. Your Wait For Trigger v2 didn't work in a test session with only a couple of triggers: with a choice of "Trigger0" and "Trigger1", either choice registered as "trig".

    @pware @Alikiwi Most likely an issue with large number of triggers, since there is no problem in a test session with only two triggers.

    Of course, even better would be "CPC:Emit Train" working properly...here's hoping...

  7. #7
    Join Date
    Nov 2006
    Location
    Netherlands
    Posts
    842
     

    Default

    No idea what goes wrong there, just tested it again and works fine here, this is how it looks here in surveyor

  8. #8
    Join Date
    Nov 2007
    Location
    United States of America, Pennsylvania, Murrysville
    Posts
    4,179
     

    Default

    Central Portal Control EMIT TRAIN at start of session works in my case :: Build 114800.

    I am only using one portal for now, which may be a factor.
    Dick near Pittsburgh, Pa. i5-2500K 4.2ghz, 8gb memory, GTX1060 3gb video card. 111951 & 115373

  9. #9

    Default

    I had a similar problem with the copy schedule from command. So I copied the driver set up or schedule library rule from the original route and pasted it into a new session of the same route. As all the other rules were not present I could add more copy schedule from commands to my drivers. I then copied the driver set up rule and pasted it back into the original session. All the commands remained in place and worked as they should.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •