Litjan

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

We run a "rough" calculation based on total distance of the route, but omit other factors (speed, altitude,...) so it may or may not be fairly accurate. The fuel consumption of our plane is fairly accurate, though - so you can use real performance charts to plan the fuel needed (if you have them). I often just do a quick calculation in my head: Distance/400 = flight time in hours 2400kgs * flight time in hours + 1500kg ascent/descent fuel + 2400kgs alternate/holding fuel Adjust this a bit for head/tailwind (if known) and for heavy/light aircraft. We are currently doing a rewrite of the VNAV calculations (you can notice them not being very good especially on descent with restrictions) and this will also give us a better way to calculate and total up the different route segments with regard to speed and fuel burn - which will make predictions on the PROG page more accurate. Cheers, Jan

Hi Valentiner, it is not implemented correctly yet. To save you the trouble of finding and listing all deficiencies not implemented yet or missing, I would like to direct your attention to these two pinned posts: https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v133/ https://forums.x-pilot.com/forums/topic/17981-version-133-known-bugs-and-workarounds/ Cheers, Jan

Normally all customers that purchased the IXEG 737 get notified of updates through the email adress they used to register at X-Aviation with. You can always download the plane again after logging in to X-Aviation (your customer account) and that would give you the latest version Cheers, Jan

Make sure that you don´t submit new tickets, this would put your request at the end of the line again.

Well, never change a running system! Yet I believe that the latest update may actually cure your problem... Thanks for the nice words! Cheers, Jan

Hi Markus, two possible reasons: 1.) Other software interfering, most often this is XPUIPC - this can be solved by using an older version of this plugin (search this forum, some people have reported which version works). 2.) The autothrottle having "control" of the thrust levers - to regain control you need to turn off the autothrottle mode (either N1 or MCP SPD or GA) and then align your hardware throttles with the position of the "virtual" throttles (aided by the ghost image UI). Cheers, Jan

It is hard for me to tell what problem you are actually suffering from. Entering restrictions into the LEGS page should mostly work, although the plane will often not meet them in VNAV. The file "This is Aerosoft.txt" file should not matter if you updated your navdata correctly with Navigraph data. It is not read by the code. We are currently rewriting the vertical navigation code, this should make the plane adhere to restrictions, both from the database and also from user entry. For now I would suggest not adding/changing any restrictions and just achieving them with selected autopilot modes (vertical speed or flightlevel change). Cheers, Jan

Ben is right, you need the intervention of X-Aviation support to clear this up. It looks like you might have X-Aviation products running on this computer before - but with a different X-Aviation account. This could happen if you bought this computer from someone else who used X-Aviation products on it. Or you have created multiple accounts with X-Aviation. A very rare situation, but possible. Sorry for the inconvenience. DRM means "digital rights management", another term for "copyright protection". It is our measure to ensure that products bought from us can not be shared with others. Cheers, Jan

Hi, you can normally install the 737 on three different computer (machines). If you just bought it yesterday it is unlikely that you exhausted this. At any rate the DRM would ask you to delete one machine, not stating that the account is registered elsewhere. You need to input your email and the password you used to register to X-Aviation into the gizmo registration window. Replies from customer support usually take between a few hours and a few days, depending on support load and weekend/workday status. You can also post a screenshot of what exactly you are getting when trying to register it here so I can guess a little better as to what your problem is. Cheers, Jan

In addition to the VNAV work we have also these fixes lined up for the next update: Improvements * Added switch in aircraft file to always force experimental flight model on * Improved tracking ability of nosewheel in tight turns (less skidding) * A "direct to" turn will not attempt to re-intercept the line between current aircraft position and the waypoint * Yoke checklist can now be flipped up and down and yellow bug goes all the way to top again * Added a dataref to indicate if autothrottle is active or not * Added a preference to "pause on Top of Descent" Bug fixes * Fixed right-hand windshield wiper 3D * Fixed fuel gauge testcycle * Fixed leading-edge devices lighttest button * Fixed EGT needle on steam gauges not going higher than 800C * Fixed hydraulic accumulator pressure on modern gauges always showing full pressure * Autopilot trim cutout switches will now also stop the speed trim * Scavange pump will not trigger unless a center-tank pumpswitch has been turned on then off * Animated stopwatch buttons * Vertical speed scrollwheel can now turn "infinitely" (instead of running against an invisible turn limit) Cheers, Jan

There can be a problem with a manipulator movement, dependent on the camera position. Just let go, move the viewpoint a tiny bit and try again, then it will work. I think it is an X-Plane problem... which version of X-Plane are you running? I think something was changed recently to fix that... Cheers, Jan

Sweet, thanks a lot!

A very interesting lead on this issue, Pedro. This might still be a thing to take to Laminar and/or check on our side. I think most people can run with max textures these days, but I think it should still look nice if you don´t. Cheers, Jan

Thanks for the report!

Thanks for understanding! I think sometimes a friendly no is better than a politically correct - "ok, we will see what we can do" - and then never do anything .

Yeah, I totally understand what you are saying - same for me. But when I take care of my kids, work, partner, pets, housework, or anything like that...I am far away from any of my computer controls. And IF I bump my joystick accidentially when sitting down or getting up or reaching for my coffee - all it takes is 3 seconds to recover the aircraft (it is usually well trimmed when the autopilot flies it) and then turn on the autopilot again. I can´t - for the life of me - understand how someone could bump or deflect the joystick "accidentially" long enough to get a 737 out of control, short of falling asleep at his desk... Thats why I think that even 5 minutes of dev time on this are not worth it - plus the added complexity and support load because someone is bound to click that option and then go on a tangent because "his joystick doesn´t work".

Hi Christian, the speedbrake we use is really the default "spoiler" dataref in X-Plane, so it should be accessible with that dateref. I am using a joystick button to set the speedbrake to its detents, so this should already work, I think. Cheers, Jan

This does happen in the real cockpit as well - and I consider it realistic. As is the solution: Be careful! We will definitely not disable yoke input because it is a real and important feature of the real aircraft: You can override your autopilot with flightcontrol inputs most of the time. Cheers, Jan

Heresy! There is always a possibility, I throw this one onto the stack of ideas and suggestions . I have to check if X-Plane offers those lights natively. Cheers, Jan