[wctrr]

Just a few questions for the Open Rails engine physic’s (eng file) team.

1. The only SteamSpecialEffects functional now is the StackFX and the others are not (CylinderFX, SafetyValvesFX, Exhaust1 and WhistleFX). Is this correct?

Suggestions to think about for future steam locomotives physics implementation:

2. Can you maybe think about adding wood for a choice of fuel?

3. Manual hand brakes for a choice of locomotive brakes?

I think more of the early steam locomotives would be modeled if there were proper engine physics for them.

I would like to take this opportunity to Thank all of you on the Open Rails team(s). ;)

[longiron]

wctrr, on 13 March 2012 - 06:23 PM, said:

Just a few questions for the Open Rails engine physic’s (eng file) team.

1. The only SteamSpecialEffects functional now is the StackFX and the others are not (CylinderFX, SafetyValvesFX, Exhaust1 and WhistleFX). Is this correct?

You are correct for v0.7. We have a prototype complete for Cylinder, Safety Valves, Whistle steam/smoke effects and sync'd chuff sound effects

wctrr, on 13 March 2012 - 06:23 PM, said:

Suggestions to think about for future steam locomotives physics implementation:

2. Can you maybe think about adding wood for a choice of fuel?

3. Manual hand brakes for a choice of locomotive brakes?

Yes, for wood as well as oil burners. Engine braking can be hand braked in you wish. The prototype model supports geared locomotives (Shay's/Heiser's) as well a simple and compound articulated monsters up to the limits of your imagination. If we can get enough dev resources on this area, we can get in all working and tested in Open Rails, but I have no ability to give you a timeframe.

[wctrr]

Chris,

Thanks for your quick response. ;) As always, we all look forward to the next OR update to see what great surprises you guys have for us. :p :) As for as timeframe we all understand about that.

[Shay 5]

Does that include climaxes too? I noticed that any climax and the Shay D models never run right in OR.

[longiron]

Shay 5, on 14 March 2012 - 03:48 AM, said:

Does that include climaxes too? I noticed that any climax and the Shay D models never run right in OR.

There's are parameter for gear ratios in steam loco model, so you can realistically have whatever reduction makes sense. This will impact the tractive effort, so these low speed pullers will get realistically modeled.

[Shay 5]

Sweet!!! ;) Now I have to figure out how to edit those certain parts of the ENG file correctly. It's odd because those models work great in msts. In OR, they act like they have no power or tractive power at all.

[Lindsayts]

Shay 5, on 14 March 2012 - 08:43 AM, said:

Sweet!!! ;) Now I have to figure out how to edit those certain parts of the ENG file correctly. It's odd because those models work great in msts. In OR, they act like they have no power or tractive power at all.

Amen, brother (on the sweet)


Hmmmmmmmmm, just in case I have spent a great deal of time getting the 4 truck shay and the heisler currently avaible to pull reasonably realisticly in OR one is welcome to the data, I shall hunt it up, currently running Linux so cannot access OR.

Some details............

Updated AI fired eng files for "shayd10.zip" originally from Train-sim.com (I think)
with Brain Bere-Streeter Wolgan Valley Railway textures applied.

The model is of a Shay Class 150-4 built by Lima Locomotive works for the
Chesapeake and Ohio Railway in May 1910.
Boiler, 200 PSI coal fired, Saturated steam
Engine, 3 cylinder, bore 17 in. stroke 18 in.
Weight in working order around 156 tons.

This is used as the Wolgan Valley Railway no. 4 which was a 90-3.
Engine 3 cylinder, bore 14.5 in. stroke 15 in. pressure 200 pSI saturated steam.
Weight in working order 93.6 tons.

The eng files are set up for a superheated locomotive although the original was
saturated steam which in fact the model portrays.

Much effort has been put into setting up the eng files to try as much as posssible
to show the performance of a real superheated Shay Class 150-4.


Note, I have not used the steamers much in the last few versions of OR as the seems to be somekind of serious problem that causes quite wide varations in performance (I have not been able to figure it out yet, changing any known eng values appears to make no difference) and as the code is clearly is still very much a work in progress I have not bothered to much.

Lindsay

[thegrindre]

Lindsayts, on 14 March 2012 - 03:39 PM, said:

... Note, I have not used the steamers much in the last few versions of OR as the seems to be somekind of serious problem that causes quite wide varations in performance (I have not been able to figure it out yet, changing any known eng values appears to make no difference) and as the code is clearly is still very much a work in progress I have not bothered to much.

Lindsay

Also the reason I haven't run my two cylinder Shay or any other steamer in OR or OR, for that matter.
Steam physics must be the hardest to work on.
I'm looking forward to the completion of this aspect in OR.

Keep up the great work, guys...

;)

[longiron]

Lindsayts, on 14 March 2012 - 03:39 PM, said:

Note, I have not used the steamers much in the last few versions of OR as the seems to be somekind of serious problem that causes quite wide varations in performance (I have not been able to figure it out yet, changing any known eng values appears to make no difference) and as the code is clearly is still very much a work in progress I have not bothered to much.

Lindsay

Linday,
Please don't make blanket comments about "some kinds of serious problems" that are unsubstantiated. Randomly changing values within the ENG file without understanding their use or even if Open Rails even uses them at all isn't going to address the performance in the game. If you want to understand, please ask I'm sure others would be interested, too. Currently, the MSTS ENG file parameters yeilds generally similar physics performance -- if the ENG parameters are used as they were intended.

[Shay 5]

That's odd Rick. Your shay and the class B shay run Ok, but not the best. We must remember that OR is still a work in progress. It has come a long way. :rotfl: