So I'm reading about this, trying to figure it out. There's a CDU page LASTE>WIND, presumably for supplying the targeting computer with wind information for correct aiming. But previous tests have found it to be ineffective (as in no effect whatsoever). There are some users on the ED forums in a post describing how it's magically fixing things but I think it's a lot of hot air, they have a special version where it worked or whatever.

So I try some tests. I did some runs with strong wind and no LASTE data, correct data. Then I try no winds with no data and again with false data. By now I am pretty convinced that this LASTE wind data has absolutely nothing to do with CCRP aiming. I don't know about real life, but in 1.2.0 it does nothing for CCRP or CCIP.

However by chance I have the yellow command bars enabled and as I cycle the LASTE data from NONE, WIND, TEMP, BOTH I notice that it jumps around. Interesting! So I change my FP attribute to TO FROM, line up the CRS knob and then do some tests. When I cycle the LASTE data to something involving WIND (WIND or BOTH) the commanded steering is directed as if to crab into a wind.

This is my WIND page, adding in silly data.
Code:
WIND     F1  1     D5/I1
                   360/000 -8
                        NONE
ALT    WIND  TEMP
[] 00 360/50 +00 WINDEDIT <-

[] 13 090/50 +20    CLR*

[] 59 180/50 +00    LASTE <-
 [                ] P1/2


Using WIND setting:
Code:
WIND     F1  1     D5/I1
                   092/050 -8
                        WIND
ALT    WIND  TEMP
[] 00 360/50 +00 WINDEDIT <-

[] 13 090/50 +20    CLR*

[] 59 180/50 +00    LASTE <-
 [                ] P1/2


Notice that the line 360/00 (which is the real wind, determined automatically) has changed to be (092/050) which is close to the 13,000' entry. Why 092 instead of 090? I think it is blending to the next highest data point (59,000'). I'm at 14,180' so it's between 090 and 180, closer to 090 because I'm much closer to 13,000' than 59,000'.

Notice that the "-8" (-8°C) is still reading -8. You'd expect that if I changed the setting to TEMP or BOTH it would display my acknowledged temperature based not on CADC data but instead interpolated as a mean between the LASTE data points. I'll try BOTH:
Code:
WIND     F1  1     D5/I1
                   092/050 -8
                        BOTH
ALT    WIND  TEMP
[] 00 360/50 +00 WINDEDIT <-

[] 13 090/50 +20    CLR*

[] 59 180/50 +00    LASTE <-
 [                ] P1/2


And you see the temperature is unaltered! I'd expect 18 to 19°C but it remains the real -8 from the temperature probe. I believe this is a bug in the software. Additionally my "OAT" readout on the POSINFO page shows -10°C. So for some reason the temperature readout is not even the CADC value.

Note that wind entered in the ME is "wind to" in true while the aircraft assumes "wind from" in magnetic (I'm pretty sure magnetic). Thus 090°T wind is coming from 276°M. All wind information in the jet is in knots and magnetic heading. ATC gives wind in true, but I think this is a mistake. All ATC wind (and turn instructions) I have ever received in RL flying has been magnetic. The only true direction data I have ever seen is from printed paper weather reports.

In conclusion:
  • Manually-entered LASTE WIND data has no effect on weapons aiming.
  • Manually-entered LASTE WIND data has an effect on navigation cues such as the DHC "captain's bars" on the HUD and the steering bars.
  • Manual temperature data appears to be non-functioning.
  • The "WND" line on the STRINFO page shows the currently-utilized wind/temp data.


Edited by Frederf (07/28/12 01:27 AM)