Activity randomizing
#41
Posted 08 November 2017 - 11:55 PM
#42
Posted 09 November 2017 - 08:57 AM
May I ask if there is a plan for random failures to be optional for certain equipped wag/eng files by having parameters that point to probable percentage chance causes over the ones that are less more likely to happen vs ones getting the failure? I want to set a piece of stock that is more likely to get a failure that I am expecting if in consists based on chances for experimental or realistic randomness I set with these parameters an testing each one.
A good example of this engine failure % chance would be traction blowouts where I set my DC motors to have a 50% or more chance to blowout its traction motors over my AC units having a 10% or less to no chances to blowing a traction or bogie. An if I set the % chance to a number representing 100%; that failure is always going to happen on each game load after the random time kicks in.
#43
Posted 09 November 2017 - 05:05 PM
#44
Posted 09 November 2017 - 06:59 PM
#45
Posted 10 November 2017 - 12:31 PM
#46
Posted 11 November 2017 - 04:40 PM
#47
Posted 11 November 2017 - 11:50 PM
To ATW: I'd prefer not to add parameters in files only to support the activity randomizing feature.
#48
Posted 12 November 2017 - 04:01 PM
Csantucci, on 11 November 2017 - 11:50 PM, said:
That’s fine but I’m not really saying to make it available as a parameter only thing getting rid of activity randomizing. But you can say I’m asking for a parameter to equip stock that is more likely to break down based on a percentage chance an those parameters to be used in explore mode when testing or simulating real conditions. Otherwise we can’t simulate careful operating practices for some units an their competitors like GE vs EMD that new tier 4 EMDs are making a number of random failures.
#49
Posted 13 November 2017 - 08:07 PM
"Norfolk Southern milepost <NearestMilePost>, <noDefect> total axles <totalAxels> "
"Norfolk Southern Detector Alarm "Hotbox Alarm, Left Side, Axle Number <RandomAxel>"
For axle count, temperature ect this could be plugged in through keywords in the config file. Its all text based and adds a bit more randomization.
So, some useful tags would be:
<AxelCount> total axles on the train
<NearestMilePost> Displays nearest milepost you are near.
<DefectDetected> This will display a random defect based upon the parameters of possible defects available to this particular detector.
<NoDefect> Displays generic "no defect" message.
<Tempreture> If and when possible display current temperature. Some railroads use this, some dont.
<Track> Displays what track youre on track 1, track 2, track 3, track 4 ect.
Sorry to hijack your thread and go a bit off topic, but it seems related to this sort of random problem and delay you are working on and hopefully show defect detectors dont have to be complicated and hard coded tons of messages and that the user can do most of the work himself as long as he has access to basic information contained in tags. Thanks, sorry again.
#50
Posted 14 November 2017 - 07:51 PM