Magician

The wheel track on the F-15 is too narrow to use differential braking to make tight turns, not enough leverage for the thrust (or mass momentum) to pivot around the main gear. To make tight turns you have to hold down the nose wheel steering range key (default: "S") while using the rudder pedals to turn the plane. Also, you can't taxi fast while taking turns any more either, because the narrow wheel track is modeled more accurately, you'll tip the plane right over and ground loop.

ditto here. (with the TF-51), seems that the flight indicator works fine in missions with a hot start though, everything running and flight indicator uncaged at start.

I just went ahead and mapped my whole keyboard un-modified to the CDU, since the only key conflicts were with functions I had access to from my HOTAS, yoke and track-ir. The only problem was that mapping the space bar that way prevented progressing the training missions, so I made that lalt-space. lalt-W for the waypoint button, lalt-F for the fplan button, ralt-N for the nav button, and ralt-M for the mkppoint button.

It's still good to know what the crab angle should be as a starting point at least when you have no visual on the runway. With experience you don't need the calculator, but without experience it's better than spending all your time chasing the needles back and forth as you hunt for the right angle and over correct left and right.

Here' a virtual E6B: http://www.csgnetwork.com/e6bcalc.html Use the third block down, titled: Heading, Ground Speed, And Wind Correction Angle Enter wind speed, wind direction, approach speed under "True Airspeed", and runway heading under "Course" Below, in the "Heading" box will be the heading to fly once on the localiser, and do your corrections around that heading to stay on the localiser. Keep in mind that if your airspeed is higher than what you entered, the heading should be little closer to the runway heading, and further from the runway heading if you are slower. And here's an i-phone E6B app: http://mye6b.com/ And sporty's has Android and Kindle apps as well as really really old school E6B's here: http://www.sportys.com/source/features/search/search.cfm?catalog=PilotShop&question=e6b

Yep, if the actual velocity vector is "off the HUD", the TVV won't help. And you have to do it "old school", by just adjusting into the wind back and forth until the localiser needle stops drifting. Or doing some "E6B" calculations to figure the correction angle ahead of time, and remembering it increases with lower speeds. The above assumes no visual on the runway, with a visual you can use other references on the plane and the angle of the runway.

No you should fly wings level (no rudder or bank) with your nose pointed into the wind from runway heading (so that the off center TVV is lined up with the waypoint marker/runway). Don't worry about lining up the plane's axis with the runway until you are about to touch down. The TVV shows the direction your plane is actually going, so if you are on the localizer, and you keep the TVV on the runway/wp marker, you will not drift from inline with the runway. And once again, only side slip through the air with the rudder when you are about to touch down, so you don't land with the wheels pointed sideways.

Bare in mind that the ILS indicators have to remain centered. The TVV should be off center in the HUD if you have a crosswind, and the waypoint marker (the square symbol) should also be kept off center, lined up on a vertical line with the TVV. In fact, you should keep the TVV a little below the waypoint marker since the marker is halfway down the runway. But the glideslope indicator is what rules. Just as the localizer indication is. the TVV should only be a guide to how far into the wind from runway heading you should fly. Also you should maintain that heading wings level without rudder (You want to crab with respect to the ground, not the air), and only turn (with aileron and rudder) to correct any drift. and only use the rudder to sideslip just before touchdown to line up the wheels with the runway.

FWIW, I discovered that the HUD Bug in the FC2 carryover missions is due to some settings in the config\views folder of the MIZ file. I used 7zip to open and extract all from the miz file, and then re zipped all but that folder and renamed it to .miz. And the HUD was back to normal.

A lot of sims model the need for trim, it is just usually elevator and rudder, rather than aileron. IL2 and its descendants in particular require a lot of ball centering, due to torque or asymmetric drag loads, As for Falcon, it modeled the Flight Management Computer, which flies the plane according to what the pilot commands, if no attitude change is commanded, the computer will fly the plane to maintain attitude. In which case the trim worked to command a continuous attitude change, rather than stop one. There's also the fact that this sim models planes with uniquely high weights and moment arms out on the wings that can and do become unbalanced by mote and more often than most.

Oh and don't use just rudder to turn the plane, that tends to only change the direction the nose is pointing without changing the direction the plane is going through the air. That's the wrong kind of crabbing. You need to crab with respect to the ground, not the air.

If your HUD and EGI are operational, you can line up the TVV with the waypoint marker for the airbase, that'ss give you close to the right crab angle, and if the Localiser bar is centered, you're lined up with the runway.

T-80's are no problem to lock on, the only problem I have is with the Strela. Something for which you really need the stand off distance. As far as I can tell it won't lock to a Strela at all, at least not before eating an SA-9.

Just found this in the change list for update 1 to 1.2.6 under FC3: Several A-10A switches have had their position set to on: PAC Switch, Inverter Switch, AC Gen Switches, Radar Altimeter Switch, Anti Skid Switch, Fuel Boost Pump Switch, and Engine Fuel Flow Switches. None of which is true for the module version.

Also confirm, Cannot use ATC to RTB. comm menu for departure airport gets stuck with the abort takeoff option. Even if you try sending it, it still comes back with the same option.

And confirm, maverick (both the D and the K) won't lock on at all to a Strela. No problem with anything else I've tried.. Shilka, ZSU-23 on a Ural, BTR 80... In fact, sometimes when I tried to slew the cursor toward it from left to right, it wouldn't budge, like some kind of force field or sumpthin LOL.

Further attempts show that the port mission has the same HUD bug as the airbase mission, and it starts horribly with the player aircraft in a more severe dive than it did in FC2, and way out of position with the leader. And the guns and rockets practice mission has the same problem as the bombs and mav practice mission, hangs while unloading the GUI. Overall, there is also the problem previously mentioned with the maverick slew, in FC2 it was kinda squirelly, but now it is far worse. and the pitch up when firing the gun is very hard to deal with, so PAC would be greatly appreciated. ETA: Also previously mentioned about the amount of elevator input needed to rotate on takeoff..... and then the sudden rotation when it finally responds. But the flight model sure is more realistic, the thing is a dog with a full load LOL And I much prefer the new AP over the old one. On a more personal note, I still haven't come to terms with the fall line rather than pbil for the bombs (this goes for A-10C as well), wish I could stop my habitual reaction to the angle of the line, I always turn the wrong way in reaction to deviations.

The missions come with it for DCS World, they are in a folder appropriately called FC2, because they are adapted (well they tried), from the missions that came with FC2.

I can confirm the HUD bug in the FC2 airport raid mission. Makes things extremely difficult if not impossible, especially since they changed the dynamics of the mission. Static aircraft blocking taxiways in the ramp start and Nav mission. Haven't tried a reboot yet, but the bombs and maverick practice mission hangs up before even closing the GUI ... music keeps playing and have the Windows "working" circle going round and round. And those are the only three (of the fc2 missions) I've tried so far... A-10A module, Windows 8 x64 I have tried the 2 new missions and haven't run into any particular issues, but haven't lasted long enough to really find any LOL, was hoping to get more comfortable flying and fighting it with the old missions... oops.

Strike fighters had a mercenary campaign in it where you had to buy, not just weapons, but aircraft as well.

I have been using fast mission to practice starting up, and JTAC. Whenever the base is Krymsk, there are AWACs messages going to and fro almost nonstop, forcing me to wait minutes at a time to request clearances. I'm pretty sure AWACS shouldn't share with a tower frequency, so I think this is a bug. On a side note, how do you deal with 5 digit UTMs? I am thinking I need to add a leading zero, but haven't been able try it yet due to crashing issues, and although I think I solved them, I didn't try it this last time due to all tasking being aborted by the JTAC.