Litjan

Well, you can not have both at the same time - but if the speedbrake is not assigned to an axis, the buttons should work... If all else fails, you may need to delete your X-Plane preferences, I think the button assignments can get messed up (we had a lot of users saying that B is assigned both to brakes and to the rotating beacon...) Jan

That is very good news! We (Nils) worked hard to get our sounds to be more economical, and it is still possible that people with crappy sound-chips may have some problems. So we are especially happy to hear that this improved for you! Jan

Can I get a pic of this with the whole instrument panel (also the MCP) showing, please? Jan

Thanks for the report - skipping a waypoint due to too much distance while passing... Its on the bug list! Vielen Dank, Jan

Hi Tom, again thanks for another detailed report! 1.) APU starts fine without fuelpump 2.) Don´t know what caused your drop to STANDBY, thought we had fixed the outflow valve problems with fluctuations. If if happens, just move the knob to STBY and back to AUTO 3.) SPD REST can be entered in format speed/altitude but only if you are above the altitude. You can´t enter a waypoint speed restriction on the DES page, it is only for showing them. SPEED and DES NOW don´t work yet, sorry. 4.) CLB is the correct power limit during a level change, even in a descent. It indicates the max power the engine COULD go to - not the actual power delivered. Jan

Yes, it seems to appear from time to time - whoever can find out what is causing this "no fuel startup" will be declared "tester of the week"! Thanks for your help, Jan

Hi, any fiddling with X-Plane internal artcontrols (skycolours, RTH, etc.) is likely to mess other settings up. This was officially stated by X-Plane devs, and I think we are seeing this effect here. FOr the "TAKEOFF REF" page problem, try to move your preferences files somewhere else (so you can copy them back if this doesnt help) and see if that helps - another user reported success with that. Jan

Yeah, deleting prefs is a harsh cure... I really wonder what is causing this! Jan

Hi Benjamin, I have no Mac, but indeed it sounds like it is a computational problem. Possible culprits are other plugins (XSquawkbox is also a plugin!), anti-virus programs (on Windows the Windows Defender is definitely causing problems in a MOD state), an outdated operating system, background programs running or heat issues (cores throttling down). Since it seems to happen on every route for you and other people on Mac are flying just fine, I don´t think it is a problem with the code per se. Yes, we will look into optimizing the MOD state calculation process in the future, but for most people this seems to be no problem, so I think we have to look at your specific setup for the solution to your problems. Hang in there and let me know if you make any discovery per the above points, Jan

Hmm, no idea - works here. Are the speedbrakes maybe assigned to an axis on a joystick? Jan

Hmm, no idea - we will try to reproduce and then we´ll be able to fix, I am sure! Thanks for the report! Jan

We will need to add some code to make the FMS not "miss" sequencing a waypoint when it passes it by more than 2.5NM (in LNAV). The LNAV is following the magenta, it has no idea about waypoints - hence the discrepancy. Jan

To clarify, 1.) The aircraft will simply follow the localizer signal. On many airports in X-Plane, this signal may not be in the middle of the runway (check local map to verify). After touchdown you must control the aircraft to stay on the runway, the autopilot can not steer nosewheel or rudder. 2.) The green light only goes on for ARMING the spoilers, not when extending. Thank you for the nice words, Papelin, Jan

Thanks, this is a bug introduced by trying to make the sound system be more econimical so it would conflict less with other add-ons. We will fix this soon! Jan

Tim, the trim indicator is not lit - it depends on ambient light to be seen. Make sure you have enough light in the cockpit to see it - I think in the real plane there is some backlighting somewhere in the control stand that sheds some light onto the trim indicator... Jan

Then don´t do that! This is not a NG! I suggest you look at some of the tutorials - in this case I would suggest tutorial #4. Have fun, Jan

Did you have VNAV armed at that point? Jan

You are right - this was a last-ditch effort to get this into the patch and there has been some confusion about what the right behaviour of that page should be. For now enjoy the fact that the TAKEOFF page will always show the correct trim setting - a luxury that the real pilots don´t have . Jan

Thanks for reporting back and happy you got it working! Jan

Roger, thanks! Jan

The real elevators are not connected to the fuselage, either - except in two connections - the elevator needs to be moveable as a whole for trimming. Jan

Thanks for the report!

Never mind, for me it works ok on both metric and imperial... We will have to search further. Jan

Well, if you look at the placard over the window, you will see that indeed quite a bit of weight-change is needed to see 1kt decrease... so I guess we can say that IF the GW changes for you on the APPROACH page, the speeds will also change - one less worry. Now we just need to find out why the GW changes for some people, but not for others... are you guys on Imperial or on Metric? Jan

Now THIS I could see - I am not sure if the real page will show the speeds updating while it is open, well, it probably does. So we will have to move these to a more frequent interval, too. The original problem was that the GW didn´t update, even if you kept re-opening the APPROACH page. Just to make sure, do the V-speeds update if you keep "refreshing" the APPROACH page? Thanks, Jan