Elvas Tower: ENG/WAG Values - The Definitive List ? - Elvas Tower

Jump to content

  • 5 Pages +
  • « First
  • 3
  • 4
  • 5
  • You cannot start a new topic
  • You cannot reply to this topic

ENG/WAG Values - The Definitive List ?

#41 User is offline   Lamplighter 

  • Apprentice
  • Group: Status: Dispatcher
  • Posts: 41
  • Joined: 24-January 18
  • Gender:Male
  • Simulator:Open Rails
  • Country:

Posted 12 March 2020 - 10:43 AM

Hi,
I do not understand why the Exhaust1 (Exhaust2) parameters are only listed as MSTS. Open Rails uses the DieselSpecialEffects parameter and cannot do without the above.

#42 User is offline   RR1 

  • Apprentice
  • Group: Status: Dispatcher
  • Posts: 30
  • Joined: 03-March 13
  • Gender:Male
  • Simulator:OR
  • Country:

Posted 12 March 2020 - 12:43 PM

View PostLamplighter, on 12 March 2020 - 10:43 AM, said:

Hi,
I do not understand why the Exhaust1 (Exhaust2) parameters are only listed as MSTS. Open Rails uses the DieselSpecialEffects parameter and cannot do without the above.


You are absolutely right, multiple exhausts can be defined with OR. It's a question of how.

There are no input parameters specifically named "Exhaust1" or "Exhaust2". The TokenID.cs listing includes the specific labels "Exhaust1" or "Exhaust2" which don't exist as specific input parameters in OR. The "OR TokenID.cs Comparison" sheet is looking specifically at the original list of MSTS tokens and determining which of these MSTS tokens still exist in OR.

"exhaust" is a new parameter introduced in OR and is present in the "OR Code Parameters" column on sheet "Parameter Comparison".

OR enables multiple exhaust entries in a much better way using this input called "exhaust". In looking closer at how this parameter is read, the statement is "where blah, blah.StartsWith(''exhaust'')", the operative word being "startswith". So as many instances of exhaust can be defined as required. I'm not sure if what follows "exhaust" even needs to be a number. I'll check this out at some point.

I missed this subtlety. Technically "Exhaust1", etc. is an OR parameter but is not directly read as such so I need to find a way to catch any additional instances like this and make sure there is no confusion. "startswith" is also used in MSTSNotchControllers so it looks like a number of "enginebrakescontroller . . ." and "trainbrakescontroller . . . " tokens which are showing up as MSTS only need to be looked at more closely.

Thanks for raising this issue.

#43 User is offline   Lamplighter 

  • Apprentice
  • Group: Status: Dispatcher
  • Posts: 41
  • Joined: 24-January 18
  • Gender:Male
  • Simulator:Open Rails
  • Country:

Posted 12 March 2020 - 11:56 PM

Hi,
I found other parameters used by ORTS but declared as MSTS Only:
Parameters of light settings - Unit, State, Service, Light, HeadLight, Control.
Parameters defining the block - Wagon and Engine.
Driver parameters - DirControls, CylinderCocks (C key), Vigilance (Y key).

DieselEngineType - ORTS may ignore it, but it's good to know if the .eng file setting is for mechanical or electric drive. ORTS can do both.
The same can be said about the type (Chain) coupler. In Europe we set up screw-tensioned three-link coupling and ORTS accepts it.

Finally, there is one parameter originating from MSTS, more precisely MSTS Bin - PantographsToggle_4. This is useless.

#44 User is offline   Lamplighter 

  • Apprentice
  • Group: Status: Dispatcher
  • Posts: 41
  • Joined: 24-January 18
  • Gender:Male
  • Simulator:Open Rails
  • Country:

Posted 13 March 2020 - 12:21 AM

The advantage is to use valid, invalid, and new color syntax parameters in the NotePad++ editor.
Even recently created .eng will show a lot of ballast.

Attached Image: ukazka.jpg

#45 User is offline   RR1 

  • Apprentice
  • Group: Status: Dispatcher
  • Posts: 30
  • Joined: 03-March 13
  • Gender:Male
  • Simulator:OR
  • Country:

Posted 13 March 2020 - 09:47 AM

View PostLamplighter, on 12 March 2020 - 11:56 PM, said:

Hi,
I found other parameters used by ORTS but declared as MSTS Only:
Parameters of light settings - Unit, State, Service, Light, HeadLight, Control.
Parameters defining the block - Wagon and Engine.
Driver parameters - DirControls, CylinderCocks (C key), Vigilance (Y key).

DieselEngineType - ORTS may ignore it, but it's good to know if the .eng file setting is for mechanical or electric drive. ORTS can do both.
The same can be said about the type (Chain) coupler. In Europe we set up screw-tensioned three-link coupling and ORTS accepts it.

Finally, there is one parameter originating from MSTS, more precisely MSTS Bin - PantographsToggle_4. This is useless.


Thanks. I've found the bug and will issue an update.

#46 User is offline   RR1 

  • Apprentice
  • Group: Status: Dispatcher
  • Posts: 30
  • Joined: 03-March 13
  • Gender:Male
  • Simulator:OR
  • Country:

Posted 14 March 2020 - 12:01 PM

The bug fix reduced the number of "MSTS Only" parameters, however there are "MSTS Only" parameters remaining which refer to parameters not yet included in the analysis, i.e, cab, sound, activity, track etc. internal OR parameters and OR input parameters. These will be included prior to updating the spreadsheet and creating the lists for NotePad++ coloring.

#47 User is offline   RR1 

  • Apprentice
  • Group: Status: Dispatcher
  • Posts: 30
  • Joined: 03-March 13
  • Gender:Male
  • Simulator:OR
  • Country:

Posted 19 May 2020 - 01:56 PM

Finally - Version 2 of the Definitive List. I think it is more definitive this time around.

Changes from last time:

1. ALL OR variables are included now. Not just eng/wag. All parameters, tokens, events for all of the files that OR reads.

2. When I say "all" I'm reasonably sure I've captured 99++% of what the OR codes reads or recognizes. I'm not sure that they are all categorized 100% accurately though. I've had to infer a lot of the categorization because it is not necessarily obvious what is going on the code where they are extracted. People who have a lot of experience with many of the file types in question will probably notice some anomalies. Please let me know if you do.

3. The spreadsheet now just contains lists of the results - no gory details.

4. Sheet "One_List" is just that- everything. But you can filter on a bunch of stuff to help narrow the view down to something more manageable.

5. Sheet "Many _Lists" is a filtered set of lists generated from "One_List" that may be useful. Some lists can be used with text editors to do the highlighting of OR parameters.

6. Sheet "Tokens.cs" is the list of MSTS only parameters based on the Tokens.cs class in the OR code. I think it is now correct.

7. Sheet "OR Manual Index" is an index of the parameters which are mentioned in the Manual. The indexing is by section number. The section numbers are the .html section numbers.

8. Sheet "CoalstoNewcastle" contains the parameters covered on that site. I'm not sure how complete these are . . . A number of OR parameters are covered on the site but not (yet) in the OR Manual.

If anyone sees something wildly out of place, please let me know.

I hope some of you find this useful.


Attached File  OR_ParametersV2.7z (203.34K)
Number of downloads: 43

  • 5 Pages +
  • « First
  • 3
  • 4
  • 5
  • 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