Activity randomizing
#51
Posted 14 November 2017 - 11:26 PM
#52
Posted 15 November 2017 - 08:29 AM
1. I start Open Rails
2. I click on options, followed by clicking on Experimental
3. I set Activity & Weather Randomization to 3, then I close out of Options
4. I choose a activity, then I start the activity
5. At a certain point, I save the activity
6. After a while, I choose replay, and I repeat steps 4 & 5
------------------------------------------------------------------------
I noticed that Activity & Weather Randomization doesn't work after the first save.
#53
Posted 15 November 2017 - 12:45 PM
1. Start activity
2. Save after a while
3. Exit activity
4. Resume saved activity; randomized weather is the one saved, and weather continues evolving
5. Save after a while
6. Exit activity
7. Resume from this second save: randomized weather is the one saved, and weather continues evolving.
So I'm not able to reproduce problems with save/resume.
There is instead a - non solvable - problem with replays (not resumes): it's very complicated to replay the same way the activity was saved, because every randomized value should be saved: recalling the same randomizing method would - by definition - lead to other numbers in the replay. So every randomized activity run is unique and not repeatable.
#54
Posted 16 November 2017 - 10:25 AM
Csantucci, on 15 November 2017 - 12:45 PM, said:
Intriguing problem, and it might be solvable. I found several solutions offered here including:
- an extension to count how many times Random.Next() is run and then pre-running it after a Replay
- serializing Random and keeping that as part of the save to deserialize from later
- implementing your own random number generator
I think option 2 would be easiest.
#55
Posted 14 December 2017 - 10:31 AM
after several evenings spent by running randomized activies, I'm experiencing what I was afraid of (see post #34 here): with almost every activity run, it comes to a loco failure - even if I set Activity randomization to 1.
Let me propose: could it be possible to set train failures randomization separately from other events? This way we would have three groups of randomized events: /a/ rolling stock failures, /b/ efficiency and times, /c/ weather, with possibility to set randomization level separately.
Anyway - this is a great feature, and - at least for me - it works fine. (Only if I had bigger chance for my train to survive my 5-hours' jurney without loco failures...)
Thanks for considering this.
Wish you all best,
Mirek
#56
Posted 14 December 2017 - 11:13 AM
#57
Posted 14 December 2017 - 11:45 AM
When done, I promise I'll test it :-)
Mirek
#58
Posted 14 December 2017 - 01:16 PM
to help you with setting the probability of rolling stock failure, I googled for some railway statistics. Not much straightforward figures. Which may be of some help is this:
"Trains hit a high of 120,591 miles between breakdowns in October 2012. That number slid to 103,813 miles in October 2013 and further to 87,750 in October 2014, according to NJ Transit."
"By comparison, the Long Island Rail Road won an award for its fleet traveling nearly 200,000 miles between failures. The New York City subway system's oldest trains went 55,540 miles between failures and the newest subway cars traveled 381,131 between breakdowns in July 2015, according to MTA statistics."
(source: http://www.nj.com/tr...stats_show.html)
Regards,
Mirek
#59
Posted 17 December 2017 - 01:50 PM
attached you have a file to replace into x.4009, that should lead to more realistic loco breakdown rates.
18/12/17: file deleted because updated release available
#60
Posted 18 December 2017 - 09:05 AM
20/12/17: File deleted because patch committed