[Csantucci]

As of now brake initialization commanded by keystroke is not accepted if speed is not equal to 0 or almost.
Brake initialization is a non-prototypical shortcut for players in a hurry or in case of problems, in particular due to the fact that brakes don't release completely because .eng parameters working in MSTS don't work in OR, which uses them more completely. (Moreover it is used internally by OR, but this is not the issue here.)
Driving a train with such .eng parameters under OR is a pain, because to release brakes completely you have to stop the train and then you can enter your initialization command. Needing to stop the train to release brakes is even more non-prototypical.
Therefore I suggest that keystroke-commanded brake initialization be possible also at speed not equal to 0. I'm quite sure this change would be hailed by many OR players.
Here's the simple patch
 Resetbrakes.zip (566bytes)
Number of downloads: 213
I hope that this patch is accepted and that I can commit it.

[eugenR]

I think The Patch would bee helpful but:

Many Engines has :
AirBrakesMainResVolume( 8 )
in the *.eng file because this is the default valour in the description of MSTS
„Eng_and_wag_file_reference_guidev2.doc“

Here you can also read. that this valour is in „cubicfeet“.
1 cubicfeet = 28,3 Liter
8 cubicfeet = 226,4 Liter
a really small Mainreservoir,
If you release the airbrake you doesn't have enough air in this small reservoir
and you have to wait until the compressor has released the Brakes.

enter here
AirBrakesMainResVolume( 50 )
50 cubic feet = 1415 liter a realistic valour for modern Engines
can solve this problem

[Csantucci]

Hi Eugen,
thank you for your exact calculations, that confirmed to me that the 8 value is absolutely insufficient.
I know that changing .eng values (often not only the main reservoir volume) the problem can be solved (by the way I put such value to 32 or 40, and now after your suggestion I will put it to 50). However this requires a high modification work that everyone must do, which is even higher if one wants to create separate .eng files for OR. What I suggest is to increase the usability of the already available Brake Initialization command, to spare or delay the modification work to people not able to do that or not wanting to do that.

[markus_GE]

Csantucci, on 21 May 2014 - 08:41 AM, said:

[...] However this requires a high modification work that everyone must do, which is even higher if one wants to create separate .eng files for OR. [...]

Maybe this is something I´ll try to remember for my current Diesel Engine Updater program, when I expand it... ;)

Cheers, Markus

[cjakeman]

Hi Carlo,

Csantucci, on 21 May 2014 - 05:16 AM, said:

I hope that this patch is accepted and that I can commit it.

Thanks for looking at this.

I wasn't around when this convenience command was first introduced, so I don't know the history. However, as it's a matter of convenience and not prototype operation, and your patch just makes it more convenient then please go ahead.

[ATW]

Has anyone not ever tried the new (not that new) ORTS eng Parameters or experimented atleast with them like I have or even messed with the brake pipe charging rate in the options based on loaded consists where I have mine currently at 115 PSI/s with my avg of 3-4 units? Sofar I'm satisfied with how my long freight trains with tweaked eng files work on releasing and applying like I have in real life except one thing needs fiddling and experimenting being how emergency brake application speeds apply slowly.

One suggesting I wish to see is how rear helpers/dupers play in helping with brake release/applications and how dynamics can be shut down on some units.

[Csantucci]

Thanks Chris,
patch uploaded in release 2248.

[R H Steele]

Csantucci, on 21 May 2014 - 08:41 AM, said:

However this requires a high modification work that everyone must do, which is even higher if one wants to create separate .eng files for OR. What I suggest is to increase the usability of the already available Brake Initialization command, to spare or delay the modification work to people not able to do that or not wanting to do that.

Regarding Modification Work,( sparing or delay of): What is needed to be available are mod instructions detailing how the mod is to be made. Many of the mods discussed are in threads that have to be ferreted out. They are easily understood by the OR Dev team and experienced folks but can be a mystery to many of us. Perhaps, once mods are decided upon a spec sheet could be distilled from the information in a specific thread. A short, but easily understood instruction on how to proceed. If helped with tech issues I would be willing to write such mod instruction sheets. Even better would be the timely release of simple mod programs devoted to a specific file modification.
(see Marcus's post above)

[Csantucci]

I agree about this. Neither I have yet figured out a complete set of rules to be respected for the braking parameters. So it would be nice if the author of the braking code could provide a short manual with following information (in order of importance):
- a suggested coherent and consistent set of the relevant .eng and .wag parameters
- the rules to be followed to select such parameters
- how such parameters influence braking behaviour.

[cjakeman]

R H Steele, on 21 May 2014 - 03:29 PM, said:

If helped with tech issues I would be willing to write such mod instruction sheets.

I'll send you a PM about this.

[ATW]

Well not that anyone cares but those that do and want to experiment their own or share like me, but here are some ORTS brake parameter lines that could and should be placed in .eng files under/between end of eng file Under: Name ( "???" ) and Above: Description (

ORTSAirBrakeMainresvolume ( 10.2 ) <-----Pretty much of what was mentioned early in post#2 but can be used if no one wants to do big changes to what MSTS reads with main reservoir volume.
ORTSMainResChargingRate ( 3.31 ) <-----Experimented that this helps the speed charging of the main res when train's BP system is fully charged as well as helping units equipped teamed up to keep main res strong up like a boost to Main Res volume.
ORTSBrakePipeChargingRate ( 3.0 ) <-----Aware this helps charging the brake pipe (BP) of train or just units faster the higher in connection as if it was a boost for ORTS menu option brake pipe charging rate PSI.
ORTSEngineBrakeReleaseRate ( 38 ) <-----Aware this is the release rate of the independent brake (helpful for RailDriver).
ORTSEngineBrakeApplicationRate ( 34 ) <----- I'm aware this line is the application speed of the loco's independent brake (helpful for RailDriver).
ORTSBrakePipeTimeFactor ( 0.008221323 ) <-----I'm aware the lower this is the faster the BP's release depending of the number of units MU teamed up with this setting the faster. Also in this current number setting I notice how like in real life of some units the BP number in cabs may giggle hard when setting up that till it gets pretty still steady means the BP of the train are equalized completely from front to rear of train. Note. The higher this line in whole numbers the slower the BP may charge.
ORTSBrakeServiceTimeFactor ( 0.19146 ) <-------I'm aware the lead unit with this and a lower number under deep from decimals setting speeds up the consists Train Brake application. Note. The higher this line in whole numbers slows application.
ORTSBrakeEmergencyTimeFactor ( .015 ) <--------I'm still experimenting if this is how fast the emergency application speed acts the lower the under decimals .

Not all of them need to be added but some can help in ways as well as experimented when together with another or all as if they were locomotive brand features or just one or more parts needing service or fixed like a unit with a bad orderd or no Main Res tank, BP, Compressor etc. Now just if there was a RPM power charges main res parameter speed for some units.

Thanks for including these in the manual but does ORTS Development team not want this known or experimented yet to ORTS supporters and users yet?

[markus_GE]

If these are to be made publicly documented and are not wanted to not be used, I´ll think about including an option for having these added to an engine file by my DPU program...

Cheers, Markus

[ATW]

Sofar so good I like the new brake initialization equal to 0 speed being able to be used at any speed in favor for faster emergency applications :)