Litjan

We are polling the official X-Plane airport database (apt.dat) - not the user´s Custom Scenery folder. Thats why it won´t show up until you either hand-edit the correct apt.dat or (easier) upload the airport to Laminar Research. Cheers, Jan

I just checked, the speedbrake increases rate of descent at 250kts from 1600fpm to 2000fpm. Thats exactly like on the real aircraft. As for it being "too ineffective" - you just found out one of the reasons why proper descent planning is so important in the 737 classic . CAL4 is not known as airport in X-Plane. You can "make" it with WED and upload it to Laminar, if you want it to be in the simulator. Thats why it can´t be picked as destination or origin. It can still be found as REF airport, because that position is coming from another (official) database, and we do not crosscheck if the airport is present in X-Plane when entering that field. Cheers, Jan

Hi, Morten is right - the real speedbrake´s effect is pretty bad, especially at low speeds. On the upside, you don´t have to observe a possible increase in stall speed, like you do on Airbus-type aircraft. The speedbrake at the FLT detent (don´t use it above that while in flight) will give you roughly 30% more sinkrate at 250kts IAS. Less when slower, a bit more when faster. As for the nav database range: We did increase it substantially in patch 1.2 (iirc). No idea why an airport would go into the REF AIRPORT field but not in the ORIGIN, have to check that out and will report back. Cheers, Jan

Hi Krzysztof, you may not be quite up to the current status of our VNAV implementation. Unfortunately VNAV is unable to follow more complex arrival procedures, and it also fails to read some restrictions from the database (especially waypoints with both above and below). For now you will have to fly descents like real pilots mostly do - in FL CHG or V/S modes, calculating the descent parameters in your head. We are working on improvingh VNAV in the future, so that also less experienced pilots can fly complex arrivals. Cheers, Jan

Yeah, and it may be worth checking if you have antivirus software running that could interfere with the FMS computations. There is some of that going on starting at lift-off, and you may have modified the routing/performance calculation unknowingly (like entering a new weight) and not executing it. So the FMS is constantly recalculating the modified routing. If antivirus checking interferes with this, the slowdown happens. I know many people are VERY worried about disabling live antivirus checking, and they frown upon excluding a folder from checking, but it may be worth just trying to test if that is the cause. We are still looking at options to remove this adverse effect of database accessing. Cheers, Jan

Never heard of this so far - lets see if other reports crop up. Do you have a modified route on the FMS (not executed)? Cheers, Jan

Hi Gareth, thanks for the reply - and again sorry for the inconvenience. We have a fix for that in the pipeline! Cheers, Jan

Hi Gareth, thanks for the report - what happens if you load up the IXEG first? I mean not after re-installing, but after shutting down the simulator completely, then starting up again with the IXEG 737 selected as aircraft? In other words, can you only fly after re-installing, or can you also fly if you don´t fly another aircraft in the same session first? Thanks for clarifying, Jan

Hi Art, I will check what is going on with that - thanks for the heads-up! Cheers, Jan

Holdings dont work. If they are important to you, I would stay away. Cheers, Jan

This may be a bug with 11.20vr3: https://forums.x-plane.org/index.php?/forums/topic/141415-strange-mouse-glitch/ Cheers, Jan

Here is the problem: Tom created the datarefs, but they need to be hooked up the autopilot logic. Nils is in charge of the autopilot, but he is out of the picture (due to private reasons) until about Summer 2018... Sorry for the tease - lets take the chance to review whats there, and collect what else you may need. I will compile those into a big list and then hit Nils with it when he returns ;-) Sorry, Jan

Most reports of "ILS not working" are due to the user selecting the wrong ILS frequency. Often the navigational database has changed, but the ILS´s in X-Plane don´t change, even if you install Navigraph or Aerosoft data. Another batch of reports are due to "shut down tailwind ILS" option selected. The rest is due to being out of range. The ILS receivers in the IXEG work exactly as the ILS receivers in the default planes - check on the map (M) to see the correct frequency. Cheers, Jan

hi Tim, havent heard of that one before - but we had some reports of users that can´t click buttons on the MCDUs after using the IXEG built-in view settings... could that be related to your issue? Cheers, Jan Edit: Also try upgrading to 11.20vr3, they fixed some problems with the mouse becoming unresponsive if the VR mouspointer is activated.

Good morning, 1.) Yes, we have some code interference - this will be fixed with next update. 2.) I see this as well and we will try to fix it. Two ways to avoid it: A.) Don´t click "resume last flight", instead choose "new flight" (should be same parameters). B.) IF you get the APU not running, flip the switch to START, wait until APU started and then connect both APU generator switches. Cheers, Jan

Yes, they are. But I would hold on upgrading until 11.20vr3 is rolled out (any second, now), as that one fixes a few showstoppers (for some people) of vr2... Cheers, Jan

Hi Jo va Bra, to tell you the truth, I don´t remember how this worked on the 737 classic . It may have been different to more modern Boeing aircraft, or it may have been the same and we portray if wrong. I will try to find out and maybe we can adjust it accordingly if warranted. Thanks for the report, Jan

Lots of info about your issue in this thread: Cheers, Jan

Thats awesome! Cheers, Jan

Same as before - 25% linearity, 0% artificial stability. Jan

Working on a fix for that as we speak (type) - just hold on for a little bit longer. Jan

I would say hold off until I tell you which sounds we specifically need. No point in doing all this work and then us not really needing it. Cheers, Jan

No, I can not confirm this. The 1.21 update is suitable for both XP10 and XP11.1x+ . The installer contains different versions of the aircraft and will install the correct set for your simulator version. Most improvements are for both XP10 and XP11 users, but some (like the adjustment for flight dynamics or the added cockpit reflections) are only valid for XP11. So both groups of users benefit from 1.21. Cheers, Jan

Yes, I can confirm your observation. Weird. I will investigate and see if we can fix this. I remember we had some problems with that before, its an initialization problem, which is never quite easy in X-Plane... Cheers, Jan Edit: Workaround for now is to start the APU really quick (or enable the ground-power)...

I just tried and it works fine, there. Watch for the mouse to become a little hand when over the switch, then grab and pull to left or right. Nothing has changed wrt the auto-brake... Cheers, Jan