[ATSF3751]

Hey everyone,

So I have been thinking lately of upgrading some exsisting MSTS steam locomotives to Open Rails specs. This would include updated physics, lighting, sounds and smoke effects.

Myself being a steam guy I am fairly picky on how I want my steam locomotives to perform and sound. That being said we have some outstanding models out there that look fantastic but lack in the physics and sound departments.

My thought is to update some older models to Open Rails specs and release the Eng and sound files to the public if it is at all phesable to do so.

I do not want to be stepping on anyone's toes and feel it would be a bennifit to the community if it was done and bring some new life to some older models.

Another proposal I would like to bring up is the chuffing sounds.

I feel it is time that Open Rails moves away from the old way of syncing the sounds to the driver's by speed but instead have it linked by the rotation of the drivers/pistons.

A few of us have brought this idea up to Peter in a group convo but none of us are sure how to go about this and I wanted to get an outsiders prospective on this idea as well.

Brandon

[timmuir]

Quote

My thought is to update some older models to Open Rails specs and release the Eng and sound files to the public if it is at all phesable to do so.

Well, I tell ya, Brandon, you are more than welcome to improve any of my locomotives in this way. :sign_rockon:

[ATSF3751]

Thank you Tim. I have always admired your work!! Here are some of the locomotives I would like to upgrade to current Open Rails specs. There are more I would like to do but here are just a few I have thought of to start with.

Narrow Gauge locomotives

Eureka #4



RGS #20



RGS #346



DRGW K28



DRGW K36



Standard Gauge Locomotives

SP GS2 and GS6



FRISCO 1522



NP 2-8-2s



CB&Q 4-6-4s

[Traindude]

One thing that I think would be a benefit for any ORTS "Upgrades" to existing locomotives would be, in the case of entire fleets of locomotives that have multiple road numbers or other variations, is that the common parameters and values could be placed in *.inc files. This not only saves tons of disk space by not repeating identical parameters and values in each individual *.eng and *.wag file, but it also makes editing an entire fleet easier.

Here is how I typically set up *.inc files for a typical steam engine:



It should be self-explanatory, but I will go through the contents of each *.inc file in case it isn't:
For the loco:
GeneralData_Wag.inc generally contains the rolling stock type, size, idler wheel diameter, number of idler axles, derail coefficient parameters, the external *.sms file to be used.
Coupler.inc contains the coupler physics.
Brake_Wag.inc contains all the parameters for the WAGON section of the *.eng file, such as triple valve/distributor properties and brake forces.
Lights.inc contains all the lighting specifications.
Resistance.inc contains the Davis coefficients, wind resistance, curve resistance and trailing locomotive resistance.
SpecialFX.inc contains all the data for the smoke & steam emissions.
GeneralData_Eng.inc generally contains the locomotive type, number of driving wheels, driving wheel diameter and sanding information.
Boiler.inc contains boiler data, such as evaporative surface, superheat, and so forth.
Cylinders.inc contains cylinder diameter, stroke, and efficiency, as well as crankpin angle and multiple-engine definitions (if the locomotive has a booster, for example)
Firebox.inc contains the grate area, fuel calorific value and maximum fuel feed rate.
Brake_Eng.inc contains all the brake parameters for the ENGINE section of the *.eng file, pertaining to the compressors, main reservoir, and brake control rates.
CabControls.inc contains all the Engine Controller parameters, and the specific *.cvf and internal *.sms file to be used for the cab view.
Desciption.inc contains the locomotive description details.
Procedures.inc contains all the operating procedures that show up in the Help (F1) menu.

Things such as loco shape files, loco names, and the like, are not included in the *.inc files and remain in their respective individual *.eng or *.wag files.

For the tender:
GeneralData.inc contains all the same data as the GeneralData_Wag.inc file for the loco--type, size, derail coefficients, external *.sms file, etc.
Coupler.inc contains all the coupler physics.
Brake.inc is analogous to the Brake_Wag.inc file used on the loco.
Resistance.inc contains the Davis coefficient, wind resistance and curve resistance for the tender in its LOADED state.
Lights.inc contains the light data (if the tender has lights).
CoalLoad.inc is used for the depleting tender coal load FreightAnim, as well as the physics changes associated with the depletion and replinishment of the coal and water supply, and any intake points.
SpecialFX.inc is only needed if the tender has steam heat or other particle-based effects (water scoop, etc.). However, this file is usually also accompanied by a SteamHeat.inc or WaterScoop.inc file.

I hope this structure makes sense to everyone. After I discovered the use of *.inc files (with a little assistance from ErickC and NAVS) they've been a real life-saver.

[Laci1959]

Quote

A few of us have brought this idea up to Peter in a group convo but none of us are sure how to go about this and I wanted to get an outsiders prospective on this idea as well.

Hello.

This was solved by Icik years ago in the CZ-SK Openrails version. Maybe you should ask him for help.

Sincerely, Laci1959

[ATSF3751]

Traindude, on 30 March 2024 - 12:22 AM, said:

One thing that I think would be a benefit for any ORTS "Upgrades" to existing locomotives would be, in the case of entire fleets of locomotives that have multiple road numbers or other variations, is that the common parameters and values could be placed in *.inc files. This not only saves tons of disk space by not repeating identical parameters and values in each individual *.eng and *.wag file, but it also makes editing an entire fleet easier.

Here is how I typically set up *.inc files for a typical steam engine:
incstructure.jpg


It should be self-explanatory, but I will go through the contents of each *.inc file in case it isn't:
For the loco:
GeneralData_Wag.inc generally contains the rolling stock type, size, idler wheel diameter, number of idler axles, derail coefficient parameters, the external *.sms file to be used.
Coupler.inc contains the coupler physics.
Brake_Wag.inc contains all the parameters for the WAGON section of the *.eng file, such as triple valve/distributor properties and brake forces.
Lights.inc contains all the lighting specifications.
Resistance.inc contains the Davis coefficients, wind resistance, curve resistance and trailing locomotive resistance.
SpecialFX.inc contains all the data for the smoke & steam emissions.
GeneralData_Eng.inc generally contains the locomotive type, number of driving wheels, driving wheel diameter and sanding information.
Boiler.inc contains boiler data, such as evaporative surface, superheat, and so forth.
Cylinders.inc contains cylinder diameter, stroke, and efficiency, as well as crankpin angle and multiple-engine definitions (if the locomotive has a booster, for example)
Firebox.inc contains the grate area, fuel calorific value and maximum fuel feed rate.
Brake_Eng.inc contains all the brake parameters for the ENGINE section of the *.eng file, pertaining to the compressors, main reservoir, and brake control rates.
CabControls.inc contains all the Engine Controller parameters, and the specific *.cvf and internal *.sms file to be used for the cab view.
Desciption.inc contains the locomotive description details.
Procedures.inc contains all the operating procedures that show up in the Help (F1) menu.

Things such as loco shape files, loco names, and the like, are not included in the *.inc files and remain in their respective individual *.eng or *.wag files.

For the tender:
GeneralData.inc contains all the same data as the GeneralData_Wag.inc file for the loco--type, size, derail coefficients, external *.sms file, etc.
Coupler.inc contains all the coupler physics.
Brake.inc is analogous to the Brake_Wag.inc file used on the loco.
Resistance.inc contains the Davis coefficient, wind resistance and curve resistance for the tender in its LOADED state.
Lights.inc contains the light data (if the tender has lights).
CoalLoad.inc is used for the depleting tender coal load FreightAnim, as well as the physics changes associated with the depletion and replinishment of the coal and water supply, and any intake points.
SpecialFX.inc is only needed if the tender has steam heat or other particle-based effects (water scoop, etc.). However, this file is usually also accompanied by a SteamHeat.inc or WaterScoop.inc file.

I hope this structure makes sense to everyone. After I discovered the use of *.inc files (with a little assistance from ErickC and NAVS) they've been a real life-saver.

I did this with my MILW S3 class 4-8-4 locomotives and it worked out great!

Brandon

Attached thumbnail(s)

• 

[ATSF3751]

Laci1959, on 30 March 2024 - 01:25 AM, said:

Hello.

This was solved by Icik years ago in the CZ-SK Openrails version. Maybe you should ask him for help.

Sincerely, Laci1959

I had no idea this was even possible or even done yet!

Brandon

[Laci1959]

Variable_Trigger ( WheelSpeed_Inc_Past 0.1 StartLoopRelease   ( 1 File ( "TM_18.wav" -1 )   SelectionMethod ( SequentialSelection ) ) )
                                        Variable_Trigger ( WheelSpeed_Inc_Past 6.0 ReleaseLoopRelease () )
					Variable_Trigger ( WheelSpeed_Dec_Past 6.0 StartLoopRelease   ( 1 File ( "TM_18.wav" -1 )   SelectionMethod ( SequentialSelection ) ) )
					Variable_Trigger ( WheelSpeed_Dec_Past 0.1 ReleaseLoopRelease () )

And

VolumeCurve(
					WheelSpeedControlled
					CurvePoints ( 5
                                        0.00		0.00
                                        2.50		0.00
                                        3.16		1.00
                                        5.62		1.00
                                        6.20		0.00      
					)
					Granularity ( 0.05 )
				)

[ATSF3751]

Thanks for sharing this!

[Traindude]

Laci1959, on 30 March 2024 - 08:46 AM, said:

Variable_Trigger ( WheelSpeed_Inc_Past 0.1 StartLoopRelease   ( 1 File ( "TM_18.wav" -1 )   SelectionMethod ( SequentialSelection ) ) )
                                        Variable_Trigger ( WheelSpeed_Inc_Past 6.0 ReleaseLoopRelease () )
					Variable_Trigger ( WheelSpeed_Dec_Past 6.0 StartLoopRelease   ( 1 File ( "TM_18.wav" -1 )   SelectionMethod ( SequentialSelection ) ) )
					Variable_Trigger ( WheelSpeed_Dec_Past 0.1 ReleaseLoopRelease () )

And

VolumeCurve(
					WheelSpeedControlled
					CurvePoints ( 5
                                        0.00		0.00
                                        2.50		0.00
                                        3.16		1.00
                                        5.62		1.00
                                        6.20		0.00      
					)
					Granularity ( 0.05 )
				)

For the record, what are the units to be used for the "WheelSpeed" variable? RPM? Or something else?