Litjan

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

Ok, thanks for the feeback... we will look into this to see if there could be any lingering issue. We (like most users, appearantly) are seeing the GW change appropriately. Maybe you can help us narrow it down - fill out the whole PERF page, fly with a route activated, use Imperial, use KGs, try different startup situations, anything to get that GW going down ;-) Thanks, Jan

Did you guys reboot X-Plane after the patch? It shouldnt be necessary, but just to make sure... Jan

Thanks for following up and reporting! This issue didnt make it into 1.0.3 but is already in our log... will bump it up due to the crash! Jan

Noted, thanks! Jan

Hi Bernt, I will try to replicate this - stay tuned! Jan

Thanks for the report - will verify! Jan