mgeiss

You can edit/add the ICAO identifier with a text editor to prevent unwanted changes by Plane Maker. The relevant line to edit/add in the .acf file is P acf/_ICAO SF34 If no P acf/_ICAO line is in the .acf, you need to add it between those two: P acf/_HUD_del_y 150.0 P acf/_ITT_is_C 0 (values may be different from Aircraft to aircraft) So that it looks like this for e.g. an B737-300 P acf/_HUD_del_y 150.0 P acf/_ICAO B733 P acf/_ITT_is_C 0

2 is fine for normal planes and I think the IXEG flies just fine with that. I only use higher values for helicopters, where it helps with the constant fine control adjustments.

Could be a flaps failure due to overspeed (X-Plane function, can be turned off). Do you have flaps assigned to an axis? Try to un-assign that axis and use buttons or keys instead for a quick test. There are cases where flaps are not retracted fully even though the flaps lever on the hardware controls is in the fully up position.

In the IXEG it's not livery-specific. The plane itswelf was modeled with some operator-specific items (as pretty much every plane out there has/had operator specific options).

IIRC this is intentional and modeled after the real plane (at least in the Lufthansa variant), where the aural altitude alert is not triggered when the AP flies the plane and is about to intercept the altitude.

Well, the Challenger's roots go back to X-Plane 9 and although it was constantly updated and refined, it does show it's age visually to some degeree. That being said, it's still the best and most realistic bizjet in X-Plane. so I wouldn't think twice if you are into this kind of aircraft. It might still take some time for something equal or better to surface (e.g. thinking about the LES Citation).

I get that people are exited about flying a fully functional 340 in XP11, I'm looking forward to that, too. But let's face it: We bought the plane as advertised for XP10. Neither LES nor X-Aviation is obligated to give us an update for XP11, let alone a free one. So with that in mind (and given the constant changes LR is introducing to XP11 all the time) we should just be patient. Constantly asking about when the update will be available to us won't speed up the process a single bit.

There should be a livery manager in the aircraft directory, so you don't need to re-run the installer in this case.

I believe it's actually preselected (being the base package) and just greyed out in order to not let the user de-select it by mistake.

1. PFPX profile tweaked to the last 0.01% - check 2. Austin decides to tweak a few parameters in X-Plane - check 3. Realizing that you burned 15.3 lbs more fuel than the PFPX loadsheet said - check Back to 1.

Before the end! (Comes with a free towel).

I also had that error lately, and by switching off mouse wheel manipulators in the options I could at least finish the flight, so I suspect it has something to do with that. Unfortunately, I didn't save my logs but will do that next time if the error occurs again.

The X-Plane 10 GNS does not support SIDs or STARs, only approaches. That functionality was added in X-Plane 11.

Did you just set the X-Plane option to start with engines running, or did you select the "Ready to Fly" state in the IXEG side menu (which is what you should do)?

Please have a look here:

You second screenshot shows the marker.1 file still in place. Did you delete that also, as mentioned in the other topic?

Will it work in XP10 (without 11-excluisive features, of course)?

Thank you! So it's fine to first reduce torque by turning the knob. I never did it that way but will try it in the sim asap.

Perfekt, Danke!

Never tried it, but IIRC you can just enter new DEP/ARR ICAOs in the INIT page and this will at least reset all the flightplan related info.

I read in a 340B manual (that might explain the difference), that instead of truning off CTOT right away after takeoff and then adjusting torque with the PL to the desired climb setting, you would turn the CTOT knob to reduce the torque and then turn it off. Is this procedure also applicable to the 340A or did they change the logic for the B?

Sorry if this was already answered somewhere: Do you plan to keep XP10 compatibility, at least for the systems-related updates like better VNAV, holds etc.? I only fly XP11 if a plane wasn't designed to work in 10 (e.g. the JustFlight Arrow) as I don't care about that scary sci-fi technology like PBR, FMOD, VR or realtime reflections. I also have better performance in 10, but that might change when LR are implementing their VR optimizations.

Do you have flaps assigned to an axis? It might be that due to potentiometer noise or the axis not always reaching full deflection etc. the aircraft thinks you want to deploy flaps. If that's the case, try to assign flaps incr./decr. to buttons instead and see if it solves the problem.

I think your CWS deadzones in the IXEG menu are not set (or too narrow).

I guess also non-RNAV? I would do MCRRN5.HEC.LYNXX8 then.