Corsair cockpit gages-has this bug been looked at?
#1

Has this issue been looked at? My initial post on this bug was back in April 2011 when HSFX 5 came out at the 242 Squadron. I haven't seen an acknowledgement of this as a bug at that site. The manifold pressure gauge got changed in the following cockpits with this release:

F4U-1, Corsair I, F4U-1A, Corsair II, F4U-1C, F4U-1D, Corsair IV (Goodyear F4U-1D for FAA)

Now the manifold pressure gauge reads only to 50" instead of 75". You can only attain a maximum of 48" manifold air pressure regardless of rpm setting, throttle setting, supercharger setting. It appears the gauge of the F4F-4 was put into the Corsair cockpits and maybe the parameters of the the Wildcat engine were switched also. As it stands now we can never attain the below settings for any of the Corsairs except Normal Rated Power at 7,000 feet and below and Maximum Cruise settings.

Below is data right out of the "Pilots Manual For the F4U CORSAIR"

The Power Settings for the F4U-1, FG-1, F3A-1 Corsair, P&W R-2800-8:
at Critical Altitude with RAM

Take-Off:
2700 RPM 54" MAP 2000 HP Sea Level Neutral Blower

War Emergency (5 Min):
2700 RPM 57.5" MAP 2250 HP Sea Level Neutral Blower
2700 RPM 59.0" MAP 2135 HP 15,000' Low Blower
2700 RPM 59.5" MAP 1975 HP 20,000' High Blower

Military (5 MIN):
2700 RPM 52.5" MAP 2000 HP 2,500' Neutral Blower
2700 RPM 53.0" MAP 1800 HP 18,500' Low Blower
2700 RPM 53.0" MAP 1650 HP 23,000' High Blower

Normal Rated (Max. Cont.):
2550 RPM 44.0" MAP 1675 HP 7,000' Neutral Blower
2550 RPM 49.5" MAP 1625 HP 19,000' Low Blower
2550 RPM 49.5" MAP 1550 HP 24,000 High Blower

Maximum Cruise:
2150 RPM 34.0" MAP 1070 HP 10,000' Neutral Blower
2150 RPM 34.0" MAP 970 HP 20,500' Low Blower
2150 RPM 34.0" MAP 950 HP 26,000 High Blower

I hope this gets addressed soon. Thanks
Reply
#2

Have you posted this at the 242 Squadron site?
Reply
#3

twice, once back in april and again last night.
Reply
#4

Mailman

It will be repaired.
Reply
#5

Any idea when this might happen?


Any chance there is a way to edit the file to fix it or create a mod (for the MODS folder) specifically to correct this temporarily until an update is released?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)