Litjan

Currently this is possible "sometimes" . In my experience the VNAV code obeys speed limits inherent in the procedure quite well, and it will probably also adhere to manual changes...but you should do them as early as possible (ideally before taking off). The current VNAV code does not react very well to changes made during the flight. A workaround would be to disengage the autothrust (turn if off completely) and use the thrust levers to manage your speed manually - VNAV would still follow the path. Naturally we hope to fix all that in the future... Cheers, Jan

Hi Splash, you are right, once the lua error screen comes up, the rest of the code is on shaky ground and may be erroneous, a reboot of Gizmo is the only way out. I am sorry that you had this error, while speed and altitude inputs in the LEGS page are not being honored by our VNAV code right now, at least they should not cause a lua error! So to save yourself the trouble and potential lua error, for now I would refrain from editing the route heavily with constraints. At best this could serve as a reminder for you, but the VNAV code will not attempt to meet your restrictions. If restrictions are read from the database, you can leave those untouched, of course. Cheers, Jan

I don´t recall what the MEL says exactly, but usually it has a modifier that says "unless it is needed for the type of flight/approach intended". So technically you can fly without CATIIIa capability, but it wouldn´t be smart to do so when going to an airport that is fogged in. I am not sure what the MEL says on the 737 Classics still flying today - but as far as I know it is not mandatory to be RNAV5 capable in Europe yet. You may not be able to fly in free route airspaces, or maybe you can and would get vectors in that case. Same goes for RNP arrivals - often there are backup procedures or ATC would offer vectors - or you simply can´t go to an airport that mandates use of those procedures. My company still flew A320s (before Covid) that had no GPS on board - they couldn´t fly RNP1 or GPS approaches, either. Cheers, Jan

Hi, yes, we always had to fly the RNAV approaches in V/S mode - VNAV mode was not certified on the 737-300. The 737NG and other more modern aircraft can fly these approaches in LNAV/VNAV - but you can also fly them in LNAV V/S or LNAV FPA (flight path angle). You have to do so, for example, if the temperature is too cold (as you would fly too low in VNAV). I know that technically the 737-300 was able to fly in VNAV as well... I tried it once in the real aircraft . In our aircraft (IXEG) it is possible, but you can not adjust the speed correctly, I think it will fly 150kts hardcoded. Cheers, Jan

No, development is not dead, it is just taking a pause because Tom is busy with something else. That is the way it has always has been, I wish we could do this full-time but this is not economically feasible. So we have to pursue other avenues of making a living that sometimes preclude us working on the 737. The plan to implement/improve VNAV, holding and a slew of other features has not changed, but as always we can´t provide an estimate or much less promise when it gets done. We are fully aware of our customers waiting for these features and will endevour to complete them as soon as we can. For VNAV and Holdings I made videos that show how to "get around" this functionality missing. https://forums.x-pilot.com/forums/topic/17872-ixeg-videos-13-and-onward/ This is not an excuse to not do them - but the real aircraft´s FMS is covered by the MEL, so you can actually fly it in regular passenger service withouth the FMC working (I have done this once in my career in the late 90s.). Cheers, Jan

Hi Enrit, I don´t see anything that looks wrong on your log.txt.... but if your pop-out menus don´t work that hints at a problem with gizmo running not nominal. Did you activate the 737 (enter your X-Aviation credentials)? Do you run a multi-monitor setup (those have problems with the pop-out menu sometimes)? Is your hardware (Saitek stick) set up properly? You might be running a different controller profile, check your joystick setup. There are two switches (buttons) not working right now (Fuel QTY test and LE device indicator test), but everything else should work. Cheers, Jan

Yep, it is a known bug with the electronic engine instrument version. The pointers do not follow the real pressue. Cheers, Jan

For a weight of 42.000 kg (92.400 lbs) the official performance climb charts (for ISA +10) show: To climb to 37.000 feet: Time: 15 mins Fuel: 1150 kgs Distance: 92 NM This is with the normal climb profile of 250/290/.74 Cheers, Jan

Hi Mizra, on the Classics steering is only possible with hydraulic pressure A. If you loose it you could still steer with the rudder (at higher speeds) or with differential braking/thrust. You can actually try this on our model by turning off the A hydraulic pumps. The normal braking system is powered by system B. If it gets low or fails, alternate braking is supplied by system A (although now the anti-skid is working on "wheel pairs" only, as opposed to individual wheels as with the normal system). Also using the autobrake only works with the normal braking system. Cheers, Jan

You can output the value for "flaps extension" to the screen (small green numbers) using the DATA OUTPUT tab in the X-Plane preferences. That way you can see the flap deploy ratio. It may be that we require a pretty small number, and if your axis does not quite reach that value, our code assumes "flaps are extended". Cheers, Jan

Hi Mizra, our weather radar will only pick up X-Plane default weather - but it depends on the weather addon if that one is also using X-Plane default weather, so it could be working with ASXP. A possibility is that you "overscanned" the weather ahead. At 32000 feet the air is really cold and the weather radar can not pick up ice crystals. It can only "see" liquid water (below the 0 C altitude). So if you approach a cell when flying high, you need to tilt down more and more to see it. When you are close, you can´t see it on the radar anymore, because you need to tilt down so much. Modern wxr radar systems "store" the position of cells, so even if the radar can´t scan it anymore, it still shows. https://safetyfirst.airbus.com/optimum-use-of-weather-radar/ Cheers, Jan

Hi mizra, this is odd - of course the lua error should never happen at any rate - I see that the climb page shows a "max rate" climb and the flaps limit active, which should only happen if the flaps are not up (do you have a hardware axis controlling the flap position?). The "max rate" climb regime is something that normally the pilot would activate manually (the default is the ECON CLB, so I have no idea how that happened. Maybe Tom can glean something from the lua error report, thanks for reporting it! Cheers, Jan

Hi Enrit, this looks like an install gone bad - make sure you install the latest version of the IXEG (1.3) Cheers, Jan

Hi James, hmm, this is odd. If you can tie this behaviour to pressing a button or key - are you using XPUIPC to drive your hardware, maybe? We are using default thrust reverser logic for the most part, so I really have no idea what could be causing this. Are you experiencing the same on other aircraft? Cheers, Jan

Make sure you do NOT depress the pedals - they release the parking brake. If that doesn´t work, make sure that no braking is applied (by bringing up the "gear and brakes" value on the screen via the DATA OUTPUT tab. Let me know how that goes? Cheers, Jan

Hi Mizra, yes, there is. You can load the 737 up in Plane Maker.exe (it is in your main X-Plane folder) and then go to the tab "Standard" then click on "Author" then make a checkmark on "Always use experimental flight model". Then save the aircraft and from now on it will always run with this option enabled. We will add this in our next update, but for now you can do the modification yourself. Cheers, Jan

Hi Novato, I am happy to hear that! Let me know if you have any other problems! Cheers, Jan

Hi Novato, I have no idea what is going on with IVAO - we made the TCAS to show the targets as available in X-Plane (AI aircraft) with those datarefs. I thought it was working with VATSIM and IVAO as well, if it isn´t then that would be up to the IVAO client to emulate correctly, I think. VNAV descents can be quirky, that is a known issue. Pretty much the only descent profile that works well is a normal descent from cruising altitude without altitude or speed restrictions. Entering restrictions is possible, but VNAV will likely not follow them. If you encounter problems with the VNAV calculations, revert to a V/S or FL CHG descent to meet the mandatory restrictions. We are looking to improve this in the future! Look here, the last point in the "FMS" section: https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v133/ Cheers, Jan

Hi, you can probably find some more detailed information if you search a little bit for the real POH - but if you calculate 2.400kgs of fuel for every hour of cruise (.74 -> 420TAS) you should be close. Add the fuel needed to climb to 37.000 feet (ca. 1.500kgs) to that and roughly 2.500 kgs for alternate fuel and final reserve and you should be ok. Don´t forget to factor in headwind, if there is some. Cheers, Jan

We will likely have to revisit the coding of the v/s scroll wheel manipulator again, anyway. Currently it only has a limited numbers of revolutions, so it is possible to "run out" during your flight. The real scrollwheel has no limit, of course. Cheers, JJan

Yes, it is fairly easy to get into trouble doing this - keep in mind that on the 737 classic NO autopilot or autothrottles modes will be used or armed while still on the ground! The autothrottle should be "armed" while lining up on the runway and then pushing the TOGA buttons will actually trigger the take-off modes for the flight-director (if they are on) and the N1 (full takeoff power) mode for the throttle. Happy landings, Jan

Hi Simon, welcome back! I personally haven´t really tried the "other" free add-on - but I keep hearing great things about it and anything that furthers our hobby is good in my book. And as they sometimes say - with the money saved on the Zibo, go ahead and buy the IXEG . Happy landings, Jan

Hi Irargerich, hmm, those are odd problems - maybe some other plugin you have running could be interfering. However the autothrottle can also take control of the throttles on the ground - that is why they are "armed" only shortly before entering the runway: If a pilot touches the TOGA buttons, the autothrottle will engage and set takeoff power! The little lights are indeed "marker beacon" lights. There used to be radio markers associated with ILS approaches, sometimes we still have them these days. When you "overfly" them, they will make the lights flash and a beeping sound - this tells the pilot that he is a certain distance from the runway. Cheers, Jan

Hi Irargerich, thanks for your kind words! Lets see if we can shed some light onto this... 1.) This usually means that the autothrottle took control of your throttles. If the autothrottle logic does that, we remove control of the throttle from the user, because normally users do not have a throttle that can "move" (it has no motors). The autothrottle will take control if the user tells it to - like if engaging a certain autopilot mode or autothrottle mode. But sometimes the autothrottle also jumps in to save the aircraft if the user tries to fly too slow - this is a reversion mode. To get out you need to increase the commanded speed by 15kts (and be fast enough to not get into reversion again) - or you need to turn off the autothrottle and then "regain" control by using the ghost-throttle symbol to align your hardware thrust levers to the virtual thrust levers. I recommend watching my tutorials on autopilot use here: https://forums.x-pilot.com/forums/topic/10746-training-videos/ but also this: https://forums.x-pilot.com/forums/topic/18101-faq-for-new-users/ 2.) Make sure you "turn on" the avitab, there is a little button on top of it on the CPTs side - we default it to "off" when starting cold and darke 3.) We use the "normal X-Plane" braking system. To help you troubleshoot you can display the "gear and brakes" status on the "DATA OUTPUT" tab, this will show you small green numbers on the screen that indicate the status of your brakes. It could be that you use the autobrake or the parking brake is still set... Cheers, Jan