Litjan

Hi! Yes, I have that tracked as a bug - and we hope to eventually add that functionality as well! Sorry for the inconvenience! For now please lean over and use the Captains CDU to do it. Happy landings, Jan

Not yet. You can easily make the necessary change in the .acf file yourself, it is not encrypted or anything. Just open it in planemaker, go to "Standard" then "Author" then click the checkbox for "Always Use Experimental Flight Model" - save and exit. Cheers, Jan

You only need to install the Navigraph data for the IXEG 737 correctly and it should work. There is nothing else to it. Maybe try to run the installer that comes with Navigraph data again, paying close attention to the options? I think you need to pick the correct data format and also the correct installation path. Which specific procedure is missing? You say a lot of them...that sounds like something went wrong with the installation, I think. Cheers, Jan

I can´t aid in answering why Gizmo needs to be a "global" plugin (i.e. it always loads), iirc there was a technical/security reason for it - but I think you can disable it in the plugins admin menu (before you start the other aircraft)? See if that helps?

Let me know about everything else you find - texture/blender fixes are fairly quick to do!

Yep, I see the same thing! The texture is present when viewed from "above", but transparent when viewed from below! Certainly something to adjust for the next version, thanks for pointing it out! Cheers, Jan

Interesting! (And thanks for the kind words, disidd). The move to the next version of X-Plane will likely feature the move to FMOD as well - which will probably take care of these peculiarities. I can not switch my sound device when using X-Plane for any aircraft, not only the IXEG - and that is a known bug, afaik. So if I start out on my monitor´s speakers but then decide to don my bluetooth headset, I need to shut down X-Plane, switch default sound to bluetooth, then launch X-Plane again. Cheers, Jan

Hi! Yes, I think quite a few folks still fly the IXEG . I think it is unusual that your sound problem only occurs with the IXEG 737, we are creating a custom sound experience with OpenAL, but this should not affect the sound stopping on your bluetooth receiver - that should be a Windows issue, I believe. I do have certain sound problems with my bluetooth headset as well (like when I move out of range and then back to my computer or when the battery charge gets low), but that is not isolated to a certain game or application... Cheers, Jan

Normally the fuel usage is very close to the flight plan - the variation due to wind changes is probably less than 5%. The major part of uncertainty is the actual flight path you will take, especially deviating around weather and delays (vectoring, holding) at the arrival airport. I will rarely take off with less than 15 minutes of extra fuel (which goes beyond the legally required reserves). It IS legal to use your alternate fuel to hold a bit longer at your destination airport...if the chance to land there is just as good (or better) than the chance to land at your alternate airport. The one big NO NO you want to avoid at all cost is having no "safe haven" that you can reach and land there with at least 30 minutes of fuel remaining. A good pilot will rather land at an intermediate airport to take on more fuel than to press on to a marginal destination with a marginal alternate.

Alright, glad you got it going again! Cheers, Jan

1.) Yes 2.) Declare emergency, land at nearest suitable airport

Yes, the second X-Aviation folder is normal, it holds uninstall information... Often the "unsupported path" is due to a typo like a missing "space" like: here between the X-Plane and the 11 (X-Plane11 instead of X-Plane 11). But the screenshot you shared shows the correct writing...

Hi James, your filepath looks legit! Some ideas: Do you have an unusual operating system language maybe? Did you install the version you are trying to activate into another (wrongly spelled) path (so you would have two instances of the plane)? Cheers, Jan

Hi Leviathan, thanks for getting back to us on this one and sharing your findings... These mods are often quite invasive - maybe more so than the original modders intended them to be! Happy landings, Jan

Yes, very puzzling! Does it also happen if you stop somewhere else (like in the middle of a taxiway)? I guess one other thing to try would be to disable all other plugins that may be interfering - especially SAM, flywithlua, ground handling, etc. You never know if they might interact in some weird way, so it would be wise to test that just to preclude this. Another thing is icing (of the ground), but this should affect you everywhere, not only near the gate. Cheers, Jan

Hi andrew, this is strange - especially since they initially seem to work! One reason I could think of is that you have not turned on the hydraulic pumps for system A and simply run out of brake-accumulator pressure after using the brakes a few times. Make sure all yellow lights are out on the overhead panel when you operate the aircraft, that should take care of this possibilitiy. To further troubleshoot you can always display the DATA OUTPUT datarefs (green numbers) on screen, look in the corresponding X-Plane menu with the keyword "brakes". That way you can see how much brake force is applied. Let me know if this helps? Cheers, Jan

Hi sthenion, you need to select your "startup state" in the IXEG preferences menu (bump mouse on left side of screen to get it). The normal X-Plane startup preference "start with engines running" is not effective with the IXEG 737. It sounds as if you have the "turnaround" option selected. Cheers, Jan

According to regulations you have to perform a lineup within a short margin, spool up engines to 40% before brake release, then release brakes and press TO/GA. Calculated take-off thrust has to be achieved before 60kts groundspeed to conform with calculation. A "static takeoff" (with brakes held and full thrust) is not recommended, because of undue stress on landing gear, danger of foreign object ingestion and danger of starting to slip (especially on wet/contaminated surfaces). Cheers, Jan

In general, airline pilots like to fly as fast as possible and as high as possible. They former saves time, the latter saves fuel - both is money . So speed wise we like to fly at ECON speed as long as possible (or close to VMO if late on schedule). However there is often a speed limit below 10.000 feet (250kts) and also collision avoidance and birdstrike hazard is an issue, so I refrain from flying faster than 250 when lower than 8000 feet AGL, even if the airspace structure allows it. Most of the time ATC will slow you down as you get closer to the airfield, often to 220. If unencumbered by any of the above I will slow down "just in time" before descending on the glideslope (10NM, 3000AGL, 180kts with Flaps 5). My rule of thumb is "almost 1 NM per 10 kts deceleration" - so if I come in at 250kts I will start the deceleration at "almost" 7 NM prior to that. The lighter you are, the faster you will decelerate...so with a light aircraft 5NM will be enough, with a heavy one 6.5. Also consider head/tailwind component. Cheers, Jan

Happy to hear that the descent calculator works out for you! And once you used it a few times you will have memorized the altitude/distance relation and work the problem in your head...like most line pilots do, too. (We cheat and use the metric altimeter - 33.000 feet = 10.000m => 100NM)

It gets used in climbs and cruise - and it can be of limited use in descents, especially calculating the optimum T/D for the first restriction (Cross XXX at or below xxxx feet) - but it is very rare that you can really fly the planned path all the way to the intermediate approach fix (it can happen in "progressive" countries with little air traffic like Sweden or Norway).

I stopped flying the Classics in 2012 and transferred to the Airbus 320 family - surprisingly the use of the managed descent mode (DES) on the A320 is even less than we used VNAV PTH on the 737... Nowadays the ATC structure changes a bit towards STARS and SIDS that have more restrictions - ATC hopes to lessen workload because the planes will move inside a "virtual tunnel", separating from each other by virtue of altitude restrictions. A famous arrival here in Germany was the EMPAX3W STAR to EDDF, but it did not go beyond the trial phase because pilots failed to meet the restrictions too many times (unfamiliar with how to properly fly managed descents, erroneous behaviour of the FMS,...). Cheers, Jan

Have you watched this episode? I show how to use the "descent calculator" that I made for the avitab plugin - it basically does for you what airline pilots do in their head all the time when planning and executing an approach: Estimate total distance remaining to the airport - then calculating the altitude one should be at for an idle power approach: https://www.youtube.com/watch?v=hSemWBgRNnE Cheers, Jan

Hi, VNAV descents are considered to be WIP. They work somewhat, the more simple the descent path, the better. Add multiple and/or complex restrictions and things will start going south. We fully intend to improve this in an update - for what its worth I can safely say that the VNAV PTH descent mode was rarely used in the real 737 Classics and most pilots used FL CHG or V/S to perform their descent. The example you describe (not flying the correct speed) is a very typical thing that happens in the real airplane, too. The VNAV path is preplanned with a lot of assumptions, and sometimes those don´t work out (different wind, for example). The aircraft will try to adhere to the PATH more than to the speed it planned with - and when I used (rarely) the VNAV PTH function in the real aircraft I often had to "help" the plane by using the speedbrake. If speed becomes excessive, VNAV will disconnect and then the pilot has to pick up the shards of the shattered approach ;-) Cheers, Jan

I don´t exactly recall the problem PilotTris had, but I believe it involved another account being active on his computer previously. There could be some legitimate reasons for it, like if you bought the computer from someone who had a X-Aviation account registered to that machine. The only solution is to submit a single request for support on the official X-Aviation support line with a true, honest and precise account why there was another account associated with your computer previously. Cheers, Jan