Litjan

Thanks for the feedback, Jailer! And no, its not solved, we just "mass locked" those threads, because people kept posting their stuff there and we were worried that we might not see them... Jan

Wow, thanks for putting all this research into this! I think the intended behaviour for the fuel is "always start with the amount the user sets up once" - so the guy that always wants to start with 5000kgs doesn´t have to drag the sliders everytime he starts X-Plane. Setting the "current fuel on exit" would defeat that purpose... I personally think that we might want to revert to the old "fixed" system for the fuel - and maybe tell users how to edit the value in the prefs.txt... Jan

Hi and thanks for the great report - yes, initialization is a total pain in the rear! It is all dependent on what is being called first, I don´t understand much about it, but you can even assign a button to "reboot" gizmo - so maybe just clicking that once the sim ran for one second is your best bet for now. We will continue to improve this aspect, but it is a total can of worms, from what I heard... Jan

Yes, that would have suprised me. It must be a problem with your computer not having enough computational capacity to run the calculations during the MOD phase...so something is stopping it from calculating well. Do me a favour. Spawn at TXKF. Output the framerate on screen. Plan a flight to KJFK, pick any STAR and approach, then fly direct to the first waypoint of the approach. Now start taping a video (CTRL-space, iirc) in X-Plane, then do the MOD thing (shortcut to the second waypoint) and then post the movie here or on youtube. I think we need to see what is going on to be able to guess the problem. Did you check on the other possible culprits? Virus scanner? What OS are you running? Is it the latest and newest OS? Jan

Hi Franz, I see the same thing on some STARs and transitions... we will need to start "tuning" the VNAV calculation process over the next weeks - for now we concentrate on clearing the crashing... Jan

Hi Tom, always good feeback from you! I think you are right, using a button will not trigger the disarm light... I get this a lot now that I am testflying on my laptop... Will check that out. The "USING RESERVE FUEL" message isn´t implemented yet - but on the list! Cheers, Jan

Have to check the real page, but could be! Jan

You are right. It is on the list! Jan

Ok - in this case it should stay - we will take a look at that! Nevertheless, even with the switch in GRD it should work... (just no pre-pressurization on ground). Let me know if you see the AUTO FAIL light again without doing something that might trigger it (power failures, resetting the plane, having window open during flight, etc.) Jan

They are in the X-Plane 10\Output\preferences folder. You probably only need to remove the X-plane.prf file (move it somewhere else and see if this helps!) Jan

Thanks for the report, Philip - let us know how the thing with the lights goes! Jan

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