Debrief Evaluation
#81
Posted 25 March 2018 - 01:23 PM
This is indeed fun now an challenging but for high density areas an long trains meeting we are going to need Mono Game.
#82
Posted 26 March 2018 - 12:46 PM
James Ross said:
Thank you for your comments, which make clear and justify not using the Openrails folder, to save the evaluation reports.
The current folder to save files is well thought out for those binary files that should not be manipulated by users.
Therefore, it would be convenient to consider a different option for evaluation reports. As the OR screenshots are stored in the ../images/Openrails folder, we could use ../Documents/Openrails folder to save the evaluation reports.
ATW said:
Now it is properly retained.
Once in the Resume window, after selecting a saved activity that has the Eval checkbox checked, we could restore the following evaluation values:
- Alerter applications above 10MPH/16KMH.
- Autopilot (Time).
- Coupler breaks.
- Curve speeds exceeded.
- Departure before passenger boarding completed.
- Distance travelled.
- Emergency applications while moving.
- Emergency applications while stopped.
- Full Train Brake applications under 5MPH/8KMH
- Hose breaks.
- Over Speed.
- Over Speed (Time).
- Train Overturned.
ATW said:
I've had several times the same crash. It needs to be fixed.
The attached files are for testing purpose.(x.4098).
27/04/2018: File deleted because new code.
#83
Posted 30 March 2018 - 09:21 AM
mbm_OR, on 26 March 2018 - 12:46 PM, said:
I've made a suggestion of new location for each type of file, which includes this idea of evaluations being inside "Documents". Feel free to add your thoughts over there, as we've not reached agreement yet. :)
I'd recommend putting the evaluation reports in the same place as saved games for now as we know it'll work. Once we agree on a better arrangement (in the other thread), everything can be moved or shortcuts created, etc..
#84
Posted 27 April 2018 - 05:16 AM
James Ross said:
Done.
ATW, on 17 March 2018 - 10:54 PM, said:
Please, try this new code.
The attached file is for testing purposes.(x.4125).
04/06/2018. File deleted because new code.
#85
Posted 11 May 2018 - 10:58 PM
mbm_OR, on 27 April 2018 - 05:16 AM, said:
Please, try this new code.
The attached files are for testing purpose.(x.4125).
DebriefEval-2018-13.zip
Looks good so far. Thanks for that bug fix as I have not experienced the crash from behind bug even on partial run in from behind coupling. Thing now for evaluations an limits as mentioned previously is getting coupling speed limits evaluated later on.
#86
Posted 04 June 2018 - 08:22 AM
ATW, on 11 May 2018 - 10:58 PM, said:
Committed in x.4148.
ATW, on 11 May 2018 - 10:58 PM, said:
Now "Work orders" section has a new item: Coupling speed limits. The coupling speed limit is set to 1.5 Mps (5,4 Kph ~ 3,35 Mph).
When the activity has ended, a new external window is opened, showing the evaluation report.
The attached file is for testing purposes.(x.4151)
02/07/2018: File deleted because feature committed
#87
Posted 04 June 2018 - 08:26 AM
#88
Posted 04 June 2018 - 08:35 AM