Steinbauer Posted May 20, 2019 Posted May 20, 2019 (edited) Hello, Is the airspeed correct on the Christen Eagle? I was practicing crosswind landings, and it seemed like the crosswind had more effect than it should. I changed the scenario to a simple headwind of 25 kts, and again it seems too strong. Even sitting still on the runway shows the 25 kt headwind as 60 mph on the airspeed guage. It seems off by about a factor of two. I'm attaching a misison file along with a track file and a pic of the airspeed indicator while sitting still. Also, if I turn the plane 180 deg so the wind is a tail wind, it still registers about 60 mph on the guage.CE2Persian25KtHeadwindA.trkCE2Persian25KtHeadwindA.miz Edited May 20, 2019 by Steinbauer
razo+r Posted May 20, 2019 Posted May 20, 2019 Are you sure it's 25 kts and not m/s wind speed in the ME?
Steinbauer Posted May 20, 2019 Author Posted May 20, 2019 Here is a pic from the mission editor... they list it as kts.
Ramsay Posted May 20, 2019 Posted May 20, 2019 Here is a pic from the mission editor... they list it as kts. I don't own the CE2 but substituting the TF-51D for the CE2 in your mission, the ground wind fails to register on the TF-51D's speedometer and the cockpit info bar (LCtrl+Y) shows IAS as 20 knots. Perhaps a bug/problem to report on the "Magnitude 3 LLC » Christen Eagle II » Bugs and Problems" forum. i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Ramsay Posted May 20, 2019 Posted May 20, 2019 Ok, Thanks. I will post on that thread! 25 m/s = 55 mph, Perhaps the CE2's flight and system model assumes the mission/user uses metric units. Try setting "Options/Gameplay>Units=Metric" (25 knot = 13m/s) and retest (might be a work around and give Magnitude a pointer where to change their code). i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Steinbauer Posted May 20, 2019 Author Posted May 20, 2019 Could be... I think I'll just use half the value for now, until they fix it. You're probably right in that they're interperating the external wind from the mission editor as m/sec.
Ramsay Posted May 20, 2019 Posted May 20, 2019 Could be... I think I'll just use half the value for now, until they fix it. Note: The max. demonstrated crosswind in the Pitts S-2B POH is 17 knots (20 mph), so reducing the crosswind may also be more realistic for the Eagle II. i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Ironhand Posted May 22, 2019 Posted May 22, 2019 FWIW, there's more to the problem than the speed. The wind direction also doesn't matter. Both a tail wind and crosswind will give the same reading as a headwind on the airspeed indicator. YouTube Channel: https://www.youtube.com/channel/UCU1...CR6IZ7crfdZxDg _____ Win 11 Pro x64, Asrock Z790 Steel Legend MoBo, Intel i7-13700K, MSI RKT 4070 Super 12GB, Corsair Dominator DDR5 RAM 32GB.
Recommended Posts