There is no "problem" with the iFly 737NG A/P.

 

In order to engage the A/P, the aircraft must be properly trimmed and no pressure/spikes from a controller or input from duplicate key assignments.

 

Jim Harnes

 

 

Hmm, turning on the autopilot myself does sound interesting. I might try it before I do the reinstall. Also, when I mentioned that problem on Ifly's autopilot, I'm referring to the fact that there is known problems with its autopilot, but they do have simple solutions.

 

If FS2Crew doesn't turn on the autopilot when so commanded, try manually pressing the autopilot button on the autopilot panel.

 

If it doesn't turn on when you press the button by hand, your autopilot is not configured properly to accept an autopilot engagement.

 

Remember all FS2Crew does is send a signal to the iFly to turn on the autopilot via an SDK command; we don't touch the internal system's logic.

As I recall, you are using the keyboard as a controller.  As a consequence you cannot use the CTL+K option to disable the 'joystick'.  You must, however, make sure that nothing in FS2Crew is using the 'Z' key.

 

DJ

Wait, you can see what key FS2Crew uses? The only keys I assigned for FS2Crew was 'E' and 'R'

At this point, I suggest you manually use the 'Z' key and see what happens.  FS2Crew should use the same key, as Bryan noted.  In all of the discussion we had on the iFly support forum you never made it clear that you were attempting to engage the a/p using FS2Crew.  If you cannot engage via the 'Z' key then there is clearly a conflict with something that is intercepting they key press - my first thought would be to make sure that you have not left the FMC with the keyboard engaged since that will intercept all key presses.  If that is not the case then start looking at whatever other add-ons you are using.  I spent close to two years as part of the 737 test team and I guarantee there is nothing the matter with the autopilot.

 

DJ

Wait, you can see what key FS2Crew uses? The only keys I assigned for FS2Crew was 'E' and 'R'

 

No, FS2Crew button control just uses those two keys (for primary and secondary) they're suggesting you use the 'Z' key as that's the default autopilot toggle key. There's no harm in trying the Z key but I'd definitely physically click the CMD A button on the MCP first.

 

FS2Crew isn't 'pressing the Z key' it's using the SDK to send the Autopilot on command.

 

In short, try clicking the button first.

... Yep, that did not work. I still can't activate the autopilot. I'm probably just going to do a reinstall. I'll report back soon.

... Nor did the reinstall. What am I doing wrong???

Can you activate the autopilot manually by pressing the CMD button on the autopilot panel?

Nope, nothing works. I've pressed it manually, did a full reinstall and it still does not work. What about those SDK, and Simconnect things you guys are talking about. Are those add-ons or are they built into the game? Maybe I can install them if they are add-ons, but their is no way I'm reinstalling FSX. I have major problems reinstalling FSX, and I downloaded so many add-ons and tweaked FSX to such a perfect state, that I doubt I'll be able to do all of that again.

 

 

Nope, nothing works. I've pressed it manually,

 

Re-fly one of the iFly tutorial flights... make sure your FMC and autopilot panel are configured properly.

 

If you can't even engage it manually, something is amiss with your iFly, or you're just not setup right.

 

Does the iFly have an option to that allows you to enable the autopilot even with force applied to the yoke?  I know the PMDG NGX does.

 

If so, enable it for starters.

Just chiming in my personal experience here with FS2Crew,

 

The iFly 737 autopilot engages fine when I'm all trimmed out and not applying pressure to the control surfaces.

So I've been looking through my IFly 737 files, but nothing was missing. I've looked at the configuration/options, and I have noticed an option that allows me to inhibit yoke controls while the autopilot is engaged. Thing is, isn't that similar to just pressing the CWS button? I'm going to dig in to some more files, and see if there is anything amiss.

OK, I have noticed something very strange. So today, as I was about to make a descent into San Francisco International, I've decided to give FS2Crew a go. I've skipped all the way to the decent checklist and 'activated' it after that. Of course I had the plane correctly set up, and to my amazement he did not interfere in any way with the autopilot. I had a successful descent and landing at KSFO.

So this obviously means that in between setting up the plane and takeoff, FS2Crew is doing something that it is not suppose to do. It will be extremely helpful if someone can provide me details into EXACTLY what FS2Crew does.

FS2Crew only sends a signal to the autopilot when you make an autopilot command.

 

As I mentioned frequently, FS2Crew does not touch any internal autopilot logic.  We couldn't even if we wanted to.

 

If you can't engage the autopilot manually by manually pressing the button on the autopilot, then something else is going on.

 

Best,

Yes, I understand what you mean but so far, I can only find FS2Crew as the culprit. I've looked into everything, yet nothing seems to be amiss. It's very strange that I am only able to activate the autopilot without FS2Crew activated. I have tried reinstalling everything which did not help. I don't know what else can be causing it. I have been changing the settings to see what happens but that does not help either. There is definitely something wrong going on here, but until then, it's safe to assume their might be miss communication with the aircraft and FS2Crew.