Here is the new .wag file -- just 25 lines:
SIMISA@@@@@@@@@@JINX0D0t______ Wagon ( xm_atsf_142331_mt Include ( XM_ATSF_142331_Mesh_Dimensions.inc ) Include ( ..\\fleet_stds\\Std_Type_Coupler_Generic_Draft_Gear.inc ) Adheasion ( 0.2 0.4 2 0 ) DerailRailHeight ( 5cm ) Mass ( 21.45t ) DerailRailForce ( 48.6486t ) DerailBufferForce ( 373.7216kn ) MaxBrakeForce( 7.095kN ) MaxHandbrakeForce( 8.6kN ) Friction ( 820N/m/s -0.260 5.690mph 5.10N/m/s 1.59 5.1N/rad/s 1 -1rad/s 0 1 ) Include ( ..\\fleet_stds\\Single_Pipe_AB_Brakes.inc ) Sound ( "genfreightwag1.sms" ) Name ("XM 40' ATSF 142331 MT") )
Reading the file, the first Include() is about the physical features of the model:
Comment ( XM_ATSF_142331_Mesh_Dimensions.inc ) Type ( Freight ) WagonShape ( SF142331.s ) Size ( 3.1m 4.6m 13.2m ) InertiaTensor ( Box (3.1m 4.6m 12.9m) ) NumWheels ( 8 ) WheelRadius ( 33in/2 )
That include file is stored with the .s file; That location makes sense to me because if I make several versions of this car (mty vs. loaded) this data would apply to each one.
The second Include() is about the couplers:
comment ( "Type E coupler w/ generic draft gear" ) comment ( "For cars equipped with uncushioned slack pro-couplers ie: Hopper cars, gondolas, tankcars" ) comment ( "older flatcars and boxcars." ) Coupling ( Type ( Automatic ) Spring ( Stiffness ( 0 5e6N/m ) Damping ( 2e6N/m/s 2e6N/m/s ) Break ( 5.1e7N 5.1e7N ) r0 ( 5cm 8cm ) ) Velocity ( 0.2m/s ) ) Coupling ( Type ( Automatic ) Spring ( Stiffness ( 0 5e6N/m ) Damping ( 2e6N/m/s 2e6N/m/s ) Break ( 5.1e7N 5.1e7N ) r0 ( 5cm 8cm ) ) Velocity ( -0.2m/s ) ) Buffers ( Spring ( Stiffness ( 5e6N/m 8e6N/m ) Damping ( 1e6N/m/s 1e6N/m/s ) r0 ( 0m 1e9 ) ) Centre ( 0.5 ) Radius ( 1 ) Angle ( 0.5deg ) )
Because that data is constant for all of my late steam era freight cars I've placed it in a special folder I've called "Fleet_STDS". Using the relative path construct of "..\\fleet_stds\\" tells the OR software to go up one level in the directory tree and find a folder called "Fleet_STDS". This include file is there. Sticking into "Fleet_STDS" means all other .wag files can point there too, meaning I'll have just one set of coupler data for the whole fleet.
Next two lines are orphans right now... as I'm not sure where Adhesion() and DeRailHeight() could go if there were moved into an include file.
Mass() is something that could vary across different versions of this car... mty vs loaded for instance and so IMO it makes sense to keep it in the .wag.
The next 8 lines have values all determined by the value of Mass() and so they're here too. IMO none of those lines should be in any part of a .wag... I'm of the opinion that all of them should be computed by the OR software when the .wag is being read.
The final Include() is for the brake line and brake equipment:
Comment ( "Single_Pipe_AB_Brakes.inc" ) BrakeEquipmentType ( "Handbrake, Triple_valve, Auxilary_reservoir, Emergency_brake_reservoir" ) BrakeSystemType ( "Air_single_pipe" ) NumberOfHandbrakeLeverSteps( 100 ) TripleValveRatio( 2.5 ) MaxReleaseRate( 1.86 ) MaxApplicationRate( 0.9 ) MaxAuxilaryChargingRate( 1.684 ) EmergencyResCapacity( 2.604 ) EmergencyResChargingRate( 1.684 ) EmergencyBrakeResMaxPressure( 90 ) BrakeCylinderPressureForMaxBrakeBrakeForce( 50 )
Like the coupler file this too is placed into my "Fleet_STDS" folder as the values are all constants for the late steam era.
If this car had lights -- a FRED, or an interior (e.g., a caboose) I'd move the data into Include files so they could be shared over several versions.
The file finishes by identifying a sound file and naming the .wag. IF the OR software ever allows us to put new descriptive data into the .wags (e.g., Car Initial, Car Number, etc. etc.) then I'd probably move all of that, plus the name line, into an Include() file so it could be shared across other versions of this car. In that case it would properly go into the car folder itself.