Litjan

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?

Yes, I think this is working as it should.

Yes, that is correct - when you change the sounds using the IXEG´s preference panel, you are effectively changing the sound level of X-Plane itself. I think that is normal, though, there are no separate sound settings for individual aircraft in X-Plane, to my knowledge. You can´t fly the R22 helicopter and turn down the cockpit sounds and then open the Cessna 172 and expect the cockpit sounds to be at normal level again. The sound settings are global. When a custom aircraft uses it´s own sound engine (like we do with OpenAL), strange things can happen and I would not expect seamless switching between aircraft in one session, it is always good to reboot the simulator when changing between those aircraft. Cheers, Jan

I can´t really say definitely how these things worked on the Classic, it has been 11 years since I flew one... there have been a few changes going to the NG, though - and there are also software differences in FMC versions. I will see if I can find out more, maybe looking at some videos I made back then, but we didn´t do many non-precision approaches.

Oh, and I just checked - the "drum" on the standby altimeter for the "hundreds" of feet does not turn on the real 737, either:

I believe this is all correct. There is no info shown for non-precision approaches on the APPROACH page, only frequency for the ILS, if there is one. Even when not selecting the ILS approach. To delete the flightplan, enter a new ICAO into the ORIG field, even if it is the same one, it will delete the flightplan. If you select a TO derate, that is still considered "full takeoff power" - the engine is just rated at a lower thrust setting, but if you set 100% of that (lower) rating, that is still "full takeoff power" (TO). If you use the TASS function, you get a reduced takeoff power (R-TO).

Ah, I see the 100 drum not rolling...that is probably a bug and will be fixed! Here is a short video I took in my 747-400 just a few days ago: https://www.dropbox.com/scl/fi/sg081mflco67y1zadvarl/Standby-altimeter.mp4?rlkey=sjmttubm79cv793t4i1mhexuo&dl=0

The right one is the standby altimeter, it is inherently inaccurate - on the 747 I fly now it is often "wrong" in excess of 300 feet.

Your bug has been logged and we are going to look into it.

Tom explained it in the recent video he did with Q8pilot - he had to make a decision whether to continue developing the 737 or going down another road in his life to make money. And he needs to eat now, he can´t go hungry for a few months with people on the fence waiting if they want to maybe update or not ("I want to wait until they put in the holds..."). That is why we nudge people to pay the money now.

Hmm, could not look at the video (it is set to private), but theoretically an unlucky combination of plugins, especially highly invasive ones like XPUIPC or FlyWithLua can theoretically cause all sorts of weirdness. Although they normally should not ;-)

There are plans to move to FMOD in the future. I realize that you are not happy with my answer and would have preferred a solution, but I honestly ask you: What do you think this solution should be? Your problem is super isolated, I have not heard of anyone complaining about "distorted sounds" in 8 years of selling our product, feel free to search these forums for similar reports, I believe you will come up empty. Once in a while a user for any software will come up with some hardware/software/OS combination that does not work, and there is nothing you can do. So while I would like to offer you a reasonable solution, I honestly do not know how.

Thanks for the screenshot and the log.txt. Ben is right, the error can be found in the log.txt - this will help in finding and fixing the problem. Greetings to Brazil, I fly to SBGR once in a while, but I would imagine that the classic 737´s hang out in Viracopos? Bom dia, Jan

Huh, I think this must be something obvious...what number are you trying to enter? Into which field? I think a short video would go a long way in clearing this up. Have you watched some of the tutorial videos available?

Hmm, maybe I can talk Tom into adding the function that when you press the button again...the menu closes again. Would that help?

Thanks for the report! I will try to recreate this so we can find and fix it - do you happen to have a screenshot of the error message or the GizmoLog.txt file? Thanks, Jan

That sounds (haha) very plausible. I am not much of a hardware (or software) guru, so I can only guess as to what might be the core of the problem here . Maybe someone reading here with a more profound understanding of the issue can chime in here. Sorry that I could not provide a ready solution, I hope that you will find one! Cheers, Jan