.
Results 1 to 9 of 9

Thread: Variable setup - possible bug

  1. #1
    Join Date
    Nov 2006
    Location
    At the end of the Line
    Posts
    750
     

    Default Variable setup - possible bug

    I'm running build 103369. I have a session where I have set up a shunt in a power station and used session variables to control it

    I have used the Input Table rule kuid2:131986:1012:1 to define the variables and operators to be used on them, and the Variable Modify rule kuid:-25:1050 to allocate initial values to them (to represent a partly-unloaded train, with some wagons still in the LWS (Loaded Wagon Sidings) and some already transferred to the EWS) - both as top-level rules run at session startup.
    I then use a series of Set S-Variable kuid2:160293:101005:5 and ChangeSVariables kuid:131986:1005 DriverCommands to control the AI shunting loco, and Variable Modify child rules (as the player-train brings in a loaded and takes away an empty consist) to adjust the values as the session progresses.

    This worked as expected in TANE, but failed in TRS19.

    I have found out this failure is because during the initial setup the Variable Modify rule doubles the values allocated to the variables to represent the number of wagons in the LWS and EWS, so confusing the AI shunting loco. All the other operations are OK.

    Is this doubling a bug - in TRS2019 or in the Input Table rule?

    Any ideas before I put in a bug report?

    Thanks

    Edit:- Bug report submitted
    Last edited by davidbird; October 21st, 2019 at 02:50 AM.
    Mountains, Sea, Islands and Steam Trains from my living-room window!
    What more could anybody want?

    TRS2019 Build 103369

  2. #2
    Join Date
    Nov 2006
    Location
    At the end of the Line
    Posts
    750
     

    Default

    Update

    I added another top-level instance of the Variable Modify rule , which worked just as expected.

    So I deleted the original VM rules, but when the session was ran again, the values were still modified - this time to the expected value - although the rules were no longer in the session!

    I seem to have "ghost" copies of the rule, possibly from when the session was either imported from TANE to TRS19, or TRS19 updated to the beta 103369.

    Bug report updated, but does anyone here have any ideas?
    Mountains, Sea, Islands and Steam Trains from my living-room window!
    What more could anybody want?

    TRS2019 Build 103369

  3. #3
    Join Date
    Nov 2006
    Location
    Australia, NSW, Sydney
    Posts
    5,841
    Blog Entries
    3
     

    Default

    I use the Variable Modify Rule, Variable Check Rule, Variable Random Rule and Variable Show Rule in my sessions and have not come across this issue. I have never used the variable driver commands or the Input Table Rule that you have mentioned.

    Is it possible that using two sets of different operations, Rules and Driver Commands, to set and alter the variables is the problem?
    A member of the "Party Machine". Now if only I could remember where they are holding the party!

  4. #4
    Join Date
    Feb 2008
    Location
    United Kingdom
    Posts
    2,015
     

    Default

    Hi David

    I've noticed on more than one occasion that in sessions brought in from TANE the driver commands often don't work correctly, if at all. Removing them and re-entering them will cure the problem. I've not noticed this with rules though so far.

    Regards

    Brian

  5. #5
    Join Date
    Nov 2006
    Location
    At the end of the Line
    Posts
    750
     

    Default

    Quote Originally Posted by pware View Post
    I use the Variable Modify Rule, Variable Check Rule, Variable Random Rule and Variable Show Rule in my sessions and have not come across this issue. I have never used the variable driver commands or the Input Table Rule that you have mentioned.
    I tried deleting the Input Table rule - all runs properly - but the Input Table is necessary to setup the driver commands to use the variables, so I've re-instated it.
    Quote Originally Posted by pware View Post
    Is it possible that using two sets of different operations, Rules and Driver Commands, to set and alter the variables is the problem?
    Don't think this can be the problem as the recently added Variable Modify rule works OK, and the "Ghost" values (from the now-deleted Variable Modify rules) appear immediately at session startup, while the driver commands are not activated until more than a minute into the session.

    I definitely consider it is "ghosts" of the Variable Modify rule...
    Mountains, Sea, Islands and Steam Trains from my living-room window!
    What more could anybody want?

    TRS2019 Build 103369

  6. #6
    Join Date
    Nov 2006
    Location
    At the end of the Line
    Posts
    750
     

    Default

    Quote Originally Posted by Kennilworth View Post
    Hi David

    I've noticed on more than one occasion that in sessions brought in from TANE the driver commands often don't work correctly, if at all. Removing them and re-entering them will cure the problem. I've not noticed this with rules though so far.

    Regards

    Brian
    Thanks Brian,
    As far as I can tell, the driver commands are working as expected. Deleting the Variable Modify rule and re-entering it just brings the problem back.

    Of course, I can completely solve the problem simply by deleting the Variable Modify rule... but that shouldn't work!
    And, as the rule is a built-in, I can't delete it from CM and do a "Remove Missing Assets" from the session.
    So how do I remove these ghosts?
    Mountains, Sea, Islands and Steam Trains from my living-room window!
    What more could anybody want?

    TRS2019 Build 103369

  7. #7
    Join Date
    Nov 2006
    Location
    South Africa, West Cape, Sedgefield
    Posts
    1,040
     

    Default

    Hi David - Could you try using "Delete Missing Assets" anyway? That option seems to get rid of ghost trains and might also work for ghost rules.

    Incidentally, "Set S-Variable" is a replacement for "ChangeSVariables" so you don't to use need both commands. The format is different so you do need to revise the Input Table entries to suit the command that you are using.

    @Kennilworth - Hi Brian. Hope you are well.

    Best Redards - Trevor

  8. #8
    Join Date
    Nov 2006
    Location
    At the end of the Line
    Posts
    750
     

    Default

    Update
    It is not a problem on transferring from TANE to TRS2019. The recently added VM rule is now doubled! Also the Show Variables rules are also doubled!

    Quote Originally Posted by trev999 View Post
    Hi David - Could you try using "Delete Missing Assets" anyway? That option seems to get rid of ghost trains and might also work for ghost rules.
    ...
    Best Redards - Trevor
    Thanks Trevor, but that doesn't work.
    Mountains, Sea, Islands and Steam Trains from my living-room window!
    What more could anybody want?

    TRS2019 Build 103369

  9. #9
    Join Date
    Nov 2006
    Location
    At the end of the Line
    Posts
    750
     

    Default

    Confirmed as a bug by N3V, in for fixing in next update.
    Thanks for all your help.
    Mountains, Sea, Islands and Steam Trains from my living-room window!
    What more could anybody want?

    TRS2019 Build 103369

Posting Permissions

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