Abrupt weather changes
-
Hi all,
Recently I have encountered very sudden changes in atmospheric conditions while in the 3D world when loading a new weather map (generated through F4WX). I can understand that because the weather maps represent discrete changes in conditions, there is bound to be some transition, but I feel that in 4.34 it has become much more noticeable. The jet will suddenly jerk to one side due to wind changes, and the barometric altimeter will go haywire for a few seconds as well.
Has anyone else encountered this, or does someone have a solution or tips? I can imagine increasing the weather map update frequency would mediate the effect, but I’m already at 10 minutes per map.
Thanks in advance,
Nicolas
-
Hi all,
Recently I have encountered very sudden changes in atmospheric conditions while in the 3D world when loading a new weather map (generated through F4WX). I can understand that because the weather maps represent discrete changes in conditions, there is bound to be some transition, but I feel that in 4.34 it has become much more noticeable. The jet will suddenly jerk to one side due to wind changes, and the barometric altimeter will go haywire for a few seconds as well.
Has anyone else encountered this, or does someone have a solution or tips? I can imagine increasing the weather map update frequency would mediate the effect, but I’m already at 10 minutes per map.
Thanks in advance,
Nicolas
10mn per map is totally crazy and useless
Map loading should be 1H minimum
I will make sure the code rejects <1H map loading as it can ruin interpolating conditions
-
Thanks for the reply Mav.
Can you explain the interpolation? I remember that in earlier versions there was a map speed and direction, but since those settings are gone now I thought that there would be no dynamic weather changes aside from the updating of the weather map.
Nicolas
-
Interpolation means the weather map transition from one file to another during a “long time”, smoothly.
-
Thanks, but I was actually referring to the specifics of the interpolation. Does BMS already load the next weather map for interpolation purposes when auto-update is enabled?
-
Thanks, but I was actually referring to the specifics of the interpolation. Does BMS already load the next weather map for interpolation purposes when auto-update is enabled?
I was about to write that given your description of the abrupt change and the very nature of interpolation, the current version could precisely not be using interpolation, but I suppose my input may not be particularly appreciated, so I’ll refrain =).
-
I think it’s always been like this when a new map loads, it’s just very noticeable now in 4.34 because of the more detailed winds aloft. So you encounter an instantaneous extreme wind shear. Like Mav-JP says, I think they’re introducing a nice smooth interpolation system in the next update.
-
Thanks for the reply Mav.
Can you explain the interpolation? I remember that in earlier versions there was a map speed and direction, but since those settings are gone now I thought that there would be no dynamic weather changes aside from the updating of the weather map.
Nicolas
Of course, I’m not speaking for Mav-JP, just me. In earlier versions speed and wind direction still had interpolation at the borderline of a change in weather type because weather doesn’t change instantly at the borderline of the weather type change. So the interpolation was behind the scenes to get a smoother transition from one weather type to another. I can see why FMAP changes might be restricted to >= 1 hour in order to limit the amount of calculations at the borderline. With FMAP changes at < 1 hour, there would be many more borderline weather type changes. The interpolations at those numerous borderlines would require CPU power, and Falcon already is CPU intensive.
And now in 4.34 interpolations have to account for wind at altitudes from 0 to 50,000 feet.
-
@jc1:
Of course, I’m not speaking for Mav-JP, just me. In earlier versions speed and wind direction still had interpolation at the borderline of a change in weather type because weather doesn’t change instantly at the borderline of the weather type change. So the interpolation was behind the scenes to get a smoother transition from one weather type to another. I can see why FMAP changes might be restricted to >= 1 hour in order to limit the amount of calculations at the borderline. With FMAP changes at < 1 hour, there would be many more borderline weather type changes. The interpolations at those numerous borderlines would require CPU power, and Falcon already is CPU intensive.
And now in 4.34 interpolations have to account for wind at altitudes from 0 to 50,000 feet.
I am talking abou interpolation between maps not between cells
Interpolation between maps is missing in 4.34 that’s why you have hiccups
Nevertheless , map shall not be loaded less than every hour else it will break the interpolation between maps that will be included in U1
-
Even when you have two weather maps with near identical weather properties, there’s always this big reset when a new map is loaded; wind seems to go to zero, then back to map value, visibility goes to maximum, then back to map value, pressure resets, than goes back to map value.
-
Even when you have two weather maps with near identical weather properties, there’s always this big reset when a new map is loaded; wind seems to go to zero, then back to map value, visibility goes to maximum, then back to map value, pressure resets, than goes back to map value.
No
-