#4506933 - 02/10/20 05:46 PM
Re: BE.2c Engines
[Re: dawnpatrol]
|
Joined: Sep 2009
Posts: 2,921
vonBaur
Senior Member
|
Senior Member
Joined: Sep 2009
Posts: 2,921
|
If you reduce the mixture to minimum the engine dies. That won't help much, I suppose, if the fire reaches any wood or canvas before that.
SALUTE TO ALL!
|
|
|
#4506950 - 02/10/20 08:54 PM
Re: BE.2c Engines
[Re: dawnpatrol]
|
Joined: Mar 2011
Posts: 938
VonS
WWI Flight Sims on a Mac
|
WWI Flight Sims on a Mac
Member
Joined: Mar 2011
Posts: 938
|
I am on my third Career in a BE2 and i have notced it's dangerous engine. Alittle TOO dangerous i should think. In almost half sorties someone in the flight aborts or burns to death and my first 2 careers ended in engine fires. Comparing this with historical data it feels way too deadly in WOFF. I agree engine fires were there, but not this much. If so, the plae would have been removed from service immediately.
So i wonder, is there any mod that reduces (not removing) engine failure risk or atleast the engine fire risk? Is there anyway to survive a spontaneous engine fire by any means? I cannot kill the engine, just set it to idle. As of now, there is really no point of flying BE2 careers, since the life expency is max 20 sorties not counting enemy AA or planes..
3 careers, 2 kia due to engine fires, 3rd alive but after 5 missions i have made 2 emergency landings with engine failure and systems failure.
Is there a datasheet with percentage values per planes of engine fail risks?
I recommend making a copy of the stock simulation.xml file available in the main WOFF OBD folder - and then tweaking the following section of a "modded" simulation.xml file that you will only use when flying Be.2 careers -----> <Failure weight="1.0" masterdisable="n"> <FailureRule SystemID="engine_one" average_hrs="90" damageAmount_pct="31" dump="y"/> <FailureRule SystemID="engine_one" average_hrs="120" damageAmount_pct="70" dump="y"/> <FailureRule SystemID="engine_one" average_hrs="160" damageAmount_pct="5" frequency_secs="111" dump="y"/> <FailureRule SystemID="engine_one" average_hrs="200" damageAmount_pct="9" frequency_secs="35" dump="y"/> Possibly increase average hrs. between random failures, and also reduce the damage pts., something like -----> <Failure weight="1.0" masterdisable="n"> <FailureRule SystemID="engine_one" average_hrs="150" damageAmount_pct="21" dump="y"/> <FailureRule SystemID="engine_one" average_hrs="190" damageAmount_pct="55" dump="y"/> <FailureRule SystemID="engine_one" average_hrs="220" damageAmount_pct="3" frequency_secs="80" dump="y"/> <FailureRule SystemID="engine_one" average_hrs="270" damageAmount_pct="6" frequency_secs="25" dump="y"/> Hope that helps and let us know the results if possible. Von S
~ For my various FM/AI/FPS/DM Mods. for First Eagles 2, WoFF, RoF & WoTR, and tips for FlightGear, recommended is to check over my CombatAce profile ( https://combatace.com/profile/86760-vons/) and to click on the "About Me" tab while there. ~
|
|
|
#4507037 - 02/11/20 11:33 AM
Re: BE.2c Engines
[Re: VonS]
|
Joined: Nov 2017
Posts: 35
dawnpatrol
Junior Member
|
Junior Member
Joined: Nov 2017
Posts: 35
|
Exellent! Thank you very much! I will report back any results!
EDIT:
A quick summary after some tests. Using above suggested settings, i am now suffering even worse from engine malfunctions. Of 5 missions, i have force landed 4 times. AI flight members have force landed 2 times. So in 5 missions with 2 machines in every flight, it is in total 6 engine breakdowns, on the other hand, there has been no fires as of yet.
I wonder what value did increase the risks though.
It should be noted that all testing has been under AI control (exept final approaches on forced landings)
Last edited by dawnpatrol; 02/11/20 03:39 PM.
|
|
|
#4507072 - 02/11/20 03:56 PM
Re: BE.2c Engines
[Re: dawnpatrol]
|
Joined: Jul 2014
Posts: 2,105
Raine
Member
|
Member
Joined: Jul 2014
Posts: 2,105
New Brunswick, Canada
|
Dawnpatrol, I suspect you might have suffered mainly from bad luck. Engine fires in the BE2 are certainly a possibility, but I haven't encountered them with the frequency you report. WOFF does model unreliability reasonably well. For example, if you fly the SE5 with the 150 hp Hispano Suiza engine, you are going to suffer fairly frequent breakdowns and the possibility of an engine fire. I found, however, that the frequency of problem dropped considerably if you avoid cruising at full throttle, reserving full power for combat situations. This same applies to the Spad 7.
I'm tempted to suggest flying the BE2 the same way, although 80% power in a Quirk is pretty much dead stop.
|
|
|
#4507094 - 02/11/20 06:20 PM
Re: BE.2c Engines
[Re: dawnpatrol]
|
Joined: Mar 2011
Posts: 938
VonS
WWI Flight Sims on a Mac
|
WWI Flight Sims on a Mac
Member
Joined: Mar 2011
Posts: 938
|
Exellent! Thank you very much! I will report back any results!
EDIT:
A quick summary after some tests. Using above suggested settings, i am now suffering even worse from engine malfunctions. Of 5 missions, i have force landed 4 times. AI flight members have force landed 2 times. So in 5 missions with 2 machines in every flight, it is in total 6 engine breakdowns, on the other hand, there has been no fires as of yet.
I wonder what value did increase the risks though.
It should be noted that all testing has been under AI control (exept final approaches on forced landings) Thank you for the feedback - I recommend one more semi-controlled test therefore, so that we can see how manipulation of the numbers, in the simulation.xml file, operates exactly in WOFFue/pe. For example, since we are getting more engine damage but less fire, on average, with the larger values in the previous modification, I suggest, when you find time, to try out these smaller values -----> <Failure weight="1.0" masterdisable="n"> <FailureRule SystemID="engine_one" average_hrs="50" damageAmount_pct="21" dump="y"/> <FailureRule SystemID="engine_one" average_hrs="80" damageAmount_pct="55" dump="y"/> <FailureRule SystemID="engine_one" average_hrs="120" damageAmount_pct="3" frequency_secs="170" dump="y"/> <FailureRule SystemID="engine_one" average_hrs="160" damageAmount_pct="6" frequency_secs="65" dump="y"/> In the above example, I've left the "damage amount pct" numbers smaller as in the previous modification, since this seems to refer to damage amount points and/or percentages, but I've increased the "frequency secs." numbers since this may refer to frequency between problems showing up, rather than frequency of duration of problem. The only thing that seems illogical is that I've reduced the no. of hrs. for the "average hrs." settings - since initially I had assumed that it referred to hrs. between damage showing up - although, there is the off chance that it refers to ave. hrs. out of commission, after engine damage. Feel free to report back with results of this second experiment, if you like, and it might help us to narrow down what is controlling general damage vs. engine fires. (Although we should also keep in mind that manipulation of these numbers still hinges on the law of averages/probabilities already hard-coded, most likely, into WOFF - so there will always, to some extent, be cases of "bad luck" and "good luck" when flying the Be.2, as other posts have indicated here.) Von S
Last edited by VonS; 02/11/20 06:23 PM. Reason: Added info. - hope we are able to narrow down the results/tweaks.
~ For my various FM/AI/FPS/DM Mods. for First Eagles 2, WoFF, RoF & WoTR, and tips for FlightGear, recommended is to check over my CombatAce profile ( https://combatace.com/profile/86760-vons/) and to click on the "About Me" tab while there. ~
|
|
|
#4507139 - 02/11/20 10:54 PM
Re: BE.2c Engines
[Re: dawnpatrol]
|
Joined: May 2016
Posts: 1,523
BuckeyeBob
Member
|
Member
Joined: May 2016
Posts: 1,523
Ohio, USA
|
Let me throw my own two cents in, if I may, although i haven't fiddled with these numbers since WOFF 3 or 4. Some things may have changed or been added since then. For example, I'm not sure what "Failure weight" refers to. My guess is that it modifies the base random system damage chances for all aircraft, so maybe changing that value might have an impact on the number of failures. Try reducing this value to .25 or increasing it to a large number such as 50 to see if it has an effect.
My comments about the other values:
average_hrs: I think VonS is correct that this number refers to the number, on average, that the given system will experience a failure. My suspicion is that at the beginning of a campaign, each aircraft is assigned a random number of hours it has been "in service," based on aircraft type and date of the campaign. Therefore, "older" aircraft are more likely to break down than "newer" ones.
damageAmount_pct=x: The percent of damage the system suffers.
frequency_secs=x: This value modifies the damageAmount_pct, if present. For example, the following line: <FailureRule SystemID="engine_one" average_hrs="160" damageAmount_pct="6" frequency_secs="65" dump="y"/> means that when engine one experiences a random failure, it will immediately lose 6% of its function. Every 65 seconds, the engine will lose another 6% of its function. When it reaches 100% it will cease function all together, if it hasn't caught fire already.
dump I'm not sure, but I think if this is set to "y", it means the system is set to break entirely, or in the case of an engine, catch fire, etc.
Hope this helps. I could be totally wrong, so take all of the above with a grain of salt!
“With Major Lawrence, mercy is a passion. With me it is merely good manners. You may judge which motive is the more reliable.”
|
|
|
#4507161 - 02/12/20 09:30 AM
Re: BE.2c Engines
[Re: dawnpatrol]
|
Joined: Mar 2003
Posts: 8,149
Polovski
|
Hotshot
Joined: Mar 2003
Posts: 8,149
|
Basically with those weightings there is a random element too as they are "average". However for some people you will see many failures, some never see any and complain those settings are not enough and others see a few - unfortunately it's how random can work out I can't remember the last time I saw a BE2c engine failure. As with all changes like that you have to run many dozens of repeating tests with each and every one of those lines one by one, as it's random. You could for example see 10 engine failures in 10 flights then see none for a year
Last edited by Polovski; 02/12/20 09:34 AM.
|
|
|
|
|
|
|
|
|
|
|
|
|
Exodus
by RedOneAlpha. 04/18/24 05:46 PM
|
|
|