var wv = windVec.new(d0, v0);
append(altvec, wv);
var res = add_vectors(dir_min, (1-f) * vmin, dir_max, f * vmax);
var vmin = w.alt[i-1].v;
var vmin = w.alt[0].v;
var vmin = w.alt[1].v;
Adding aloft weather point for 27.93155061499999,-15.38558745
Vmin is null!
1
1083.755495041428
5000
15.2110922752
Nasal runtime error: nil used in numeric context
if (vmin == nil) {
print("Vmin is null!");
print(i);
print(alt_wind);
print(wind_altitude_array[i]);
print(w.alt);
print(w.alt[i].v);
print(w.alt[i-1].v);
}
print("First altvec: " ~ d0 ~ " " ~ v0);
print(getprop("/environment/aloftwind/windspd/mb1000"));
SurferTim wrote in Tue Aug 20, 2019 9:35 am:V12 wrote in Tue Aug 20, 2019 7:09 am:Hmmm, again discontinuity in weather. I'm happy that I'm not alone with this nasty problem. I crashed many times in GA aircrafts with this reason - steep wind speed and direction changes. When You are climbing 80 kts in C172 a 20 kts headwind change direction about 180 degs in half second, You have almost unsolvable problem. When You have this problem 3 or 4 times in one day, You will stop use GA airplanes or leave FG.
I see a third alternative. I haven't looked into it deep enough yet, but now you have my interest up.
There must be a way to prevent radical wind direction, speed, and altimeter setting changes (the three settings that could kill you) to just change in an instant. It needs to be slowed up somehow. I have used setListener very effectively in the past. Is there a way to get a new METAR report, then slowly change each of those three settings over 30 seconds or so? That might give a pilot time to adjust.
I often see wind direction changes at high altitudes of e.g. a 60 knot tailwind to 50 knot headwind with live weather (or even greater) et vice versa in a fraction of a second. I use aloft waypoints wind model.
Users browsing this forum: No registered users and 1 guest