Well, I bit the bullet and purchased the 2004 iFly yesterday. Very nice...I just wanted to get the feel of the bird in the air before pouring through the 104 page (whew!) Operations Manual.I can't seem to get the Command A or Command B to light up green...and hence no Autopilot. I just wanted to climb to 10,000 and look around. Do I have a bad install, or is there some other system that must be set before you can access the Command A function button. Do you have to have something set or activated on the FMC?Thanks in advance.Mitch

Going to recommend you register at Ifly support forum, that has been covered to wits end and the fixes are listed there.

Going to recommend you register at Ifly support forum, that has been covered to wits end and the fixes are listed there.

Ok registered in the Private Members.I tried all the suggestions to get the CMD A or B to engage. No luck! It amazes me that in all the raving and discussions, there was no mention about how finicky if usable at all...the autopilot engagement simulation was on this bird if using a joystick or flight yoke.Mitch

Hi Mitch,Like in the real aircraft, you cannot engage the autopilot as long as you put any pressure on the yoke. As you were climbing, this might have been the reason. By the way: I would recommend to read the tutorial, which is im my opinion more useful to start with than the ops manual.Regards,René

Hi Mitch,Like in the real aircraft, you cannot engage the autopilot as long as you put any pressure on the yoke. As you were climbing, this might have been the reason. By the way: I would recommend to read the tutorial, which is im my opinion more useful to start with than the ops manual.Regards,René

Thanks Rene,I went back to the support forum and found one more suggestion...and that worked to allow me to engage the CMD A. I had to not drop the sensitivity on my Saitek, but rather in the MY FLEET and lower the joystick sensitivity down to 3 bars above MIN. That worked. I now am trying to get the LNAV and VNAV to work. I intend to read through all the manuals, as this really seems to be a most interesting purchase. I just have to wonder about why they made the AUTOPILOT simulation so sensitive, as to be troublesome to use for quite a few users.

I too have a Saitek stick and found that the iFly config alone was not enough, I had to tweak the sensitivity and null zone of both the ailerons and elevators in the FS options. Once I'd done that, it was fine. Also, knock the aileron and elevator sensitivities down for keyboard input in the FS options, that can also help.Al

Thanks Rene,I went back to the support forum and found one more suggestion...and that worked to allow me to engage the CMD A. I had to not drop the sensitivity on my Saitek, but rather in the MY FLEET and lower the joystick sensitivity down to 3 bars above MIN. That worked. I now am trying to get the LNAV and VNAV to work. I intend to read through all the manuals, as this really seems to be a most interesting purchase. I just have to wonder about why they made the AUTOPILOT simulation so sensitive, as to be troublesome to use for quite a few users.

It isn't finicky but just the real thing.If the real 737 is out of trim and the controls are thus under pressure, good luck on engaging the AP's.Same with the iFly 737.I honestly haven't had any trouble with it from day 1.But as I have read, we had a lot of "complaints" about it when the FS9 version was there too.It forces one to fly differently and we all know how humans react to change :( cheersJP.

It isn't finicky but just the real thing.If the real 737 is out of trim and the controls are thus under pressure, good luck on engaging the AP's.Same with the iFly 737.I honestly haven't had any trouble with it from day 1.But as I have read, we had a lot of "complaints" about it when the FS9 version was there too.It forces one to fly differently and we all know how humans react to change :( cheersJP.

Hi JP,Loving the rest of the plane. BTW, I think that this airframe is the most realistic 'feel' on the ground or in the air. Especially on the ground. I would kill for all my planes to react to the stick in ground handling and throttle/engine response as the iFly 737 FS9 version does! This is superb in fact. Running with a locked down 60 FPS in FS9 really helps things along, you know what I mean? :)Edit: I also realise that I probably should not be discussing 'fixes' outside of the lock-down forum. For obvious reasons....like those that 'walk the plank' and run Torrents, Matey.... I usually come to AVSIM first for wanting to post a question, but should change my M.O........Mitch

I too have a Saitek stick and found that the iFly config alone was not enough, I had to tweak the sensitivity and null zone of both the ailerons and elevators in the FS options. Once I'd done that, it was fine. Also, knock the aileron and elevator sensitivities down for keyboard input in the FS options, that can also help.Al

Thanks Al, will try all suggestions. I'm really liking this bird. I haven't tried to bring in repaints yet...will read and run through the Tutorials and the Operations Manual and get proficient with the flight deck before doing that, lol. I'm thinking of bringing the FSX version online as well.Mitch

I'm starting to sound like a real a really excited user, but honestly I have experienced this only once (Saitek Evo stick), and I had not trimmed properly. Other than that instance the bird has really not given me any unusual issues with any autoflight systems engagement, and I started with SP1 version. I use the MyFleet sensitivity slider just for tweaking responsiveness, not fixing a/p.Go figure :(

Overall, I must say I too am rather impressed. I have some problems with route input in the FMC (already posted about it at the iFly forums), but I have a way to work around it. For the rest, beside some FPS issues now and then, this plane is unbelievable. It just works. It seems to me to be really stable, very reliable. Everything functions correctly, the plane handles nicely... Loving it! Did ESSA-ENBR, which was a stunning flight (I LOVE FSDT's Bergen ENBR scenery. It's beautiful!), now doing ENBR-ESSA, going very well so far.Not perfect - not yet, but nearly perfect for sure!

I'm starting to sound like a real a really excited user, but honestly I have experienced this only once (Saitek Evo stick), and I had not trimmed properly. Other than that instance the bird has really not given me any unusual issues with any autoflight systems engagement, and I started with SP1 version. I use the MyFleet sensitivity slider just for tweaking responsiveness, not fixing a/p.Go figure :(

I just picked up the FSX version. I ran the beast and even though I had trimmed out to no plus or minus altitude change, (and not trying the fix..) I couldn't get anything to light up on the A.P. So...what EXACTLY does being properly trimmed out mean,if you are not properly trimmed out by being at level flight and not touching the control stick?!?!? This beats me! How do you have no issues and not use the My Fleet?!?Would love to know...Mitch

I just picked up the FSX version. I ran the beast and even though I had trimmed out to no plus or minus altitude change, (and not trying the fix..) I couldn't get anything to light up on the A.P. So...what EXACTLY does being properly trimmed out mean,if you are not properly trimmed out by being at level flight and not touching the control stick?!?!? This beats me! How do you have no issues and not use the My Fleet?!?Would love to know...Mitch

Make sure your joystick is properly calibrated in Windows and the nullzone is set wide in FS and in the ConfigManager/My Fleet and you should be good to go - I run an ancient Saitek X36 and have had no problems...DJ

Make sure your joystick is properly calibrated in Windows and the nullzone is set wide in FS and in the ConfigManager/My Fleet and you should be good to go - I run an ancient Saitek X36 and have had no problems...DJ

Thanks DJ, I am fiddling around with the settings and got the FSX version (that's what I'm in flight with right now) A.P. to light up. Everybody's right...you have to keep fiddling around until iFly likes being on your system, I guess, LOL. I originally got the FS9 model, and if I generally liked it, would, and did pick up the FSX version for another $14.95. That was a no-brainer.Getting cozy with the all the manuals...is probably the ultimate 'fix', huh?The bird looks great on both platforms.Cheers,Mitch

I just picked up the FSX version. I ran the beast and even though I had trimmed out to no plus or minus altitude change, (and not trying the fix..) I couldn't get anything to light up on the A.P. So...what EXACTLY does being properly trimmed out mean,if you are not properly trimmed out by being at level flight and not touching the control stick?!?!? This beats me! How do you have no issues and not use the My Fleet?!?Would love to know...Mitch

I usually take off, adjust trim until the aircraft maintains v2+20 (or just accept whatever reasonable initial climb speed I stabilize at) without any stick pressure, then just push CMD A or B, boom - a/p engaged. I'm not the best sim hand flyer by far, I rely heavily on autoflight. so if anybody would have issues it's me, but I don't.edit - just to add: My Saitek stick is sensitive/noisy in it's initial ranges, so I have set null zones in Windows control panel for all axes to cover these noisy ranges.