Litjan

Hi guys, this was something we changed during development - initially we had the EXEC button light up (just like in the tutorial video), but later we decided that it should only light up when there is a route that can be executed. In a way the EXEC button is the trigger for the FMS to start "working with the new route". And if you only input PERF data without a route, there is nothing to "work with". So once a route is activated, changing (or even entering anew) any value on the PERF INIT page will give you an EXECute light, because now a route will be influenced by your changed performance parameter. If you don´t have an active route, you will not get the EXECute light. Jan

Hi guys, thanks for the nice words and feeback - I think we are getting to the point where the plane works reliably and satisfactory within the limits of what we set out to do. Next will be adding the "missing features" as outlined in my initial post about that. We will spot/introduce some bugs during this process for sure, and I envision us doing the odd hotfix until 1.1 - but they will not be coming at a weekly basis, but rather "when having enough to warrant one". Please continue to report all findings, it is easy to get accustomed to little peculiarities, but we want the plane to work as the real one does, without having to "work around" or "avoid" certain things! Happy flying everyone, Jan

Thanks, poodster, I will verify and add for the 1.1 list - we can´t fix stuff like that in a hotfix, but it will go into the first real "installer" patch. Jan

Hi Tony, if you want to do it correctly, don´t use the disconnect buttons. The A/T disconnect buttons on the sides of the throttles are not used in normal flight, instead you disarm the speed mode just like you did. By disarming the A/T alltogether, you disable the speed reversion protection modes, too - something deemed too dangerous when carrying over 130 passengers ;-) I could imagine that you are flying in very bumpy weather, and the speed mode is re-engaging in speed reversion mode to stop the airplane from going too slow or too fast? I would really need a video to see what is going on. Also notice that the speed mode will automatically engage whenever a new pitch mode (alt hold, GS, vertical speed, etc.) engages, this is normal and a safety feature. Jan

Correct

We are aware but have not been able to figure out how to fix it. Maybe you can ask with the maker of the VATSIM light .pngs. For now we have only found out that using HDR makes them square, but not why... Jan

No, the tiller will always respond - but you are not supposed to use it at higher speeds, it is too sensitive. During takeoff and landing you should only use the rudder (over about 30 kts). Jan

Hi Jean, glad you got that working! In the real plane, the tiller will override the rudder - so if you hold the tiller, the nosewheel will not turn with the rudder. But if you move the rudder, the tiller moves with the wheels. The rudders won´t move if you use the tiller, though. Jan

That is weird ... make sure that you reboot the plane when transferring to a new area of the world, sometimes the navdatabase will not be loaded into the FMC whithout rebooting. Example: You fly around in Texas. Now you move your plane to LIRF (having the option of reboot on repositioning off) - now there will be no navdata for Europe in the FMC (we can not always load the whole world, it would slow down the database access too much). Jan

Very nice, thanks for sharing! Jan

I am pretty sure that is exactly how a VECTORS type waypoint is shown - just a loooooong line out. How far? Nobody knows... Jan

Thanks for the reference - I will have to check my manual at home - it could be that you are right! I didn´t know that it disabled the reverser as well - I know the lever can be pulled back - but of course I could never see if the sleeve actually moves or not. Good find, and I stand corrected! The gear sound playing with the lever is already added to the bug list. Jan

If you work for an airline that checks on you turning the landing lights on/off at FL100 via ACARS I would start looking for another employer . I will check the dataref and see whats going on . Jan

The inhibit system works ok for flaps 15 landings, though - can you describe what you think is not working ok? Jan

Thanks for the report! We have seen some cases where the waypoint won´t sequence, usually due to a wide turn and the plane not passing close enough - the LNAV is strictly following the magenta, but the wpt sequencing is dependent on crossing the wpt close enough... THis sounds different, as a direct-to did not seem to help (it usually does)... I will add this to the list and we will see if we can recreate and fix it! Thanks, Jan

Hi and thanks for the report - can you quantify "real slow" and "a lot of time"? I have timed the movement of yoke and aileron to the real aircraft, and they move about the same speed. I just want to know if you hve any other problem, there. Ideally you would make a short video and post it here... Thanks, Jan

Hi and thanks for the report. It is hard for me to say anything about the report - the landing gear I can see - there is a very outlying case where the gear won´t work without electricity, but in reality it should... The reverser on engine 1 should work just fine after an engine fire. The extinguishing agent will not destroy the mechanism. You will see that it operates more slowly than the one on engine 2, though - because only the electrically driven hydraulic pump creates pressure. So I guess it IS correct .

Yes, I love the Italian people, their country, the food and also their way to work around problems! I have been to Italy many times, everywhere from Catania to Milano - a great country for sure. The only thing not so fun is flying to LIRF, but that is another story. Yes, the green needles on the compass card show the bearing to the NDBs . the "thin" needle is NDB 1, the "thick" needle is NDB 2. If they don´t receive anything, they will simply point to the "right". You can also display pointers to the tuned VORs on the MAP modes, select the VOR/ADF pushbuttons on the EFIS control panel to do that. The RMI can show bearings to VOR1 or ADF1 (thin needle) and VOR 2 or ADF2 (thick needle). Change the selection with the pushbuttons underneath the RMI. Jan

No worries, I love Italy, I was just trying to make a joke (that aside, Italy is the only country I know that has a lot of published procedure for the case that certain NAVAIDS are inop ) For your problem: I see everything is working fine and just as intended. I suggest that you watch the tutorials and fly them - you will learn a lot about the operation of this aircraft and the way the avionics work. In this case, you have not set any wind, so the direction and velocity indications are blank (as in the real aircraft). The DME readout shows 6.6 in the top left corner (as in the real aircraft). The green NDB bearing indicators point to the 90 deg relative bearing position if no NDB is received (as in the real aircraft). If you think you have a bug (there certainly are still some to be discovered), try posting in the support forum under bug reports, we have a better chance of spotting the reports there. Happy flying and buona giornata, Jan

Thanks for the nice words! Jan

Since it´s an italian navaid, it´s probably simply not working Jan

Can´t reproduce this on my end - I only hear one bell. Thanks for the report, we will keep our ears peeled for that... Jan

Question: Can you "click" the missing buttons? I.e. are they functional, yet invisible? For standard bug chasing protocol I would ask you to remove all plugins except gizmo and pluginadmin from your plugins folder to another folder (you can move them back later), and reboot X-Plane. Please also post your log.txt file again when running the test. Thanks, Jan

This is intentional and the way it is in the real aircraft. The numbers and terrain symbology is created using the WXR Radar software (thats why you need the WXR system switch on) - and the symbology is rotated with the compass card between updates, so that wxr and mountains will stay in the right spot, even when turning wildly. The update via the sweeping beam or new terrain scan isn´t fast enough for this. Jan

I will forward this to Tom, we have seen some issues with characters from different keyboard types in flight-plans, and he has added some protections against crashing from that for the next patch... Thanks for the report, Jan