Litjan

No problem - as far as I know there are no commercial aircraft that are capable (or even legal) to take off with the autopilot on...not even the A320! Here are the training videos: Enjoy, Jan

It is obvious that you have the autopilot engaged during takeoff - annd as designed it will try to do what it is told - and when you push TO/GA the lateral mode "HDG SEL" (heading select) will automatically engage. Now the autopilot will try to fly the heading you have dialed in - on your picture the heading bug is at 089, almost completely behind you. So this is not a bug, it is 100% user error. I advise you to watch some of the tutorial videos on how to fly the 737 - the autopilot is never engaged for take-off! Cheers, Jan

You need about 15 minutes for the IRS units to align - that is the limiting factor, timewise. The startup of the systems and engines can be done in less than 5 minutes. If you want to do everything realistically (checks, tests, including programming the FMS) you would need about 15 mins altogether. Cheers, Jan

No. I don´t feel that this is needed, the Saab 340´s engine management is a lot more complex. The 737 is very easy to start up. In general I really don´t see the need for an "auto start" sequence - if you don´t want to do it manually, select the "ready to fly option". What´s next, an "auto fly" option? Cheers, Jan

The IXEG´s usability is unchanged with the update to 11.30. So it is perfectly safe to upgrade to 11.30, just make sure to not use the "experimental flight model" checkbox. There will be no "emergency patch" to make it compatible (since there is no emergency ), but we will think about incorporating some of 11.30´s features in a future upgrade, notably the new particle effects. We haven´t decided yet how to deal with the new "experimental flight model" - I have to evaluate it first, but eventually it will probably become the new regular flight model and I want to be ready for that. Cheers, Jan

Increase the joystick deadband in the IXEG preferences menu - your joystick is sending a pitch signal to the autopilot, which will prevent engagement of the autopilot modes, just like in the real plane. Let me know if this helped! Cheers, Jan

Thanks for your work and expanding the usability of our 737, Tom! Cheers, Jan

Thank you for the nice words, Vitek! Happy flying, Jan

Relieved to hear that! Happy flying!

No solution known to me, sorry. Cheers, Jan

Yes, I have heard of this problem a few times. No specific reason it works for some people and not for others. Only workaround is to either run in windowed mode (there are some mods that allow frameless "windowed"), or use the left monitor as "main", afaik. Cheers, Jan

The picture in the gallery is from an alpha version where Nils used slightly different radios, I think. Unfortunately the release version has 25khz spacing, only. We will have to update that to make the 737 fully 8.33khz compatible. Cheers, Jan

Yes, we are very aware of the high sensitivity of these knobs and reducing that is high on the list of desired adjustments - not only for VR! Cheers, Jan

Ok, checked on my side and everything works as expected in 11.30rc2. Keep in mind that changing the aircraft state is only possible with the IXEG side-screen pop out menu "preflight" - not the X-Plane 11 airplane screen option "start flight with engines running". There is always a chance of some weird interaction when running with other plugins - so another troubleshooting step would be to disable those (XRaas, etc.) Let me know how it goes! Jan

Oh, don´t get me wrong - I LOVE being in France - just not flying there . Cheers, Jan

Good morning, Fropa... when glancing over your Log.txt while I munch my breakfast I noticed that X-Plane is complaining about not being able to save (write to) the B733_prefs.txt file. It says: The file could not be saved. Check that the directory still exists and is not flagged read-only. 0:06:32.464 E/SYS: | C:\Program Files/X-Plane 11/Aircraft/X-Aviation/IXEG 737 Classic/B733_prefs.txt 0:06:32.464 E/SYS: | The file may be flagged as read-only. 0:06:32.464 E/SYS: | Change the permission on the file so it's not read-only, or create the folder listed in the file path. This strikes me as odd - but COULD be the reason that there is trouble when you are trying to change the aircraft configuration. I will try myself now in rc2, there is always the chance that something got messed up with these betas... I will report back. Cheers, Jan

Welcome to the world of french aviation procedure design. I fly to major french airports in real life (Charles de Gaulle, Toulouse, Marseille, Nice, Orly) and what you describe is our everyday bread and butter. Or as an american pilot once asked on frequency: "You really want me to fly this shit?" Ultimately the french radar controllers know that the designers of these procedures are selfrighteous, proud french engineers that are detached from reality (like the people that built my airplane ) and usually just hand out directs to fixes or give radar vectors to make the system work... So do yourself a favour - don´t try to follow those procedures or you will grow grey hair (or loose it) and never arrive at your destination... Cheers, Jan

Weird - brakes work fine for me in 11.26 and 11.30... maybe icy runways? Hydraulics off? Brake failed (per failures)? Cheers, Jan

Thanks for the heads-up. I will try again on my side (also running b7)... Cheers, Jan

Turn off the option "show vertices" in the IXEG side-bar menu. Cheers, Jan

Hmm, if you are really running "vanilla" (no 3rd party except the IXEG) X-Plane 11.26 and still have that problem then I can´t give you any advice, either - except to doublecheck if you are really running without any 3rd party changes or plugins affecting your X-Plane installation. It is sometimes surprisingly hard to really remove or disable some artwork hacks. If that is not the case, then - since you are the only customer suffering this effect - it is probably in order to start thinking about a hardware malfunction or the like... Cheers, Jan

Yes.

Yes.

A good point - but one we have considered thoroughly! The real flight-controls in a Boeing (and any airliner) will only move so fast - the hydraulics can´t move them as fast as a pilot could throw around the control wheel/sidestick. In Boeing aircraft (at least the ones I flew) the flight-control inputs are connected proportionally to the flight-control surfaces. This means that you can only move the wheel as fast as the controls move. This is great, because the pilot always FEELS what the current displacement of the flight-controls is like - very important in windy/gusty situations where overcontrolling is a real threat. Airbus does it differently - here you can throw around the sidestick pretty much as fast as you want, with the flight-controls lagging behind (and the computer in normal law also messing with you). Thats why Airbus aircraft are (in my humble and personal opinion) a nightmare to fly in gusty crosswinds. Sorry, Tolouse. For the IXEG we have the same problem - the user can throw the joystick from side to side in 0.2 seconds, while the flight-controls take a lot longer. So we had a choice to make - but if we made the flight-controls stay in sync with the joystick (which leads to better control), we would have had unrealistic roll (and pitch) rates - which is a no-go! So until we all get force-feedback hardware inputs, it´s just something we have to live with. But rest assured that the plane rolls as quick as in real life. Cheers, Jan

Hehe, cool story! You have to be careful with the units when you go to places where they are still confused about the correct units to use for weights, distances etc (like the U.S.) . But normally the FMS and airplane gauges are set to use one unit only, the only problem could be when telling the fueltruck guy that you want 8000kgs and he doesn´t listen (or know what kg´s are...) and fuels 8000lbs, only. But then rule #1 applies, and those 8000lbs would show as 3600kgs in your fuel gauges. By the way, the conversion factor is 2.2 - so 2.2lbs are 1 kg. There was a spaceship lost because the braniacs at NASA confused some units once, iirc. Cheers, Jan