richjb

Thanks Pils! Rich

Greetings, I took the B737 for a flight today. After takeoff, I was climbing in LVL CHG and HDG. After engaging the autopilot, the control yoke began oscillating back and forth and stab trim was moving nose up and nose down. I could not tell which control was leading. You could see the in sim yoke move back and forth while the stab trim wheel rotate nose up and nose down along with the wheel sound. It continued to occur even after I disengaged the autopilot and went back to FD mode. It was not until I made a manual stab trim input that it stopped. Best that I can tell, I have no control conflicts in XP, i.e., multiple control axis or button assignments. Any thoughts on what the problem might be? Thanks! Rich Boll

I have not discussed it with them. The Autopilot engage button is the only one that does not work. In fact, I have been able to program my Goflight MCPPro and EFIS to a greater extent in HS650 using dropdown boxes in PolyPot's GoFlight modules than I have any other airplane. The only button that doesn't work is the autopilot engage, and per Toto, it's the time delay that you mention. Is that delay covered in the X-Plane SDK?

That's per Toto over on the HS650 Discord channel. He said that he was considering making an option to bypass that one-frame delay to permit hardware binding. That was a couple weeks ago. Rich

Going into Preferences and unclicking the use KG solved the problem. I didn't even think about looking there! <sigh> Sorry for the fire drill! Thanks again! Rich

argh.... I did not even think to check KG v. LBS. I did not check that. I'll check it after dinner and see if that fixes the problem. 93.3 KG might be a bit high...ya think! Thanks! Rich Boll

Greetings all, I updated to Ver 1.5.1 yesterday. First flight, found that I was unable to enter either the ZFW or the GW on the PREF INIT page in the FMC. When I entered the ZFW or the GW, the INVALID ENTRY appeared in the scratch pad. See attached screen shot: I thought it might be a corrupt installation, so I uninstalled the program and also deleted the IEXG 737 Classic Folder and its contents that remained after the uninstall. After the clean re-install, loaded a new flight with a new airplane livery just to make sure. Same issue. Without being able to load the ZFW or GW, I'm not really able to fly the airplane. We'll could, but it wouldn't be any fun. This was not an issue with 1.5.0. It came up after the update to 1.5.1. I can revert back if needed. Any thoughts on why this is occurring and/or how to fix? Thanks! Rich Boll

I just did a V1 cut and a continued takeoff, litmus test for me with a new aircraft model. I only have one word to say... PERFECT! Well done, IXEG! Well done! Rich Boll

Thanks Pils All of the above changes worked! Rich

Hi IEXG team! First, great to have this airplane back in the XP hangar. I've been flying it around Kansas &Colorado and having a blast! I'm mostly shaking things out, getting joystick bindings set, etc. Which brings me to some questions: 1. Where should I set Navigraph to update the IXEG's Navdata? Which folders? Navigraph is not finding the correct folders in "auto" mode. 2. Do not see a CONTROLS setting in IXEG for binding the TOGA thrust level switch to a joystick button. What should I use? 3. The default binding in CONTROLS for "Parking brake on/off" does not work in IXEG. What binding should I use? 4. Possible Bug: The Windshield Wiper switch does not move when you either rotate the mouse wheel, click on either side, or "drag" the switch to change settings. No way to turn on the wipers, which is essential if XP12 is raining! This one might be confirmed, but I'll include here as well. 5. Question....possible bug(?) The airplane appears to lack elevator authority in the landing flare. Crossing the threshold right at VREF speed, reducing thrust at about 30' with it closed at touchdown. All landings are very firm, and some are three-point with the nosewheel touching at the same time as the mains regardless of how much elevator up I am adding. Is anyone else seeing the same thing? I have 15% set on the Pitch and Roll sensitivity just to take some of the "bounciness" out of the control wheel inputs. Any t houghts? Time to do some chores around the house before I get in trouble with the wife. I'll be back later! Thanks again! Great airplane! Rich Boll

On my way between KDEN and KSLC!!!!!!!!!!!

Ok... we need correct something here. We do not turn off the flight directors when established on an ILS approach, even in the Boeing aircraft. In fact, without a flight director, in part 121 or part 135 operations, your approach landing minimums increase automatically to 4000 RVR or 3/4 SM regardless of what is on the instrument approach by OpSpec. OpSpec requires use of the flight director or autopilot to use the published landing minimums for these operators. In addition, the use of flight director, autopilot, or HUD is required in certain circumstances to fly an approach to 1800 RVR instead of the published 2400 RVR as noted on the approach. Speaking to Collins about the Proline 21 flight director's behavior on an ILS approach, the flight director command bars do follow with an initial pitch change that you may make manually. Not with the roll, but with pitch only. Until it sees a deviation from the glideslope, the command bars will not display a correction command. For this reason, it appears that the command bars initially follow any pitch change initiated by the pilot, intentional or otherwise. I have tested this both in the simulator and the actual aircraft. It is a behavior that we see in other autoflight systems as well, for example, the Garmin system in the Lear 75. For the most, this behavior is accurately depicted in HS650. The flight director is a required component for ILS approaches in a turbojet. It should not be disregarded when flying an ILS approach. Rich Boll

Thank you!

You could do that, but it might be just easier to change the DEST in the FLT PLN page once you're heading towards your alternate airport. The go back into the LEGS page and build the route to the alternate. First, get the airplane going to the first fix on the route. Let's say that Wichita KS (KICT) is your destination and Hutchison KS (KHUT) is your alternate. You're tired of shooting and missing the ILS 01L approach at KICT due to fog, etc., whatever. Time to go to KHUT. Wichita gives you the following clearance to KHUT: "N1234 is now to cleared to the Hutchison airport via direct Wichita VORTAC, Victor 73, Hutchison VORTAC, then direct, climb and maintain 6000". By the way, this was a common clearance we gave in the sim when I was an instructor in the Learjets while at FlightSafey. Step 1: On the LEGS page, type in ICT to go direct, then EXEC Step 2: On the FLT PLN page, change DEST to KHUT Step 3: On the FLT PLN page, delete any remaining approach going into KICT Step 4: on the FLT PLN page, type in: V73 HUT DIRECT KHUT (this is optional) Step 5: On the DEP/ARR page, select KHUT and enter the expected approach, e.g., ILS 13 Your performance data should remain, i.e., PAX and CARGO, ZFW entry, etc. With ALT LEGS page, you can set some of this up ahead of time. However, as practical matter, I have never used the ALT LEGS page to preload my flight the alternate. Most of the time if you are diverting to your alternate, ATC will clear you direct. In mountainous areas, that might different. ALT LEGS page is mostly used for programming your engine failure departure procedure, so that it is ready to use if the engine fails on takeoff after V1, assuming that it is not a straight-out departure. Rich

You will have to do that to get the approaches for the alternate. The ALT LEGS page allows you to pre-program your route to your alternate before you begin the approach to the destination. In the meantime, using the ALT LEGS page allows you to monitor fuel required to the alternate and reserves to post the CHECK FUEL AT ALTERNATE message. Rich