Litjan

Hi Tom, another good report, complete with debug.txt and everything... thanks a lot! I have never really deleted a coroute in the real FMS... not sure, but I don´t think the DELETE button would work. Conceptually it is just "triggering" a load process. Afterwards it is irrelevant... in our FMS simply type in the ORIGIN 4-letter ICAO again, this will clear the route. In the real FMS I would simply "overwrite" the old route - enter new data, clean out the old by shortcutting (copy+paste the first waypoint of the new route+STAR+Approach and then insert it right after the last waypoint of the new SID). You shouldnt have a crash, though, we will investigate that! Thanks, Jan

Hi Xander, There is a thread about braking and brake-pedals - I dont think this is really in our court, maybe more Laminars... The deceleration levels for the autobrake are default X-Plane, we can´t overwrite those... I agree that the values are a bit less than in the real aircraft, I prefer to use 3 or MAX (which ISNT maximum braking, despite the misleading name...). SETI works for me, just tried to make sure. What is the problem you face? Thanks for the nice words! Jan

Hi Stefan, this is most likely a bug - could it be the same thing happening as here: ? I will try to recreate that one... next time you see something funny like that, please export a debug.txt (need to enable debug mode in PREFERENCES and then click the . on the left MCDU four times....) Thanks! Jan

Ok, will look into that! Thanks for the report! Jan

Hi, and thank you for the excellent report - did you output a debug.txt by any chance? This enables us to examine the vertical profile with the click of a button, instead of reflying the whole route ourselves... Will look at this nonetheless, of course! Jan

That's correct. Jan

This is realistic. The fwd pumps "uncover" if attitude or acceleration is high, the fuel surges aft. More prevalent the less fuel you have. This is the reason the master caution only triggers if both pumps run dry... Jan

Hi, Initial Problem most likely due to residual control Input, most likely from flying with the Mouse and not centering. Or a spikey Joystick. The second problem (crash) is probably fixed with next update! Jan

Looks a bit funny - but at least no crash, right? I will recreate and add to list. Thanks for the good report, Jan

What, and pass on my secret tricks??

Hmm, crap. Where you able to narrow it down at all? Plugins? Artwork control tweaks? Video card drivers? Jan

! And my poor brother, too!

Thanks for the log - I will forward it to someone who can read that cryptic stuff ;-) Jan

That IS strange... thanks for reporting it to Ben. Nils thought it might have to do with HDR (since the lightning ups lighting values across the board, some lights may appear dimmer in relation, or such...) Jan

I will try to keep that in mind, thanks! Jan

Hi Josheph, thanks for reproducing it - I just tried, and I see the same thing. However - I also see this effect on the default airplanes (tried with the Baron).... SO: 1.) Don´t set weather like that (its REALLY unusual to have CAT II ops AND thunderstorms) 2.) File a bug with Laminar Research Good luck! Jan

You are wrong, though Jan

Even though you are a very pretty lady - no! Jan

Ok, I was able to reproduce the issue, thanks for the report! Jan

Tried to reproduce, but lightning works fine with the default X-Plane weather. Can´t fix until we get more info.. Jan

We are not over-writing any of those settings, so it should not be a problem with our plane. Make sure to never close X-plane with the little "X" in the corner, always use the "close" dialog - or it will not save your settings. For recommended control settings, read the documentation, it is also discussed in "Quickflight #1". We recommend 0 artificial stability and 25% non-linear, iirc. Jan

Just following up on this - did we fix these issues with 1.0.2? Thanks for your help, Jan

Quick thinking, James. I think we have modeled the alignment process not working when the airplane is moving. Without engines, the plane shouldn´t move much, unless the ramp is slopey. But I have also seen users that started the engines without the hyd-pumps on, and never realised the brake accumulator was depleted. That being said, we look into improving charging of the brake accu during reboots - right now a gizmo-reboot won´t recharge it, so you would either have to run the B hydraulic pressure up, or reload the aircraft... Jan

That is true - the weights on the PERF INIT don´t update every frame, just every 2 seconds (we figured that you can´t really burn too much fuel in 2 seconds to warrant a higher frequency). The downside is that you sometimes see this small lag when switching to the PERF INIT page. Once that page updates, the changed GW is also transmitted to the APPROACH REF page. Unfortunately this won´t work without going to the PERF INIT first, so that is what we are fixing (looking into making it a smaller interval, too) Jan

Ok, we will look into increasing oil pressure a bit in the future, I agree that it is a bit lower than in the real plane ;-) Automatic failures is yet to come - we have some failures that you can trigger yourself in the "failures" menu, and some failures from the X-Plane failures work (engine failure, fire, ....) Since we control a lot of features through our plugin, you will get mixed results with the X-Plane failures, though. Jan