Litjan

Hi, we are aware of the problems with the restrictions and are working on that... it should be possible to add "in between" restrictions, eventually. There is no way to customize the turnaround state. It is fashioned after a realistic turnaround state and not moddable. Jan

Hi letec, I am very happy to hear that! I will try to replicate your findings on my computer - we will nonetheless work on this issue - after all it is only our plane that seems to be affected, so it must be something within our plugin code that is causing it. I am very happy that you were able to find an interim solution for yourself, though, and hope that you can get to enjoy our plane now! Happy flying, Jan

Yes, its normal . Happy flying, Jan

Hi Thomas, this is needed for the 2nd AP to stay on: Both ILS set on respective VHF receivers Altitude > 800´ RA Both hyd systems powered Both gen buses powered And probably a few more I didn´t think about - but most likely it is the second ILS not being set on VHF Nav 2... Jan

Thanks for reporting back - this will help us with future reports like this, as we have seen this issue now and then... Cheers, Jan

Hi Jolmos, you can find this information in the "interface guide", page 12. Jan

Hi Brian, thanks for the feedback - I also enjoy just flying it around VFR, got to do that much too little in my time of really flying the 737 . The flashing 8 is a sign that the autothrust reversion mode has kicked in - trying to help you from breaking the airplane or it´s passengers - It will spring to life if you get too fast for your current configuration, or too slow. To get out of it, simply increase the selected speed (it will automatically pop to a speed that is still "just" safe) by 15kts in the "right direction" - the flashing should stop, and then you can resume normal flight. Cheers, Jan

Hi and thanks for the report, in addition to Tchou´s advice for avoiding this problem, I suspect a jittery hardware throttle triggering the Rejected Takeoff Mode (we are basically just watching if the hardware throttle is "moving" and "being at idle"). To get out of the T/O mode, make sure that you turn off the A/T (switch) and also turn off both FD´s. To regain manual control of the thrust-levers during approach, make sure that the "ghost-throttles" match up with the hardware throttles long enough - i.e. don´t yank back and forth, but move over slow and deliberately. There is a tiny time-delay to avoid jittery throttles to display the ghost throttles all the time. Let me know if this helps? Jan

It will be another hotfix, but most likely the last one before the first real "traditional" patch which includes more than just code fixes. The hotfix is ready except for one item (VNAV descent speed limit overhaul) - and we figured it would be well worth holding off another day or two if we can get this in. If it turns out to take too long, we will release the hotfix without that. Jan

Hi and thanks for the report! The channels A and B are exclusively LEFT and RIGHT. There is no crossreferencing - even when you have both on (dual channel approach) every autopilot is tracking his onside ILS signal. We have a quirk which will be fixed with the next update: The FlightDirector MAster lights (MA) should stay on, even if the AP is in "command" (= working). So that might have added a bit of confusion. The FD that gets turned on first will be MA(ster) - unless an autopilot gets engaged, this will supersede the FD Master allocation. The channel A (left side) can only track stuff tuned on VHF NAV 1 and vice versa. Both can reference the FMS (LNAV). You can also see this at work when flying an ILS - the onside FD will give commands, while the offside FD will disappear (unless the ILS is also tuned on that side). However, the FMA (flight-mode-annunciation) will always be the same on both sides. I am not sure what happened on your FL CHG, it does sound quirky. If you can reproduce it and (ideally) make a short video of how it happens, you would help uns very much! Thanks for the feedback, Jan

Thanks for the feedback, gentlemen! Jan

Thanks for the feedback - we continue to optimize our sound code to have as small a footprint as possible, but if other code is taking up sound resources and there are not enough available it is tough. But your report gives us another idea to test... Thanks, Jan

No, its not Tequila (unfortunately) Jan

Thanks a lot, guys - we have something cooking for you as we type - development continues! Jan

We see some issues with people that have soundcards that can´t play enough sounds and those sound slots are already taken up by other, sound-intensive add-ons... We have also had the odd report where people turned down volumes by accident. Then people got sounds again after rebooting, so there is definitely some vodoo involved, sometimes. Let me know if any of these hints helped you get your sounds back - best regards, Jan

Ah, I see - so basically CH was added to the END of your routing, instead of the first point... I will have to see if I can reproduce that, looks indeed suspicious . Thanks for the report, Tom! Jan

Yep, this has been the bane of Tom´s LEGs page editing efforts - when you add a waypoint to the route that already exists, you will usually "shortcut" to it - but sometimes you don´t want that, especially if that waypoint is like the last point of your route. Many Routes pass the same waypoint twice, once as the IAF, and then as the last waypoint with a hold... We will have to revisit these cases - and I see a solution when we start implementing "derived waypoints" where we need to add a numbering tag to waypoints to keep them apart... Let´s see. Jan

Absolutely - and always has. I suggest reading up on the logic behind that before posting bug reports, though - it is a pretty intricate system. Jan

We will look into A/T tuning in the future - but it is a fine balance between it being too springy and too sluggish. The real autopilot will also over- undershoot the target values on occasion, but it shouldn´t do so by 20kts, that is true. Jan

Hi, hard crashes are usually related to other plugins or scenery installed. A hot candidate in your case is MrX6s San Diego Scenery. It has been causing crashes for many people, and so far he has not been able to figure out why that is... So I would go with that first (just add a _DISABLED to your scenery_packs.ini) and hope that fixes it. Good luck, Jan

Definitely a bug you saw there, Tom - thanks for the report and keep them coming! We will need to proof the FMC outside the "regular use envelope" in the future, like what happens if you do something really odd. We concentrate on getting "normal use" right, first, but are going to field more and more of the oddball stuff in the future. Jan

Correct observation - and known already. It is quite funny that this seems to be quite a job to fix, Nils is usually very quick about these things, but it has been known for a long time (since way before release) and it will just require a lot of time to change. Definitely on the list, tough! Jan

Yes, I am seeing the same issue - and it is indeed more obvious if the framerate is really high - we will look into it. Jan

Yeah, this is completely normal and I have seen it like this (or even worse) in the real airplane many times. IIRC the thrust levers were allowed to be about "one knob apart" at the same N1 and it was still considered to be in limits. And the acceleration in your movie was also fine. Also be aware that "engine age" is random between airplane loads. Jan

No need to apologize at all! This stuff is incredibly complicated and I often refer to my manuals and real pics and vids when trying to figure out how stuff is supposed to work ;-) Cheers, Jan