Elvas Tower: Debrief Evaluation - Elvas Tower

Jump to content

  • 9 Pages +
  • « First
  • 7
  • 8
  • 9
  • You cannot start a new topic
  • You cannot reply to this topic

Debrief Evaluation

#81 User is offline   ATW 

  • Engineer
  • Group: Active Member
  • Posts: 501
  • Joined: 07-January 13
  • Gender:Male
  • Simulator:MSTS Open Rails
  • Country:

Posted 25 March 2018 - 01:23 PM

Edit: Reply to my post #79 I would like to say everything is not retained due to the fact activity had been completed an resuming it from a saved point after it was already complete. Evaluation is retained upon save if the act was not complete which is good if say one had a sim crash, had to go take care of something an did not have time to complete etc. But do know the distance traveled is reset when resuming a un finished act. Another thing to be aware of is fuel burned... Activity developers that lower the percentage of fuel left in the tank will experience that total fuel % deducted in addition to actual fuel burned will total together. So users better have evidence of total fuel start to finish to protect themselves from fuel conservation managers instead of them charging you the additional voyage distance to get to your start point or better yet the briefing better show the total start info :p


This is indeed fun now an challenging but for high density areas an long trains meeting we are going to need Mono Game.

#82 User is offline   mbm_OR 

  • Fireman
  • Group: Active Member
  • Posts: 113
  • Joined: 03-July 15
  • Gender:Male
  • Location:Spain
  • Simulator:Open Rails
  • Country:

Posted 26 March 2018 - 12:46 PM

James Ross said:

There's a very large difference between content files and save/output files

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:

Everything including distance traveled is reset

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:

Broken couplers or even overturned cars where they re couple back to you from behind crash ORTS (Immediate game over crash)

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 User is online   James Ross 

  • Open Rails Developer
  • Group: Elite Member
  • Posts: 4,915
  • Joined: 30-June 10
  • Gender:Not Telling
  • Simulator:Open Rails
  • Country:

Posted 30 March 2018 - 09:21 AM

View Postmbm_OR, on 26 March 2018 - 12:46 PM, said:

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.

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 User is offline   mbm_OR 

  • Fireman
  • Group: Active Member
  • Posts: 113
  • Joined: 03-July 15
  • Gender:Male
  • Location:Spain
  • Simulator:Open Rails
  • Country:

Posted 27 April 2018 - 05:16 AM

James Ross said:

I'd recommend putting the evaluation reports in the same place as saved games for now as we know it'll work.

Done.


View PostATW, on 17 March 2018 - 10:54 PM, said:

Not a bug in evaluation but broken couplers or even overturned cars where they re couple back to you from behind crash ORTS (Immediate game over crash).

Please, try this new code.

The attached file is for testing purposes.(x.4125).
04/06/2018. File deleted because new code.

#85 User is offline   ATW 

  • Engineer
  • Group: Active Member
  • Posts: 501
  • Joined: 07-January 13
  • Gender:Male
  • Simulator:MSTS Open Rails
  • Country:

Posted 11 May 2018 - 10:58 PM

View Postmbm_OR, on 27 April 2018 - 05:16 AM, said:

Done.



Please, try this new code.

The attached files are for testing purpose.(x.4125).
Attachment 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 User is offline   mbm_OR 

  • Fireman
  • Group: Active Member
  • Posts: 113
  • Joined: 03-July 15
  • Gender:Male
  • Location:Spain
  • Simulator:Open Rails
  • Country:

Posted 04 June 2018 - 08:22 AM

View PostATW, on 11 May 2018 - 10:58 PM, said:

I have not experienced the crash from behind bug even on partial run in from behind coupling.

Committed in x.4148.

View PostATW, on 11 May 2018 - 10:58 PM, said:

Thing now for evaluations an limits as mentioned previously is getting coupling speed limits evaluated later on.

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)

Attached File  DebriefEval-2018-14.zip (1.31MB)
Number of downloads: 2

#87 User is online   dforrest 

  • Engineer
  • Group: Active Member
  • Posts: 506
  • Joined: 12-January 12
  • Gender:Male
  • Location:St. Vincent (formally UK)
  • Simulator:MSTS, Open Rails
  • Country:

Posted 04 June 2018 - 08:26 AM

View Postmbm_OR, on 04 June 2018 - 08:22 AM, said:

Committed in x.4148.



4148 is noted as "Broken couplers or overturned cars, crash ORTS".

#88 User is offline   mbm_OR 

  • Fireman
  • Group: Active Member
  • Posts: 113
  • Joined: 03-July 15
  • Gender:Male
  • Location:Spain
  • Simulator:Open Rails
  • Country:

Posted 04 June 2018 - 08:35 AM

View Postdforrest, on 04 June 2018 - 08:26 AM, said:

4148 is noted as "Broken couplers or overturned cars, crash ORTS".

You can read, that the bug report is linked to this topic.

Regards,
Mauricio

#89 User is online   dforrest 

  • Engineer
  • Group: Active Member
  • Posts: 506
  • Joined: 12-January 12
  • Gender:Male
  • Location:St. Vincent (formally UK)
  • Simulator:MSTS, Open Rails
  • Country:

Posted 04 June 2018 - 08:40 AM

So this is not referring to the debrief evaluation?

#90 User is offline   mbm_OR 

  • Fireman
  • Group: Active Member
  • Posts: 113
  • Joined: 03-July 15
  • Gender:Male
  • Location:Spain
  • Simulator:Open Rails
  • Country:

Posted 04 June 2018 - 09:09 AM

View Postdforrest, on 04 June 2018 - 08:40 AM, said:

So this is not referring to the debrief evaluation?

This bug was discovered when testing the broken couplers and overturned cars for the debrief evaluation functionality.
ATW was who first notified this bug here.

  • 9 Pages +
  • « First
  • 7
  • 8
  • 9
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users