Litjan

You are putting in a zero fuel weight of 63+ tons - that is way more than the maximum allowable weight. Change the weight to be within limits and try again. Cheers, Jan

There is one more important thing to know about "crossfeeding": If you open the crossfeed but have BOTH sides pumps on, fuel will not get evenly burned from both tanks. You would think so - and inititally this was also how the big, official "Level D" simulators that we used for training had it. But they found out in the real aircraft that - since pressures are never EXACTLY the same, the "stronger" side will COMPLETELY "take over". So you yould see that fuel only gets used from one tank, even if all pumps are on and the crossfeed is open. So just like mmerelles said: If you have an imbalance, open crossfeed, turn off the pumps in the tank with less fuel. We used to say "less fuel, less pressure" to memorize this. THEN you need to set a reminder (I used to clip the tip of my tie to the card-holder clip on the yoke! ) because its easy to get distracted and then you suddently have reversed your imbalance. We used to call this "fuel yo-yo" . Cheers, Jan

Interesting, haven´t seen that... At any rate, the PROG page is not yet fully working and 100% error-free...as you have just found out . I am hopeful to get it fixed up (together with VNAV, HOLDs, etc) in the future. Cheers, Jan

Hi Petter, I can unfortunately not give hands-on training to operate the 737 here or on Skype, due to real-life time constraints. Sorry, Jan

Hi widero, The short answer is that you may be running an AIRAC cycle as your FMS database (like the one we include when you buy the plane) that is not current. You would need to download a current one (from Navigraph or Aersosoft) and load it into X-Plane (they provide an installer) and then you should be able to see the SID. May I ask which airport, and which SID you are trying to load? Cheers, Jan

Wow, Nick, that is totally awesome! Now my good old Bobby gets a new lease on life at Lufthansa - just like it should have in real life, too . Thanks so much for making this livery! Cheers, Jan

Hmm, how about the "new" Lufthansa livery?

Hi Nick, the update process will never delete anything you made yourself or downloaded. It will only "overwrite" the files it considers X-Plane´s own, native files. But even if you have changed those, it will always ask you if you want it to overwrite those. To access betas (like the current 11.33b1) you have to manually run the installer file and check the box for "betas". Cheers, Jan

Wow, incredible! Nice work!

It is the "show vortices" option. You must deselect it, we will remove it in the next patch. It doesn´t work with XP11 anymore. Cheers, Jan

Hi Ralf, so far this is the only report we received about a combination of a certain scenery and our IXEG causing a crash. The best place to find a solution would be in filing a bug report with Laminar Research, if the whole simulator crashes! If the simulator crashes reproducibly and ALWAYS then I am sure they would love to hear about that! Also check the latest beta of X-Plane (11.33b1) as they have fixed some crash reasons, I heard. https://developer.x-plane.com/2019/04/x-plane-11-33b1-out-now/ Let me know how that goes! Cheers, Jan

Thanks Ben for reporting back on that! I knew Windows Defender would cause some problems while entering a modified route into the FMS...but your problem was new! Thanks for sharing, Jan

Now I have learned to normally stay out of these "authorization" things. But whatever possible reason could someone have to type in FREEZE when presented with the warning that this action will lock his computer forever...if he actually intends to use this computer in the future? The only possibility to undo this action is to get a new copy of the IXEG, as far as I know. Or a new computer. You still have the right to use three machines, just not the ones you locked yourself when facing a very clear and concise warning to not do this if you want to fly the IXEG on it... Cheers, Jan

The one thing I could imagine is that you have no hydraulic pressure for using the brakes. Other than that our brakes are "default X-Plane" and should work just as well as in other aircraft. Cheers, Jan

Like Tony said - the VNAV logic can NEVER fly across the altitude set in the MCP - it is like a safety barrier. The VNAV logic can also not fly in the "opposite" direction, i.e. it can´t climb if the MCP altitude is "lower" than the current altitude, and it can´t descend if the MCP altitude is higher. So you have to assist the VNAV logic by setting your MCP altitude correctly. Cheers, Jan

Hey Nick, Nah, I won´t delete it - some valuable info in here that someone else might find useful. Plus - if you have any other questions - feel free to post! Cheers, Jan

Hi Nick, welcome and thanks for the nice words. We had to switch styles for some instruments during development - mostly because I was able to provide detailed shots for the type we had installed in the aircraft I flew. So yeah, some of those "early WIP" shots aren´t representative of the final, current product. At this point it is also not likely that we will spend the time to develop different variants for things like radios or transponder panels, to be honest. I hope that you will get used to those that we have! Happy landings, Jan

Not sure what you are talking about, do you have a pic or so? Thanks, Jan

Hi TH, it is normal for the real plane in VNAV PTH to not adhere perfectly to the "set" speed - the plane will calculate a fixed geometric path in the sky that it "believes" it can fly with idle power at the calculated descent speed. But more often than not some external influences (wind, mostly) will not allow the speed. The plane will prefer to stay exactly on the calculated path and lets the speed go up or down. If this is excessive, it will nag you "drag required". If the speed gets too slow, it will activate the autothrottle and add thrust to regain speed. But there is a "window" in which speed may vary without any action at all Our plane does not model a "smooth" intercept of the VNAV PTH at the top of descent (yet). So it will initially get a big high, then tries to catch up by descending fast to the pre-calculated path. For now there is not much you can do to avoid that, except manually starting your descent a bit prior to the T/D in V/S mode, then, once on the path, enable VNAV PTH descent. Cheers, Jan

Hmm, no idea, then - something unique to your setup. I think we would have received more reports on this if it was a genuine problem with the IXEG. Works fine on my system, too... Try to remove your plugins (better pushback and xenviro) to test if they influence this... Sorry I can´t be of more help, Jan

Hi Ben, really weird. The defaults are shift-2 for flyby, shift-3 for nearest runway, shift-4 for chase view, shift-5 for tower,...and so on! They don´t work for you for default planes, either? Some ideas... Do you have the SHIFT-LOCK key activated, accidentially? Do you have a third-party plugin running that may interfere (fly with lua, easyview, etc)? Did you change the key assignments in a custom key-binding profile? Cheers, Jan

Hi Ben, I am not aware of the Shift-8 view mode - the regular external view mode is shift-4. Can you try that? Cheers, Jan

Yes, I think this was only on an experimental, internal version. Cheers, Jan

No worries, Michael! I know it can be overwhelming to have a "real" 737 under your seat of the pants... I still remember the day I sat in the real one for the first time (March 92, Paphos, Cyprus) and even though I was type rated, had been in the LevelD for many hours and was "just" going to do some touch-and-goes to get my landing training in...I was really almost overwhelmed ;-) Keep learning and - most importantly - have fun while you do it! Cheers, Jan

And that is the way we model it, too. The "suggested" (QRH) Vref values on the approach page change with calculated weight, but once you "hardcopy" them into the MCDU they stay the same. Cheers, Jan