I'm mostly an FSX person now, but the 737NG from iFly looks to be spectacular and I've really been waiting for a great 737. I must say overall I am more of a systems person than a good looks and that is why the PMDG NG for FS9 has fallen by the wayside for me. After talking to some people who have the aircraft, I have just a couple questions.1. Most important, I've heard some people say that they have had difficulty assigning custom keyboard commands from the iFly menu to button presses in FSUIPC. For me, this is important for a few of the key function I need during take off and departure like gear up, TO/GA, AT disconnect. Is there anyone who is successfully programming these functions through FSUIPC to buttons for the iFly?2. I have heard of difficulties initially engaging autopilot in the VC. It seems from what I can tell that you need to switch to a 2D view to engage it the first time. Is this true? Is there anyway to engage it from the VC? This is what I fly in all the time and it is hard to control an airplane precisely while switching views.3. I've heard reported issues that spoilers can get stuck in a "mid" deployed position and can then not be fully retracted to down, just back to "ground arm" which triggers a takeoff config warning. The person who reported this to me was assigning a spoiler axis in FSUIPC, so perhaps this was the issue.4. I know it requires more thrust than it should to taxi. Any indication if this is being worked on?I'm likely to buy this soon, but would like to get a bit more information on these issues, in particular #1 and #2. Looks like a great aircraft.

I'm mostly an FSX person now, but the 737NG from iFly looks to be spectacular and I've really been waiting for a great 737. I must say overall I am more of a systems person than a good looks and that is why the PMDG NG for FS9 has fallen by the wayside for me. After talking to some people who have the aircraft, I have just a couple questions.1. Most important, I've heard some people say that they have had difficulty assigning custom keyboard commands from the iFly menu to button presses in FSUIPC. For me, this is important for a few of the key function I need during take off and departure like gear up, TO/GA, AT disconnect. Is there anyone who is successfully programming these functions through FSUIPC to buttons for the iFly?2. I have heard of difficulties initially engaging autopilot in the VC. It seems from what I can tell that you need to switch to a 2D view to engage it the first time. Is this true? Is there anyway to engage it from the VC? This is what I fly in all the time and it is hard to control an airplane precisely while switching views.3. I've heard reported issues that spoilers can get stuck in a "mid" deployed position and can then not be fully retracted to down, just back to "ground arm" which triggers a takeoff config warning. The person who reported this to me was assigning a spoiler axis in FSUIPC, so perhaps this was the issue.4. I know it requires more thrust than it should to taxi. Any indication if this is being worked on?I'm likely to buy this soon, but would like to get a bit more information on these issues, in particular #1 and #2. Looks like a great aircraft.

1. Don't know too much about this. I disconnect the autothrottle via the switch on the main autopilot panel in the VC or the disconnect button on the throttle itself in the VC.2. Not true you can activate the AP in the VC like any other high level add-on. There are sensitivity issues with various joysticks/yokes that could be an issue. Just like the real NG moving the yoke can disconnect the AP. There's an adjustment for this in the included iFly config utility that'll solve any issue with the yoke sensitivity where bumping it and/or a slight uncentered position doesn't disconnect the AP.3. I haven't seen this. I don't know why some people are playing with FSUIPC at every drop of the hat. I've never touched FSUIPC since I had this add-on. You can assign yoke/joystick commands via the FS menu under 'Assignments' and never have to touch FSUIPC.4. This will be addressed in the first full service pack.

( I don't know why some people are playing with FSUIPC at every drop of the hat)I wouldn't exactly call it playing with FSUIPC at every drop of the hat :) From how you have described your setup you are clicking buttons in the VC or 2D using your mouse which is good if it works for you. Many off us use hardware that enables us to fly from startup to shutdown with little or no use of the keyboard or mouse, a reg version of FSUIPC is essential for this.Regards

2. Not true you can activate the AP in the VC like any other high level add-on. There are sensitivity issues with various joysticks/yokes that could be an issue. Just like the real NG moving the yoke can disconnect the AP. There's an adjustment for this in the included iFly config utility that'll solve any issue with the yoke sensitivity where bumping it and/or a slight uncentered position doesn't disconnect the AP.

My understanding on this issue was not that you could never engage the autopilot from the VC. Rather the first time you engaged the autopilot (and only the first...i.e., after takeoff climbing out), clicking the button in the VC didn't work and people needed to go to the 2D to do this. Reportedly, the autopilot buttons worked just find after this in the VC. I've also heard people state that assigned keyboard commands didn't work to turn the autopilot on the first time on the VC.I am not referring to the autopilot reverting to CWS mode when the yoke is moved. I've read of people with this "problem", but it is actually a realistic representative of the systems and can be programmed.

My understanding on this issue was not that you could never engage the autopilot from the VC. Rather the first time you engaged the autopilot (and only the first...i.e., after takeoff climbing out), clicking the button in the VC didn't work and people needed to go to the 2D to do this. Reportedly, the autopilot buttons worked just find after this in the VC. I've also heard people state that assigned keyboard commands didn't work to turn the autopilot on the first time on the VC.I am not referring to the autopilot reverting to CWS mode when the yoke is moved. I've read of people with this "problem", but it is actually a realistic representative of the systems and can be programmed.

In my experience of the iFly what you have heard is completely untrue. I can engage the AP from the VC first time every time, without needing to faff about in the 2D in any manner. I have also not had any problems with unintended disengagement of the AP.

The iFly 737 is a great sim. The only time I have had any problem with the auto pilot is if I load the aircraft without loading the default Cessna 172 first.I believe this is a problem with any complex simulation and even PMDG developers will tell you to load the default Cessna or Ultralite (FSX) first, then wait about 15 seconds or so until everything settles and load the more complex aircraft.After loading the default aircraft, I will select Shft+F1 to turn off the engine by cutting off the fuel.iFly has done a very impressive job of making a very enjoyable 737. I can't get enough of it and look forward to the release of the FSX version for only $14 USD more (I just can't get over that!) :(

( I don't know why some people are playing with FSUIPC at every drop of the hat)I wouldn't exactly call it playing with FSUIPC at every drop of the hat :) From how you have described your setup you are clicking buttons in the VC or 2D using your mouse which is good if it works for you. Many off us use hardware that enables us to fly from startup to shutdown with little or no use of the keyboard or mouse, a reg version of FSUIPC is essential for this.Regards

I agree. I set up button and axis profiles for all of my aircraft in (registered) FSUIPC. It's the only way to go! I can't imagine using FSX options except if the specific aircraft requires it for the throttles which use FADEC, like the Superbee or Airbus A320.

Cutting to the chase:

1. Most important, I've heard some people say that they have had difficulty assigning custom keyboard commands from the iFly menu to button presses in FSUIPC. For me, this is important for a few of the key function I need during take off and departure like gear up, TO/GA, AT disconnect. Is there anyone who is successfully programming these functions through FSUIPC to buttons for the iFly?2. I have heard of difficulties initially engaging autopilot in the VC. It seems from what I can tell that you need to switch to a 2D view to engage it the first time. Is this true? Is there anyway to engage it from the VC? This is what I fly in all the time and it is hard to control an airplane precisely while switching views.3. I've heard reported issues that spoilers can get stuck in a "mid" deployed position and can then not be fully retracted to down, just back to "ground arm" which triggers a takeoff config warning. The person who reported this to me was assigning a spoiler axis in FSUIPC, so perhaps this was the issue.4. I know it requires more thrust than it should to taxi. Any indication if this is being worked on?

1) Absolutely no problems mapping functions through FSUPIC. All fully mapped to home-built MCP.2) No problems engaging through VC - once again, functionality mapped to MCP. Use FSUIPC to calibrate your yoke / joystick though.3) Never encountered this.4) This is (ever so) slightly annoying as > 40% N1 is required to get things moving. However, this and other issues / improvements are being worked on.Great A/C though and well worth the purchase. Gary