Quig

I can only talk on my own TMWH, but it's a distinct clicking sound when switching between the three modes (I assume we're talking about the 3-stage metal switch on the left hand throttle?). It's definately looser than the other switches, but still clearly clicking and no flopping, will only move if pushed. It's default mapping is for controlling lights, back is "set as lightspanel", middle is all lights off, and forward is.. I'm not certain, some kind of default light setup I reckon.

While not being an expert at all, there are a couple of things to aid you with your alignment. Firstly, when you contact the ATC you get directions to a point roughly 10nm off the runway, you'll easily notice this if you put a steerpoint on the airfield of you choice, and then talk to ATC, they'll give you a heading and a distance which do not match that of the airfield itself. This point is lengthwise out from the runway. Secondly, at the same contact call they give you which runway to land at. You can then dial in that course on the HSI, and it will give you the indication when you're aimed in the runways direction, and when you're aligned with it. Worth noting is that this needle isn't perfect, it oftentimes puts itself slightly off to the side when you're aligned perfectly for the runway, but if you get that far, you're regular ILS steering bars should be up and running, and you can ignore the HSI indicator from then on out.

That would seem to be the case. That makes some sense I s'pose. I'm just happy I finally (I think) have the wierdness with the windpage figured out.

Doh, ofc they are, all the other data is in meters. Makes perfect sense for alot of reasons too. Was kinda wondering on that wind picking up so strongly as just 8000. 2000m gives me roughly 6.500 feet. Almost the 7 I was able to input into the CDU then. I s'pose 26 shouldn't be a problem then even tho I haven't tried it. Close enough to make me happy, now I just need to remember to always make the direction, speed and altitude conversions from the auto-generated briefings to knots and feet. I'm still hoping for a future patch to make the ME conincide with the game, or a setting to make it so anyway. On that regard, is it how it works IRL, that you get the wind heading (towards direction, so to speak, not sure what the technical term is) in a briefing and you always have to convert it. Or is it possible that US gives their wind in the same way they have implemented in the A-10, so it makes perfect sense there, but other air forces have different proceedures? It just feels a bit strange that there is this big conversion needed. At least I think I can finally get some good out of the WIND page!

Just to clarify, this data is from the (in .09, the only) campaign, I'm not yet a mission creator myself. With that said I did some checking from the editor and noticed something strange. First, it seems you are correct, all of those winds seem to be in the opposite direction from how the wind should be inputed into the CDU, and the speeds were listed as m/s, so again, that's counterintuative to how the wind is to be inputed, as I guess the CDU only works with knots/s. Not only that but I were completely unable to locate any setting for metric or imperial in the ME. Game options has me listed as imperial, but the ME still shows m/s. Lastly, I noticed the weather page in the ME allowed one to set windspeeds and directions for 3 heights, those 3 mentioned, ground, 2000 and 8000. The altitudes was hardcoded, you had a textbox for speed and direction, but for those 3 altitudes alone. If the CDU isn't working for anything below 7000 (or so my tests seem to indicate) that practically makes the wind function still more or less inoperable. Could be something to take to ED maybe, fix one or the other. If the CDU is working as it's supposed to, then the ME should be able to give winds for higher altitudes, or fix the CDU =) Either way, right now it seems there's not to much point bothering about the wind inputs, when the only wind we can know is something we cannot input properly.

Good point. I'd have to check the inflight wind and see if the mission creator just interposed the m/s for knots/s or if the conversions need to be made. Same for wind direction I s'pose. But then at least it's not just me going crazy, but there is something fishy going on with the wind page afterall then? I wonder, is it better to leave it as is, or would some wind data be better than none. My thinking here being if you can't have the whole spectrum as given by the briefing, just some parts might skew the data incorrectly, as oposed to letting the computer work with a blank slate. Thoughts?

Unless I'm severely misstaken, since .09 we're able to input wind conditions for different altitudes to improve our dumb (or was it guidance challanged?) bombs accuracy. Anyone else having issues with this? I can input ground wind no problemes by following flight manual instructions, but when it comes to other altitudes, no dice. For instance, I have this data from my campaign mission: 0: 327 deg, 2m/s 2000: 302 deg, 5m/s 8000: 288 deg, 9m/s Now, according to flight manual, first you specify altitude in thousands of feet on the scratchpad, then click a free row of wind. If I input 0, I get 0 feet (logical, yes), if I input 2, I get an "CDU input error". If I try 02, same thing. Now if I put in 08, I get 07 on the windline (I assume here it's 7000 feet, why 7, when I give it 8?). To experiment I also input 20 (for 2000) which also didn't work (not very surprised), and lastly I tried 80 (for 8000) which resulted in a line of 79, which again seems just plain wierd. So, is there something else that needs to be done to make this work, am I missing something, or is there something fishy going on with the wind inputs?