Litjan

I just doublechecked, indeed the light in the forward entry area does NOT turn off when the cockpit door closes and the camera is in the cockpit area - I will talk to Tom and see if we want to implement this (again). Thanks for the headsup, @manguras!

Hmm, I thought that we automatically "turned off" the cabin lights when the cockpit door is closed to avoid this effect (which - Cameron is right - can not be controlled otherwise by aircraft designers as X-Plane does not calculate shadowing by aircraft parts). I will have to check later today...

If the cockpit appears "dead" AND you can see the pilots, even while sitting in the cockpit, that means that your Gizmo plugin is not working correctly or did not validate your license correctly. This is the relevant part of your log.txt file: dlerror:dlopen(/Users/louislepage/X-Plane 12/Resources/plugins/Gizmo64.plugin/mac_x64/Gizmo64.plugin.xpl, 0x0006): tried: '/Users/louislepage/X-Plane 12/Resources/plugins/Gizmo64.plugin/mac_x64/Gizmo64.plugin.xpl' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/Users/louislepage/X-Plane 12/Resources/plugins/Gizmo64.plugin/mac_x64/Gizmo64.plugin.xpl' (no such file), '/Users/louislepage/X-Plane 12/Resources/plugins/Gizmo64.plugin/mac_x64/Gizmo64.plugin.xpl' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')) I don´t know anything about Mac computers (only that they are bad for playing X-Plane), but this seems to be the problem. Maybe something is incompatible... If you can´t figure it out (or someone here like @Cameron can shed some insight), you will have to go and file a support ticket with X-Aviation. This thread may be of interest (it says that Gizmo can not work with ARM, if I understand it correctly) https://forums.x-pilot.com/forums/topic/27542-ixeg-is-not-usable-in-apple-silicon-with-latest-gizmo-avionics/Cheers, Jan

Hello alireza, Please read the list of things that do not (yet) work correctly - as displayed prominently in our support forum here: https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v15/ You will see that VNAV during descent is not considered reliable in all cases and you as the pilot are responsible - just like in a real aircraft - to make sure that you follow your planned vertical profile and revert to other autopilot modes (like V/S or FL CHG) to ensure adhering to it. The ILS localizer alignments in X-Plane are in general more and more accurate these days. If you tell me which airports and runways you experience misalignments, I can investigate what the problem may be. Cheers, Jan

The IXEG 737 is provided for X-Plane 12 only. It will not run on XP 10 or XP 11.

In a way that is very true! There was a famous accident with a Hapag-Lloyd Airbus A310 in 2000, they took off and wanted to fly to Hannover, but the landing gear did not retract. They looked at the FMS and it said that they could make it all the way easily...but the pilots did not know that the FMS did not calculate with the additional drag of the gear being down. The pilots failed to do the basic "fuel flow x estimated flight time = fuel needed" calculation, instead relying on the FMS...and made a flame-out landing in Vienna because of fuel starvation.

Thanks for the kind words! Yes, 1.5 is the current version for XP12. We are planning to updated the aircraft further in the future and are very aware of it´s current shortcomings, especially in the FMS department. Unfortunately we can not provide a realistic timeline as to when the next update will drop, we have a history of lengthy dormant phases and then stretches of working hard on the aircraft - both Tom and me do this as a side project in our lives in addition to our "real" jobs and family, so don´t expect the same cadence of updates that you would get from a dev team that does this "full time". As you said, the plane can be flown safely, realistically and (I think) with having a lot of fun with it - I flew the real aircraft for 10 years and regularly fly our model in it´s 1.5 status and still enjoy that immensely...despite the shortcomings. I know this may sound apologetic, but real pilots (at least the older ones) still pride themselves in their ability to calculate and execute descent planning better than the FMS can . Cheers, Jan

V2 should be in the 120-150 range...not 437. The maximum allowable speed you can set on the MCP is 340.

Hmm, is this only happening on a certain path (i.e. the same airport and SID) or does it happen a lot and in various scenarios? If you could provide reconstruction steps and a log.txt, that would be helpful to find out what the bug is - because it is clearly that, not user error. The speed window should never show these out-of-bounds values, no matter what the pilot does. Thanks, Jan

Hi Seahawk, as stated here (check the last bullet point for FMS): https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v15/ the VNAV calculations during the descent part of the flight may be erroneous, especially if restrictions are part of the path coding. Entering restrictions manually is further increasing the chances of things going wrong. For now we recommend calculating descent paths manually, there is also a "descent path helper table" available in the documentation that you can refer to. The landing elevation on the overhead panel is used to set up the pressurization system - it has nothing to do with autoland or the autopilot Chances are that you used a wrong approach speed, the wind was unusual or your center of gravity was out of limits - however it is pretty normal for the 737 to not do a very smooth touchdown when using autoland. Happy landings!

Interesting! ...and hard to reproduce, of course - with your report being the only one for this so far (after many many years and many many users ;-)). If this happens repeatedly, you can "reboot gizmo" while on the ground, that should really clear all variables and reset the plane as if you just booted X-Plane. Cheers, Jan

If you log in to the forums and there is not a post about the update, it means exactly that.

Hi Jarret, That looks cool! I think posting the .acf file here should not be a problem - the aircraft does not run without the other files and the DRM, so there is no risk of someone "pirating" the plane. Maybe give a short credit (like "This is a modification of the original .acf file by IXEG"), so people know the heritage of your work. Cheers, Jan

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