Boris Posted May 15, 2014 Posted May 15, 2014 What I think people want is to be able to set a 'maximum' value for wind speed. The altitudes you can set wind speeds for should be the altitudes where wind speeds peak. For exanple if you got rid of the 10m setting and made it 200m instead, people would know that the wind speed between 0-200m will be not be higher than what they set in the editor. That sounds like a good solution. A drop in wind from 200-0m sounds completely plausible, but it would be better if it scaled the wind speed of the bottom layer down, rather than to scale up the wind speed of the bottom layer based on the windspeed at sea level (does that make sense?). As it is now, mission designers need to halve the windspeed of the bottom layer, to match the windspeed of the second layer, if they want a consitent wind. In any case, the wind in the bottom layer will always be roughly twice that set in the mission editor, except for a few hundred meters above sea level. I fear many mission designers don't know that they should halve the wind speed of the bottom wind layer to achieve the desired effect. PC Specs / Hardware: MSI z370 Gaming Plus Mainboard, Intel 8700k @ 5GHz, MSI Sea Hawk 2080 Ti @ 2100MHz, 32GB 3200 MHz DDR4 RAM Displays: Philips BDM4065UC 60Hz 4K UHD Screen, Pimax 8KX Controllers / Peripherals: VPC MongoosT-50, Thrustmaster Warthog HOTAS, modded MS FFB2/CH Combatstick, MFG Crosswind Pedals, Gametrix JetSeat OS: Windows 10 Home Creator's Update
howie87 Posted May 15, 2014 Posted May 15, 2014 Exactly. Any wind speed entered in the mission editor should be the maximum speed for the particular altitude range. Wind speed either side should decrease unless you set the adjacent altitude range to a higher wind speed.
Recommended Posts