Litjan

Huh, never noticed those - thanks for pointing them out! We will doublecheck and fix!

Correct.

They already decrease at a realistic level. And when you sleep, the mechanics refill the fluids as per aircraft maintenance manual.

Can you try to run without "Zink" enabled?

We have had a report like this before...but were unable to resolve the issue for that customer. For what it is worth, the plan is to modify all sounds to use FMOD only, right now we still use OpenAL, but there may be some hardware configurations out there that have problems with it: https://forums.x-pilot.com/forums/topic/27322-distorted-sounds-151/

You could open the .acf file in planemaker and change the specific fuel consumption to a very low value to extend the range.

Try to run with Zink disabled (not checked)?

Not from our side, I am afraid. Maybe you can write to Navigraph and ask them if they have a legacy database?

The 737-300 is an older model of the 737 that does not have dedicated nav radios for the ILS. On modern aircraft, there are often 2 VOR receivers and in addition several ILS receivers...not so on the 737 Classic. You need to tune the on-side nav radio to the ILS frequency AND be in the valid reception range and area for the GS (or LOC) to work on your side. Just setting the ILS approach on the FMS does nothing to the radios. The GS works fine, also in MAP, CTR MAP and even PLAN mode.

Haven´t heard this one before, but here are some things to try: Try with a default aircraft, like the 737-800. Does the problem persist? Do you have aircraft malfunctions enabled in X-Plane? They can randomly fail all sorts of things, among them both nav receivers and transmitters. Do you have other third-party aircraft or plug-ins installed? Especially things like flywithlua can cause all sorts of weird behavior, just by being installed. Does this happen at ALL ILS installations or is there a specific one you are trying to use? Which one, if so? Does this happen on BOTH nav receivers (left and right)? Cheers, Jan

Hi Luiz, Yes, the PROG page is not working correctly. We try to be upfront as much as possible about things that are not done (yet) and posted them in this thread, so that prospective buyers can form a picture about the state of the aircraft before making the purchase: https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v15/ While modern pilots (and especially layman simulator users) do rely heavily on the FMS to do the necessary aviation calculations for them, it IS entirely possible to do all of them in a conventional way. If you want to know your ETA at a certain point, just use the formula velocity = distance / time. Solve for time: time = distance/velocity. Insert distance (NM) and average groundspeed (KTS) and you will get the time in hours. Multiply by 60 and you get the estimated time enroute in minutes. Add those to your current time and you have the ETA. Cheers, Jan

In the X-Plane GUI you can filter for the word IXEG to show you all of the custom commands.

It could well be that the autopilot of the real 737-300 has some additional gain parameters that limit certain pitch rates in certain speed regimes or something like that. I just want to be honest with you to let you know that we are probably not going to spend considerable time implementing and testing such further parameters to a custom autopilot that already works much better than the default X-Plane autopilot (in my opinion) - especially given the fairly small discrepancy from real behavior which also can be mitigated with an easy selection of alternate modes or reverting to a continuous speed (vs Mach) descent, if so desired.

Thanks for the report and the flight plan - we are very aware of VNAV not being all that it could be, especially for the descent path calculation. We are trying to be as open about this fact as possible and it is mentioned in detail and clarity in the "things that will not be in version 1.5.2" forum thread. I would however like to know your weight and CG when you got the "unable crz altitude" message and what charts you used to calculate that indeed you should be able to reach that cruising altitude? This is not on my list of issues, so I am wary of there being another bug. Thanks again, Jan

Glad to get this sorted and very much appreciate the kind words, it means a lot to me coming from someone who got his hands dirty on the real aircraft!

Happy to get it sorted - weird, though. The only "other" way to trigger the fluorescent light is to turn on the emergency panel lighting by disconnecting all AC sources during flight (standby power takes over). This will trigger the tube to turn on...but I see that the instruments are powered in a normal way in your first screenshot, so that can´t be it.

Have you tried the "Background" light rheostat yet?

Yeah, you might try that, although you will find that any questions about the IXEG are frowned upon on the .org - as it is a product from a competing store. So don´t be surprised to get some hostility or your post deleted. I have no idea what could be causing your problem, the product should work fine on Mac... and I would really like to see a video of the problem. I am uncertain of how well you know the correct procedures for the 737 and there could be half a dozen (user error) reasons why the engines won´t light up.

Hi, very strange, have not heard of this problem before. I looked at your log.txt and could not spot anything unusual, the one advice I would give to try and isolate this problem would be to remove (temporarily) this plugin: Loaded: /Users/chrisn/Desktop/X-Plane 12/Resources/plugins/AFC_Bridge/mac_x64/AFC_Bridge.xpl (aerosoft.bridge). [XPPython3] Starting... Logging to XPPython3Log.txt 0:00:00.000 [XPPython3 Updater] +++++ XPPython3 Updater v3.1.4 - for Python 3.10 +++++ 0:00:00.000 [XPPython3 Updater] Python version is 3.10.7 / OpenSSL is OpenSSL 1.1.1q 5 Jul 2022 [XP3: XPPython3.I_PI_Updater] >>>>> A new version is available: v.3.1.4 - for Python 3.10 -> v.4.4.1. [XP3: XPPython3.I_PI_Updater] >>>>> To upgrade: See documentation Loaded: /Users/chrisn/Desktop/X-Plane 12/Resources/plugins/XPPython3/mac_x64/XPPython3.xpl (xppython3.main). and also Marginal´s ground traffic plugin - I think this is outdated by now and not even sure it is compatible with X-Plane 12 anymore. Let me know how that goes?

What I believe happens is that people engage the LVL change while in MACH mode. This will make the speed control chase the set Mach number, and since the indicated speed rises rapidly for the same mach number in a descent (as temperature gets warmer and the speed of sound increases as a consequence), the plane will pitch down rapidly to achieve the necessary acceleration. If you disregard the automatic reversion to indicated speed (by setting the MACH mode again after it reverts to SPEED in the descent, for example), you can actually overspeed the aircraft easily, as at some point the set Mach number will exceed the VMO of the aircraft. Descent speeds in excess of 5000 feet per minute in LVL CHG while in Mach mode is something I have observed regularly in the real aircraft, especially when paired with a decrease in headwind in the descent. PS: Many pilots did not use FL CHG for the initial part of the descent for this very reason, rather using V/S to initiate a shallow(er) descent until the speed reference could be switched over to IAS and the FL CHG would work more stable.

I will let you know when I get home on Monday, I am still on the road. I just reread your initial post and it seems odd that those commands are now missing when we had them before, that does not sound right. Hang tight!

You can use the default X-Plane commands for that.