Blackburn Beverley Uploaded
- Thread starter mjahn
- Start date
Bill, normally, on loading a plane all its variables are set to zero. That doesn't seem to be the case on your setup. Perhaps you have an app that saves and resets variables on loading the sim or a plane, possibly the C47 GCA-MVC you mention (and could check on this issue).
A simple solution, hopefully, is to explicitly zero the two major GCA variables in the Beverley's intialization run. Initialization happens in Sim_Bev.xml. I am attaching a revised version - simply copy it to panel\Bev, overwriting the original. Then let's see what you get. To make sure the initialization takes control, reload the Beverley a second time. If that doesn't help we can read out the current state of those variables. I'd really like to get this sorted. It is interesting to see that something like this is even possible.
--Manfred
Hi Manfred,
When you mentioned an app that saves variables, you reminded me that I generally start FSX using the utility SimStarter NG which I have been using for years. I am not sure whether you are familiar with this utility but it enables me to start FSX using my choice of simulator configuration (essentially FSX.cfg) and scenery configuration (scenery.cfg) and I have created and saved a number of these configurations depending on my planned flight scenario and potential VAS footprint. To be honest however, I do not know whether this utility saves or resets any other variables on loading the sim or a plane as the only elements I ever set it up to configure were the scenery and simulator.cfgs, the latter mainly involving varying the various graphics, display and realism parameters that are usually controlled by the sliders. Still I thought I should make you aware I am using this in case it has any bearing on the issue.
With regard to the revised sim_bev.xml file which you kindly provided, I installed this following your instructions and I then started FSX without using SimStarterNG (just in case it might be contributing to the issue) but the same repetitive call out was still occurring when I loaded the Beverley the first time. Out of interest, I shut down and restarted FSX again (without using Simstarter) and reloaded the Beverley and again encountered the same issue but this time the callout had changed to "turn right"!
Bill
Bill,
Not sure about the configured loading of FSX, shouldn't do any harm, I suppose, and you did try without it. So the search continues... I am now attaching a replacement file for the Monitor gauge that lists the two most suspect variables - APC and PAR - in the Test area as in the pic below. Both values are at zero, as they should be, I have even selected Shannon as my AILA destination, and naturally I can hear no calls. Please copy the attached Mon.xml to panel\Mon, temporarily replacing the original Mon.xml. Your PAR value may say 1, i.e. ON, that would be the culprit. I have added a clickspot to the first line of the Monitor Test window (the FS serial number), if you click that both APC and PAR should be reset to zero. Any insights one way or another with that?
Not sure about the configured loading of FSX, shouldn't do any harm, I suppose, and you did try without it. So the search continues... I am now attaching a replacement file for the Monitor gauge that lists the two most suspect variables - APC and PAR - in the Test area as in the pic below. Both values are at zero, as they should be, I have even selected Shannon as my AILA destination, and naturally I can hear no calls. Please copy the attached Mon.xml to panel\Mon, temporarily replacing the original Mon.xml. Your PAR value may say 1, i.e. ON, that would be the culprit. I have added a clickspot to the first line of the Monitor Test window (the FS serial number), if you click that both APC and PAR should be reset to zero. Any insights one way or another with that?
Thanks Manfred,
Just an update. I replaced the original mon.xml file as you suggested but I am afraid the issue unfortunately persists although the repetitive call out this time was different - "on centreline, on glidepath". Incidentally both APC and PAR had a reading of zero as soon as I opened the monitor and, as might be expected with these readings, clicking the clickspot on the FS serial number didn't make any difference.
Bill
Just an update. I replaced the original mon.xml file as you suggested but I am afraid the issue unfortunately persists although the repetitive call out this time was different - "on centreline, on glidepath". Incidentally both APC and PAR had a reading of zero as soon as I opened the monitor and, as might be expected with these readings, clicking the clickspot on the FS serial number didn't make any difference.
Bill
BendyFlyer
Charter Member
Manfed. The Boost Guage works without any issues that I could discover. The MP on the tool tip is actually a nice touch. The guage indicated pressure accurately before start (atmospheric) then engine running. All 4 operated correctly in correct sense. I checked the MP and boost and RPM at all relevant power settings - idle, take off, intial climb, cruise climb and cruise (8000 ft) Checked at sea level location with ISA pressure set. For the values I can find for the Centaurus engine the boost/mp readings are accurate at various power settings and for a supercharged piston engine. There were no issues with the VC gauge display or graphics. Checked on FSXA running on Win7 64 bit OS. I wrote down all the relevant MP/RPM?Boost settings but no point in reproducing that data here, it is correct and obvious when the sim is running.
I think it is preferable to the MP guage with the release and finalises the authenticity of the cockpit.
Excellent work.
For interest is a screenshot of the guages and VC on climb:
I think it is preferable to the MP guage with the release and finalises the authenticity of the cockpit.
Excellent work.
For interest is a screenshot of the guages and VC on climb:
HighBypass
Members +
Hello All,
Just joined SOH and getting to grips with the Beverley. Thank you Mr. Jahn for a fine freeware product! A couple of questions if i may: Where's the flap lever in the cockpit please? I've found the parking brake!
Also, I've downloaded the boost gauges. How do I install them into FSX:SE please?
My wife's older sister is called Beverley (good job they are not twins!!). I'm sure I mentioned to Beverley years ago that there is a plane with the same name. I shall take some delight in reminding her - unless my missus has already told her about me already flying the fat biffa around..
Just joined SOH and getting to grips with the Beverley. Thank you Mr. Jahn for a fine freeware product! A couple of questions if i may: Where's the flap lever in the cockpit please? I've found the parking brake!
Also, I've downloaded the boost gauges. How do I install them into FSX:SE please?My wife's older sister is called Beverley (good job they are not twins!!). I'm sure I mentioned to Beverley years ago that there is a plane with the same name. I shall take some delight in reminding her - unless my missus has already told her about me already flying the fat biffa around..
Thanks Bendyflyer, that situation does look spot on.
I think if there is going to be an update I'll include the boost gauges as a panel.cfg option so that the user can decide which one to use. The boost numbers can easily be added to the checklist.
When I started out on this project I was briefly in touch with Kevin Kelleher, who made significant modifications to the original FS 2002 Beverley model by R. Pegram, R. Hazeldine, and B. Horsey. His father was a Beverley pilot, and Kelleher's Notes on Flying the Beverley describe some of the Bev's "pleasant and endearing" handling characteristics:
I think if there is going to be an update I'll include the boost gauges as a panel.cfg option so that the user can decide which one to use. The boost numbers can easily be added to the checklist.
When I started out on this project I was briefly in touch with Kevin Kelleher, who made significant modifications to the original FS 2002 Beverley model by R. Pegram, R. Hazeldine, and B. Horsey. His father was a Beverley pilot, and Kelleher's Notes on Flying the Beverley describe some of the Bev's "pleasant and endearing" handling characteristics:
Hello All,
Just joined SOH and getting to grips with the Beverley. Thank you Mr. Jahn for a fine freeware product! A couple of questions if i may: Where's the flap lever in the cockpit please? I've found the parking brake!
My wife's older sister is called Beverley (good job they are not twins!!). I'm sure I mentioned to Beverley years ago that there is a plane with the same name. I shall take some delight in reminding her - unless my missus has already told her about me already flying the fat biffa around..
Pleasure, and I really LOL'ed on this!
No flap lever I am afraid, didn't know where to put it. However, the flaps gauge has clickspots for moving them up and down.
The boost stuff, just copy the 5 files to folder panel\Bev, then in the panel.cfg, replace all instances of "Bev!ManPress1649AFE" by "Bev!BoostPress".
BendyFlyer
Charter Member
Manfred Glad to help.
For those who want to make the change here is the VC01 from the panel.cfg. Just copy all this and replace the current section (backing up the older one first of course!) as MJ says just drops the contents of the zip into the Bev folder in the panel folder>
[Vcockpit01]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$VC_01
gauge00=Bev!Sim_Bev, 0,0,1,1
gauge01=Bev!OBSVC, 188,480,150,150
gauge02=Bev!AttitudeVC, 355,346,150,150
gauge03=Bev!TurnIndicatorVC, 143,181,150,150
//gauge04=Bev!ILS_cagedVC, 172,324,150,150
gauge05=Bev!TrimVC, 291,188,150,150
gauge06=Bev!LightFire, 214,649,26,26
gauge07=Bev!AirTempVC, 518,350,137,137
gauge08=Bev!Call_SignVC, 33,350,89,25
gauge09=Bev!BoostPress_1, 197,20,150,150
gauge10=Bev!BoostPress_2, 360,20,150,150
gauge11=Bev!Tachometer1649AFE_1, 524,20,150,150
gauge12=Bev!Tachometer1649AFE_2, 687,20,150,150
gauge13=Bev!BoostPress_3, 197,696,150,150
gauge14=Bev!BoostPress_4, 360, 696 ,150,150
gauge15=Bev!Tachometer1649AFE_3, 524,696,150,150
gauge16=Bev!Tachometer1649AFE_4, 687,696,150,150
gauge17=Bev!Gyro049VC, 5,180,150,150
gauge18=Bev!VerticalSpeed121GFE, 460,185,150,150
gauge19=Bev!ClockFE, 850,20,150,150
gauge20=Bev!AltimeterFE, 818,183,164,167
gauge21=Bev!flaps, 662,196,126,126
gauge22=Bev!RadioAltimeterVC, 338,485,183,183
gauge23=Bev!CarbAirTemp121G_12, 540,505,166,166
gauge24=Bev!CarbAirTemp121G_34, 715,505,166,166
gauge25=Bev!vor_1, 392,889,107,107
gauge26=Bev!asi, 18,7,166,166
gauge28=dsd_battery_charger!charger, 0,0,1,1
gauge29=Bev!LightsOMI, 30,654,55,167
gauge30=Bev!FuelQuantityLeft, 15,849,170,170
gauge31=Bev!FuelQuantityRight, 190,849,170,170
gauge32=Bev!VOR2, 669,332,171,171
gauge33=Bev!hsi, 816,817,204,204
gauge34=Bev!RMI, 17,480,150,150
gauge35=Bev!ILS_notset, 578,839,184,184
gauge36=Bev!APC_PAR, 33,391,32,18
gauge37=dsd_fsx_fuel_dump!fuel_dump, 2,2,2,2
For those who want to make the change here is the VC01 from the panel.cfg. Just copy all this and replace the current section (backing up the older one first of course!) as MJ says just drops the contents of the zip into the Bev folder in the panel folder>
[Vcockpit01]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$VC_01
gauge00=Bev!Sim_Bev, 0,0,1,1
gauge01=Bev!OBSVC, 188,480,150,150
gauge02=Bev!AttitudeVC, 355,346,150,150
gauge03=Bev!TurnIndicatorVC, 143,181,150,150
//gauge04=Bev!ILS_cagedVC, 172,324,150,150
gauge05=Bev!TrimVC, 291,188,150,150
gauge06=Bev!LightFire, 214,649,26,26
gauge07=Bev!AirTempVC, 518,350,137,137
gauge08=Bev!Call_SignVC, 33,350,89,25
gauge09=Bev!BoostPress_1, 197,20,150,150
gauge10=Bev!BoostPress_2, 360,20,150,150
gauge11=Bev!Tachometer1649AFE_1, 524,20,150,150
gauge12=Bev!Tachometer1649AFE_2, 687,20,150,150
gauge13=Bev!BoostPress_3, 197,696,150,150
gauge14=Bev!BoostPress_4, 360, 696 ,150,150
gauge15=Bev!Tachometer1649AFE_3, 524,696,150,150
gauge16=Bev!Tachometer1649AFE_4, 687,696,150,150
gauge17=Bev!Gyro049VC, 5,180,150,150
gauge18=Bev!VerticalSpeed121GFE, 460,185,150,150
gauge19=Bev!ClockFE, 850,20,150,150
gauge20=Bev!AltimeterFE, 818,183,164,167
gauge21=Bev!flaps, 662,196,126,126
gauge22=Bev!RadioAltimeterVC, 338,485,183,183
gauge23=Bev!CarbAirTemp121G_12, 540,505,166,166
gauge24=Bev!CarbAirTemp121G_34, 715,505,166,166
gauge25=Bev!vor_1, 392,889,107,107
gauge26=Bev!asi, 18,7,166,166
gauge28=dsd_battery_charger!charger, 0,0,1,1
gauge29=Bev!LightsOMI, 30,654,55,167
gauge30=Bev!FuelQuantityLeft, 15,849,170,170
gauge31=Bev!FuelQuantityRight, 190,849,170,170
gauge32=Bev!VOR2, 669,332,171,171
gauge33=Bev!hsi, 816,817,204,204
gauge34=Bev!RMI, 17,480,150,150
gauge35=Bev!ILS_notset, 578,839,184,184
gauge36=Bev!APC_PAR, 33,391,32,18
gauge37=dsd_fsx_fuel_dump!fuel_dump, 2,2,2,2
Bill,
Reviewing your reports I now think it's likely the errant sounds may be due to some sort of duplicate setup. The suspect item in particular would be the file "GCA_dsd_fsx_xml_sound.gau". You do have that in the Beverley's panel folder and a separate panel\GCA folder, don't you? (Just asking because some simmers habitually copy all such stuff to the main gauges folder.) Two additional tests along these lines come to mind:
(1) Rename "GCA_dsd_fsx_xml_sound.gau" in the Beverley's panel folder to "BEV_dsd_fsx_xml_sound.gau" and edit the corresponding gauge02 of [Window03] in panel.cfg.
(2) (Errant calls still present) Run a file search in FSX to find duplicate instances of "GCA_dsd_fsx_xml_sound.gau". Temporarily disable (rename) them and test.
HighBypass
Members +
Thank you, gents! 
HighBypass
Members +
OOPS, another thing. Is there a way of tying all 4 condition levers together to adjust the propeller pitch a la Flight1 Islander for example (toggle separate and tied) so that it's less of a struggle using the mouse to adjust them? Less realistic I know, but I cannot use a virtual hand or pair of hands to move all 4 levers at once. I realise that there are presets on the monitor for takeoff and cruise...
OOPS, another thing. Is there a way of tying all 4 condition levers together to adjust the propeller pitch a la Flight1 Islander for example (toggle separate and tied) so that it's less of a struggle using the mouse to adjust them? Less realistic I know, but I cannot use a virtual hand or pair of hands to move all 4 levers at once. I realise that there are presets on the monitor for takeoff and cruise...
Use the middle mouse button to click once on the controls and they will all adopt the identical movement (same for throttle and mixture); click again to revert to individual movement.
nagpaw
SOH-CM-2022
Manfred, et. al.,
I installed the new boost gauges. I wish I could report success like BendyFlyer, but alas, something is amiss. I probably did something wrong. I dropped the new gauges and bmps into my Blackburn Beverley/panel/Bev folder, then edited the panel.cfg by commenting out the MP gauges and substituting the new gauge like this...
gauge09=Bev!BoostPress_1, 197,20,150,150
I did the same thing for the other three engines. The gauges show up correctly and all appears well. But I think the gauge is reading wrong. I performed the following tests...
1) On the ground with all engines shut down, I cleared all weather and made certain the local altimeter was set to 29.92. As expected, the boost gauge reads 0 and the monitor display MP reading says 29.9. Cool.
2) Started the engines and advanced the throttles to takeoff power, +14 boost on the boost gauge. The throttle required was 69% and the resulting MP was 44". That seems really low.
3) I began advancing the power from idle and noting the resulting boost/MP relationship and found the following...
41% throttle gives +0 Boost and 30.0" Hg
49% throttle gives +4 Boost and 34.0" Hg
57% throttle gives +8 Boost and 38.0" Hg
So for some reason on my system the boost pressure gauges are acting like the MP gauges, where 0 equals approximately 30" and 1 Boost unit is equal to 1" Hg, which jives with +14 boost being 44" (30 + 14 = 44). But the boost gauge (I believe) should be reading psi above standard, where 0 equals 14.69 psi and 1 boost unit is equal to 1 psi. So the numbers should have looked something like this...
41% throttle gives +0 Boost (14.69 psi) and 30.0" Hg
49% throttle gives +4 Boost (18.69 psi) and 38.1" Hg
57% throttle gives +8 Boost (22.69 psi) and 46.2" Hg
69% throttle gives +14 Boost (28.69 psi) and 58.4" Hg
So something is wrong, and may go back to my installation. Could something be hanging around from the original MP gauges? I'm going to try reinstalling the whole package fresh and see if that solves it. I'll report back later!
Thanks again for working on this! I never thought much of the Beverley until your model showed up. What a fascinating airplane and story! This is why I love flight simming
I installed the new boost gauges. I wish I could report success like BendyFlyer, but alas, something is amiss. I probably did something wrong. I dropped the new gauges and bmps into my Blackburn Beverley/panel/Bev folder, then edited the panel.cfg by commenting out the MP gauges and substituting the new gauge like this...
gauge09=Bev!BoostPress_1, 197,20,150,150
I did the same thing for the other three engines. The gauges show up correctly and all appears well. But I think the gauge is reading wrong. I performed the following tests...
1) On the ground with all engines shut down, I cleared all weather and made certain the local altimeter was set to 29.92. As expected, the boost gauge reads 0 and the monitor display MP reading says 29.9. Cool.
2) Started the engines and advanced the throttles to takeoff power, +14 boost on the boost gauge. The throttle required was 69% and the resulting MP was 44". That seems really low.
3) I began advancing the power from idle and noting the resulting boost/MP relationship and found the following...
41% throttle gives +0 Boost and 30.0" Hg
49% throttle gives +4 Boost and 34.0" Hg
57% throttle gives +8 Boost and 38.0" Hg
So for some reason on my system the boost pressure gauges are acting like the MP gauges, where 0 equals approximately 30" and 1 Boost unit is equal to 1" Hg, which jives with +14 boost being 44" (30 + 14 = 44). But the boost gauge (I believe) should be reading psi above standard, where 0 equals 14.69 psi and 1 boost unit is equal to 1 psi. So the numbers should have looked something like this...
41% throttle gives +0 Boost (14.69 psi) and 30.0" Hg
49% throttle gives +4 Boost (18.69 psi) and 38.1" Hg
57% throttle gives +8 Boost (22.69 psi) and 46.2" Hg
69% throttle gives +14 Boost (28.69 psi) and 58.4" Hg
So something is wrong, and may go back to my installation. Could something be hanging around from the original MP gauges? I'm going to try reinstalling the whole package fresh and see if that solves it. I'll report back later!
Thanks again for working on this! I never thought much of the Beverley until your model showed up. What a fascinating airplane and story! This is why I love flight simming
Hello again Manfred,
Yes the files are where they should be (I don't copy them into the main gauges folder).
(1) I did as you suggested and the Beverley worked fine the first time I loaded it but then I shut down and restarted FSX and on loading the Beverley the second time unfortunately the issue recurred.
(2) Checked both FSX and the rest of my computer (as sometimes I find things can lurk in odd places that you don't even know about) and no duplicates of that file present.
I also thought I would try your GCA equipped C-47 release which also includes an AILA setup to see if that was showing any similar issues but that loaded perfectly on two separate occasions.
Clearly this has to be something to do with my set up as I seem to be alone in experiencing these persistent callouts, which makes me wonder if SimStarterNG is playing some role although the fact that the Beverley issue persisted when I started FSX without using that utility suggests that it is not involved. Searching through my setup the only other thing I wondered about was a program called vLSO (Virtual Landing Signal Officer) which comes with the SimWork Studios Midway Battle Group and contains audible instructions for approaching a carrier. However the voice in vLSO is completely different and there is no doubt that the voice I am hearing is the male voice from the GCA_... wav files in the panel\GCA\calls folder. However just in case it might be connected in some way I also deactivated vLSO and started FSX and that made no difference.
So, although it remains a mystery, I am very happy to be able to say that it is not affecting my enjoyment of this excellent aircraft!
Bill
BendyFlyer
Charter Member
MJ (and Nagpaw).
Here are the various readings I got from the Boost Guages:
The values are consistent and as expected. Performance - Speeds were also consistent and correlated. All at MTOW at Sea Level with ISA values set for the sim. Note sure why you would be getting lower values as you have reported. I guess the question I would ask is what was the elevation of the airport you were using and what was the outside air temperature? ISA at sea level would be +15C. The values I obtained also confirmed the red band on the boost gauge being the area of engine operation where you get low RPM with higher than atmospheric pressure which is a NO NO for supercharged or turbocharged engines but varies with the engine type or design, I noted the comments from Manfred earlier that there was a vibration-propellor harmonic issue for the Centaurus egnine which had sleeve valves so that would be a factor as well. The Boost gauge is only going to take the values from the aircraft config and air data files and would not read the values from another gauge such as the MP gauge in the folder.
Note I did not consider throttle position as I regard that irrelevant - because PWR=Torque (MP) X RPM. In real engines and it seems it is modelled correctly in FSX the throttle merely regulates fuel flow via the main jets in a carburettor or injectors to the inlet manifold the throttle or power levers merely control that part of the engine nothing else, more fuel more power, if they get out of whack it can be a pain but it is merely a mechanical linkage (simulated in the sim)
Sometimes with FSX for some reason it takes values from the previous setup or flight especially if you have used a different aircraft type, this is particularly acute when you say swap types using the aircraft select menu or make changes to say a panel config file or textures (such a checking a repaint) and it will simply not read these changes but keep giving you the old, it is an FSX bug and the only solution is to shut it down and restart it afresh. It is the reason on my setup my default flight is a Cold N Dark with all systems OFF that is intially loaded. I can then relocate the aircraft using the menu to where I want it, set the weather (REX) and then go about doing starting from that criteria.
Cannot comment on the GCA-ILS gauge issues have not tried it.
Here are the various readings I got from the Boost Guages:
| BOOST | RPM | MP | PHASE |
| 0 | 0 | 29 | BEFORE START - SHUTDOWN |
| -6 | 1050 | 13 | AFTER START - IDLE |
| 0 | 1800 | 30 | PWR-PRESS CHECK 1 |
| 6 | 2000 | 36.8 | PWR PRESS CHECK 2 |
| 8 | 2200 | 38.2 | PWR PRESS CHECK 3 |
| 12 | 2300 | 42.1 | PWR PRESS CHECK 3 |
| 16 | 2500 | 45.7 | PWR PRESS CHECK 4 |
| 25 | 2700 | 59.7 | TAKE OFF POWER |
| 20 | 2600 | 50.0 | CLIMB 1ST SEGMENT -1ST PWR REDUCTION |
| 16 | 2600 | 45.5 | CLIMB 2ND SEGMENT - 2ND PWR REDUCTION |
The values are consistent and as expected. Performance - Speeds were also consistent and correlated. All at MTOW at Sea Level with ISA values set for the sim. Note sure why you would be getting lower values as you have reported. I guess the question I would ask is what was the elevation of the airport you were using and what was the outside air temperature? ISA at sea level would be +15C. The values I obtained also confirmed the red band on the boost gauge being the area of engine operation where you get low RPM with higher than atmospheric pressure which is a NO NO for supercharged or turbocharged engines but varies with the engine type or design, I noted the comments from Manfred earlier that there was a vibration-propellor harmonic issue for the Centaurus egnine which had sleeve valves so that would be a factor as well. The Boost gauge is only going to take the values from the aircraft config and air data files and would not read the values from another gauge such as the MP gauge in the folder.
Note I did not consider throttle position as I regard that irrelevant - because PWR=Torque (MP) X RPM. In real engines and it seems it is modelled correctly in FSX the throttle merely regulates fuel flow via the main jets in a carburettor or injectors to the inlet manifold the throttle or power levers merely control that part of the engine nothing else, more fuel more power, if they get out of whack it can be a pain but it is merely a mechanical linkage (simulated in the sim)
Sometimes with FSX for some reason it takes values from the previous setup or flight especially if you have used a different aircraft type, this is particularly acute when you say swap types using the aircraft select menu or make changes to say a panel config file or textures (such a checking a repaint) and it will simply not read these changes but keep giving you the old, it is an FSX bug and the only solution is to shut it down and restart it afresh. It is the reason on my setup my default flight is a Cold N Dark with all systems OFF that is intially loaded. I can then relocate the aircraft using the menu to where I want it, set the weather (REX) and then go about doing starting from that criteria.
Cannot comment on the GCA-ILS gauge issues have not tried it.
nagpaw
SOH-CM-2022
BendyFlyer and Manfred,
Thanks for the detailed information! Yes, I do start FSX fresh as well with a similar flight setup as you. I mentioned throttle position merely because of the discrepancy between throttle position between the original MP gauges and the new boost gauges. Anyway, I rechecked everything thinking it was a local problem, but the data you posted shows that the gauge is not reading correctly.
The boost gauge should show pounds per square inch (psi) above or below standard. With the engine shutdown on a standard pressure day (about 14.7 psi or 30 inches of mercury), the boost gauge should read zero, which it does. A boost indication of +4 indicates 4 psi above standard, or 18.7 psi (14.7 + 4), which equates to about 38.3 inches of mercury as read on the manifold pressure gauge. Takeoff power on the Centaurus 173 as fitted to the Beverley is listed as +14 boost. That would be 28.7 psi (14.7 + 14), which equates to about 58.4 inches of mercury.
The problem is that as currently programmed the boost gauges are showing inches of mercury above or below standard. Looking at both of our charted numbers, the MP readings are just standard pressure (about 30 inches) plus the boost. (I never noticed the option of making a table. Bravo!
) So using the published takeoff power of +14 boost would give you only 44 inches. My cruise airspeed was low because I was setting the published cruise power setting of +4 boost, which resulted in only 34 inches manifold pressure.
I'm not sure why Blackburn installed boost gauges that read up to +25. That setting would be 39.7 psi...or a bone-crushing 80.8 inches of mercury. Must be something I don't know about operating big piston engines! (Well, I'm sure there's lots of things. I haven't flown any piston engine since the late 90s!)
It looks like just a units issue, and hopefully a simple adjustment. I know absolutely nothing about gauge programming, so I can't provide any other information. BTW, thanks to everyone for talking about this and working on it!
Thanks for the detailed information! Yes, I do start FSX fresh as well with a similar flight setup as you. I mentioned throttle position merely because of the discrepancy between throttle position between the original MP gauges and the new boost gauges. Anyway, I rechecked everything thinking it was a local problem, but the data you posted shows that the gauge is not reading correctly.
The boost gauge should show pounds per square inch (psi) above or below standard. With the engine shutdown on a standard pressure day (about 14.7 psi or 30 inches of mercury), the boost gauge should read zero, which it does. A boost indication of +4 indicates 4 psi above standard, or 18.7 psi (14.7 + 4), which equates to about 38.3 inches of mercury as read on the manifold pressure gauge. Takeoff power on the Centaurus 173 as fitted to the Beverley is listed as +14 boost. That would be 28.7 psi (14.7 + 14), which equates to about 58.4 inches of mercury.
The problem is that as currently programmed the boost gauges are showing inches of mercury above or below standard. Looking at both of our charted numbers, the MP readings are just standard pressure (about 30 inches) plus the boost. (I never noticed the option of making a table. Bravo!
) So using the published takeoff power of +14 boost would give you only 44 inches. My cruise airspeed was low because I was setting the published cruise power setting of +4 boost, which resulted in only 34 inches manifold pressure.I'm not sure why Blackburn installed boost gauges that read up to +25. That setting would be 39.7 psi...or a bone-crushing 80.8 inches of mercury. Must be something I don't know about operating big piston engines! (Well, I'm sure there's lots of things. I haven't flown any piston engine since the late 90s!)
It looks like just a units issue, and hopefully a simple adjustment. I know absolutely nothing about gauge programming, so I can't provide any other information. BTW, thanks to everyone for talking about this and working on it!
Attachments
BendyFlyer
Charter Member
Nagpaw - I had the Beverley Manual and guess what the only section missing turns out to be the Part2 with the engine limitations performance etc. You are correct in terms of what the guage should be reading if it was calibrated to PSI, I think MJ has the air files data set for MP using inches of mercury not PSI (The British Measurement), the boost gauge is conveiniant fix to give a boost guage in the cockpit. To redo it would require him to re do the air file tables and parameters and then gauge to work off that. Basically a complete rebuild on some levels. Due to the way FSX works this stuff out there are whole set of other problems that would arise and the issue of superchargers in FSX has been a significant problem for a long time because of the way the ESP engine calculates values etc etc.
I guess I read off the values being shown and they equate to what one would expect, but as you correctly indicate they do not equate to the Beverley or Centaurus 173 engine because of the PSI v Hg issue I alluded to above.
As for why would Blackburn use a guage showing such high values? Well that was common in the British aircraft at the time they would simply borrow a guage from another type that would do the job and was available and then give you the correct values to stick with in the manual, the fact that it shows 25 Boost never meant it would get there. The fact that they put in a Torque gauge strongly suggests this was the case.I can live with what Manfred has put together even if it is slightly out of whack with the manual.
I guess I read off the values being shown and they equate to what one would expect, but as you correctly indicate they do not equate to the Beverley or Centaurus 173 engine because of the PSI v Hg issue I alluded to above.
As for why would Blackburn use a guage showing such high values? Well that was common in the British aircraft at the time they would simply borrow a guage from another type that would do the job and was available and then give you the correct values to stick with in the manual, the fact that it shows 25 Boost never meant it would get there. The fact that they put in a Torque gauge strongly suggests this was the case.I can live with what Manfred has put together even if it is slightly out of whack with the manual.
nagpaw
SOH-CM-2022
BendyFlyer,
That makes total sense about the gauge and +25 boost! I guess that would really help standardization, wouldn't it? The same gauge in every airplane. A mechanic's (and accountant's) dream!
I agree with you. The gauges works fine the way they are, and I don't want to give Manfred any more work...unless he wants to make a version without the Rebecca aerials and supply aimer's position...
...I kid...I kid!
That makes total sense about the gauge and +25 boost! I guess that would really help standardization, wouldn't it? The same gauge in every airplane. A mechanic's (and accountant's) dream!
I agree with you. The gauges works fine the way they are, and I don't want to give Manfred any more work...unless he wants to make a version without the Rebecca aerials and supply aimer's position...
...I kid...I kid!
