Litjan

@trisho0 Hi and welcome to the IXEG 737! This post may answer a few of your questions as a new user: Let us know if there is anything else we can help you with. Cheers, Jan

I have tried to replicate this problem - but was not successfull. For me this works as expected (no error). Since you are the only one reporting this so far, there is the chance that you do something very unique to trigger this error, I doubt that it is interference from another plugin (although flywithlua and volanta are known to cause problems sometimes). If we can not get to the bottom of this, one solution would be to trigger the "reboot gizmo" function (right-side pop-out menu, the small "flash" symbol) to reset the logic for the second and subsequent flight... Cheers, Jan

Thanks for confirming that - I will replicate this tomorrow and give Tom detailed reproduction steps.

I REALLY don´t want this thread to devolve into the same old same old "my sim is better than your sim" discussion. We X-Plane people don´t care how many copies MSFS sells (maybe a little bit, the more the better since it introduces people to the flightsim genre that might try X-Plane as well later on), we only care about how many copies we sell and if those are enough to cover our cost and make us enough money to keep doing this. We could make a LOT more money coding some farm game where you can raise pigs or plant barley, but we like making airplanes better.

You still have a bunch of (potentially conflicting) plugins running in your installation - I am especially wary of the terrain radar plugin and the marginal ground traffic plugin. ActiveSky and XPilot are also non-default plugins, they should work but you must make sure that you have the latest, XP12 compatible versions. Last but not least - it could be that running Zink might cause problems with the OpenGL rendering functions we use, so it might be good to disable Zink, just to test this theory.

Hmm, but then people would complain that "in the real plane the switch pops back to neutral the second you let it go" I think that is just one limitation we have to live with. If you don´t trust the cutout switch, you can trigger a fire via the failure menu, use the cutout switch to silence the bell, and once you have established that it works, extinguish the fire by "fixing all faults" and then commence with the cockpit preparation . Hmm, maybe we can assign a command to the switch so you can use a key or button to "hold" the test switch?

Right - getting to the core of these bugs is super time-intensive...but maybe if you fly the same routing again and the plane looses the track over IKEKA again, let me know. Cheers, Jan

Hello Pavel, currently there is no option to show the displays in separate windows, but there may be in the future. One way to make the appear larger is to get a larger monitor and sit closer to it, that is what I do. We won´t do the loading and fueling in the FMS, but there will be a new and improved GUI that will allow loading and fueling the plane to your heart´s content - I am working on that with Tom at the moment. Cheers, Jan

Huh, that is the first time I see that reported... this used to be a problem on the default GPS units in X-Plane until Philipp fixed this recently, if the leg distance was over 60NM or so, the plane would veer offtrack in direct-to mode. But haven´t seen this (or heard about it) in relation to our 737. You do have a vast assortment of potentially conflicting plugins in your installation and unless I get more reports about this happening on our 737 I would have to ask you to run the IXEG in a "vanilla X-Plane installation" to rule out interference, just to test this. If you have a "surefire" way to trigger this misbehavior (like a route that ALWAYS does that at a certain point), please let me know and I will verify it on my end.

I will look at the sim later on today to see this, I can´t really tell from the pictures, I think the forum compression kills the necessary resolution. I am not sure if we draw the shadow ourselves or if they are drawn by X-Plane, possibly via ambient occlusion.

You are correct, we have not changed that logic yet.

Hello Ahmed, I think Pils is correct, it seems to be a problem on your computer that does not run Visual Basic correct - maybe a problem with your Windows installation. This is the first time I heard this being reported, if it really was a problem on Gizmo´s side or with the 737, more people would have complained about it. If you file a support ticket with X-Aviation, the staff there may have a better idea what you could do to fix it, we are no computer experts here . All the best, Jan

Maybe this is a good chance to upgrade to XP12?

The Classic Plus aircraft is exclusively for X-Plane 12, it does not work in X-Plane 11. You have to contact X-Aviation customer support, maybe there is the possibility to get the version for X-Plane 11, but I do not see it on the main store page anymore. The Saab340 should work in X-Plane 11, as far as I know - I would say you did not install it correctly, because otherwise it would show in your aircraft selection interface in X-Plane. Greetings, Jan

I think it is a good idea to once in a while take stock of one´s add-ons and plugins and to ask yourself "what do I really still need in there?". And after clearing out the unnecessary stuff, go over the remaining ones and make sure they are updated and listed as compatible with the version of X-Plane that one uses. Too many users simply "copied over" whatever they had in XP11 and then are totally surprised that things don´t work they way they used to. Cheers, Jan

You have many plugins, some of them notoriously prone to cause problems. (Like SAM, for example). You need to remove (not only disable) all plugins except for Gizmo and the default X-Plane plugins, then try again. If that works, start adding your other plugins until you find the one that is causing the crash. Cheers, Jan

Next - first real flight one - video is up:

The "cabin ready" is something that the flight-attendants notify you verbally about. We have decided to NOT add any of the automatic callouts that co-pilots or flight-attendants do, as opposed to other dev teams, because the procedures and wordings vary too wildly and instead of people being happy, it would trigger an avalanche of people requesting to do it this way or that way, because when they flew as kids in the 60´s they alwas used to hear "fasten your harness", but now they say "seatbelts" and how on earth can they expected to enjoy the 737 with such a glaring discrepancy...

These are indications of electrical connections behind the panel - if a section of light on a panel does not work, sometimes pushing on the + will make the lighing go on, then the technicians know that the connection is faulty (so I was told).

Didn´t NASA loose a space probe or something because of exactly this sh*t?

Hi everyone - I am going to start doing some videos again - starting out with one that explains how to set up the IXEG 737 in X-Plane 12. I will add various flights in my channel in the next days and weeks, talking about how to fly the 737, developments at IXEG and X-Plane in general, not really tutorials, but hopefully something a bit more fun to watch. Stay tuned!

Yes, you need to use the IXEG PREFERENCES menu - it can be invoked by popping your mouse against the left side of the screen. There is also the ability to switch the X-PLANE units in the weight and balance GUI (that you invoke by using the top bar of your screen). Here are two screenshots, the first one shows you the PREFERENCES menu and the side-bar popout, the second shows you an alternative way to get to the PREFERENCES menu by using the top bar (in case you have disabled your side-bar pop out).

Look at the fuel gauges - they say KG!!!! You are on metric system. You can change that on the PREFERENCES menu. The values you put in are in LBS, but if you convert them to KG´s that is just too high a weight, it is out of bounds of what the FMC will accept. What is confusing me is that I gave the EXACT solution to your problem above in the post I wrote on Monday. Did you not read it?