Litjan

Hi Charlie, you already can! There is currently a bug with the autopilot disengaging if you hit TOGA while the FLARE mode is engaged, but if you hit TOGA before that (like when not seeing any lights at 50 feet) the autopilot will stay engaged and fly the go-around for you. Cheers, Jan

Sorry Roger, I know next to nothing about coding or how Gizmo works... Ben Russel is lurking here sometimes or you have a better chance to get some info on that over here: https://forums.x-pilot.com/forums/forum/117-gizmo-development/ Cheers, Jan

Hmm, thats weird - sorry you are having problems with that. I know less than nothing about hardware interfacing and how our aircraft or Gizmo could influence that . Good luck getting to the root of this! Cheers, Jan

What Cameron said. And definitely not this month. Events in Texas certainly threw a big wrench into the wheel. It is really hard to do good development work in a cold house with a computer that has no electricity.

Hi Kris, yes, this is not the way it should be - often the 250/10.000 restriction gets erazed in the real plane to climb with a higher speed when still below 10.000 feet. Unfortunately our VNAV code is pretty frail right now and doing things out of the ordinary can make it fail, like you observe. The same goes for changing cruise altitude, entering complex descent restrictions, and so on. We plan to solidify the code some more - for now I would suggest to just enter the most "basic" profile and not modify it too much regarding the vertical profile. If you want to fly faster below 100, just use selected modes to do so and disregard what the FMS tries to make you do ;-) The combination we used in 95% of all climb scenarios was LNAV with CWS P - that way we could keep the pitch constant, i.e. 10 degrees for roughly 250kts, 5 degrees for roughly 300 kts (great for passenger comfort) and the speed would vary slightly. Cheers, Jan

The workaround here is to assing a button (I think you can assing buttons on the VR controller) to "toggle reverse". Once you toggled it, you can use the VR controller to push forward on the regular levers, but this moves the reverse levers back. It is a bit counterintuitive, we are thinking about ways to make this easier in VR. Cheers, Jan

Thanks for the report - interesting. I have never seen that before! While the PROG page is still very much WIP, the distance to the top of descent on the cruise page normally works well. I am very confident that this will not happen after the VNAV rewrite (which is currently on hold due to the horrible weather in Texas). Cheers, Jan

Buona sera Claudio, unfortunately I don´t have any runway weight charts for the Classic - we never had personal copies (they were on board the aircraft) until in 2000 or so we switched to calculation of take-off performance on our laptops/EFBs. So I can´t really help you with those, finding them on the internet is also impossible...for simplification reasons you can go with the 35 - 45 - 55 rule. 35 for "performance challenged" takeoffs (short runway, obstacles, contamination), 45 for heavy and 55 for light aircraft. Most runways in Europe are really long enough for the 737 and obstacle performance is only critical at a few (LSZH, LEBB, EDDS,...). Buona notte, Jan

I envy you! I had to transfer to A320s about 8 years ago and miss my 737 every day I fly! Arrividerci, Jan

Hi Claudio, we are missing the option to select arrival procedures for your departure airport (which is present in the real plane) - but there is a simple workaround: You can simply overwrite the DEST airport with the ICAO code for your departure airport (on the RTE page) and should then be able to select all arrival procedures for it. If you ever want to "erase everything" in your flightplan, simply enter a new (or the same) ICAO code in the ORIG field of the RTE page and that clears the whole flightplan. Cheers, Jan

If we can somehow disable the outside camera... yes

The truth is that you really can´t tell a -500 apart from a -300 while you sit in the cockpit. Well, there are two things - one is the registration plate pinned to the instrument panel (our -500s had an I or a J as the third letter). The other way to tell is to set flaps to 1 and shove the thrust lever forward on the ground, the -500 will get you the takeoff warning horn. The -400 is actually a bit different, it has stronger engines (you can see the thrust limit on the FMC and also get slightly higher N1s at full power) and a slightly different airconditioning panel. Cheers, Jan

No, unfortunately not - the future always in motion is. Cheers, Jan

Hi Jim, we definitely consider those variants (I flew both in real life as well) but we want to finish the -300 to "feature complete" standard, first. Cheers, Jan

Hi Noboru, this is intentional because it gives you the best "default view" (so you can see the engine instruments and the gear+flap gauges). There is no requirement to sit "right in line" with the yoke in the real aircraft. If you chose to do so in our plane, you can either set up your view with the arrow keys and then save it with CTRL-Numpad keys (recall with Numpad keys). You can assign these views to your joystick buttons, too. This is default X-Plane functionality. If you really want to move your default viewpoint you can start planemaker, import the 737 and then navigate to "viewpoint" where you can set the coordinates for the default viewpoint. Cheers, Jan

Hmm, no idea what you did there. Our plane should run fine with the Zibo mod installed as well - or we would have heard about it before. To troubleshoot I would try removing all other plugins - the ultimate solution is to delete the whole X-Plane folder and reinstall it from scratch, then install the IXEG. Cheers, Jan

Hi Fred, the gizmo versions should not conflict - the plugin resides in /resources/plugins and is a "global" plugin, you only need it once for all of the X-Aviation addons. The 737 "knows" these airports because it polls the database for all X-Plane airports. Normally a FMC will only poll airports from its database (what you buy from Navigraph or Aerosoft) and this includes only the airports "known" to that database. The 737 polls "all" of the X-Plane airports in addition. It scans a file called apt.dat. There are several instances of it present in your X-Plane installation, nowadays the most relevant one is in /Custom Scenery/Global Airports/ Earth Nav Data. There is also a "fallback" apt.dat in /resources/default scenery/default apt dat/earth nav data. My hunch is that your installlation of "Prefab airports" somehow does not jibe with our polling of those apt.dat files. Cheers, Jan

Wow, your installation of X-Plane is certainly "loaded"... normally I would suggest to remove everything plugin and addon (especially stuff like prefab airports) to test if they interfere...in your case I think a full wipe and careful re-installation of only the most necessary add-ons would be indicated. Your log is full of error messages related to not finding stuff in the apt.dat and I am sure this is the cause of the gizmo error you see. Evaluating custom path: D:\x_plane\Custom Scenery\Saint Barthelemy [TFFJ] TerrainFix\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\Hawaii\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\Antarctica4XPlane_3v1\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\Antarctica4XPlane_2v4\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\Antarctica4XPlane_1v4\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\z_ortho_Arizona_Grand_Canyon_HD\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\Orbx_C_GB_Demo_TrueEarth_Orthos\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\Orbx_B_GB_Demo_TrueEarth_Overlay\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\Orbx_A_GB_Demo_TrueEarth_Custom\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\yOrtho4XP_Overlays_v3\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\yOrtho4XP_Overlays\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\zPNG\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\Saint Barthelemy [TFFJ] by O.Maaß V1.0.1\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\reykjavik\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\simHeaven_X-Europe-7-network\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\ZZ_DF-Hard_Surface\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\XAirportScenery\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\x_Prefab_Library V8.0 MisterX\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\Wrecked_Vehicles\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\world-models\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\THE-FRUIT-STAND Aircraft Library v3.0\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\The_Handy_Objects_Library\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\STATIC LIBRARY\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\SS Segmented Circles\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\simHeaven_Vegetation_Library\Earth nav data\apt.dat Did not find any airport data in this scenery. Evaluating custom path: D:\x_plane\Custom Scenery\Shoreline_Objects\Earth nav data\apt.dat Did not find any airport data in this scenery. In general my recommendation for every X-Plane user is to try to keep the installation as lean as possible. Some folks seem to be unable to resist installing whatever they can find, and at some point things are going go give. Sometimes less is more ;-) Cheers, Jan

No, the dashed line not matching the approach course is just an effect of a strong magnetic declination, I think.

I am running Navigraph cycle 2008 and when I turn onto the final approach course at KISIL I get this picture (both taken at the same time, sim paused) - so for me it works fine. If you see something else there may be something wrong with your Navigraph cycle. Cheers, Jan

Couldn´t reproduce the error . Maybe you can give me the exact steps to get it? I spawned at FXMM, then went to RTE page, entered FXMM in ORIGIN and FAWM in DEST fields and it worked fine...

Hmm, ok - can you tell me which ILS approaches are not lining up so I can test it on my installation? There is always the chance that a navdata set has wrong data, I still run a cycle from summer 2020...

Hi, the navigational data we include for free with the IXEG 737 is fairly old. Back then, there was no ILS nav data published for Canadian airports. It is possible that the MD80 uses more modern (i.e. X-Plane default) navigational data. If you update the navigational data to current one (by buying it from Navigraph or Aerosoft) it should work out much better. Cheers, Jan

Hi Fred, thanks for the clarification! I will try the airports I can see in your screenshot and see if I can reproduce that! Cheers, Jan

Hi Valentiner, you are doing fine! It is my fault for not looking at your first post closely enough! The waypoint "MENBO" is your "FROM" waypoint - you have already passed it. The waypoint "NORET" is your "current to" waypoint and "KISIL" the "next" waypoint. The PROGRESS page is built like a standard ICAO position report that pilots had to make (and still do in some regions) where radar coverage does not exist. You would need to call ATC with a position report that would go like this: "Flight XYZ, position MENBO at 1558, estimating NORET 1602, KISIL next". Airline pilots also use this page to fill out the flightplan when they track fuel usage. So you can use it to check how much fuel you had at the last waypoint (FROM) that you passed. Because often you forget (or are too busy) to read off the fuel right as you pass the waypoint, so you can use the PROG page to check it. The fuel at MENBO should definitely be more than the fuel at your next waypoints, though - which is clearly a bug. Cheers, Jan