softreset

Thanks. If I wanted to redo the flight before then, is there a work-around? I assume it's the overwrite of the hold that caused the CTD. Fly the hold? Go into heading and fly direct? I was probably visual with the field anyway at that point. It's the trip on a VA world tour and I've got the rest of the week off, so I'd love to knock it out in the next 48-hours.

Simbrief route - DCT MERIT DCT HFD DCT PUT DCT WITCH DCT ALLEX/M080F350 N25A CARAC/M080F370 DCT JEBBY DCT BOBTU DCT 44N050W 46N040W 47N030W 45N020W DCT BANAL/N0458F370 DCT BUSEN BUSE5P Crash scenario - Descending on the STAR through FL160 past BUSEN. Was planning the ILS 02 and PESEX was in the flight plan as a fix and as a hold (directly after the fix). I put the PESEX fit into the scratchpad and then put it over the PESEX hold (to remove it and fly direct from PESEX to NETVO. Immediate CTD when updating the flight plan to override/remove the hold. Bummer too... 6 hours in. Log.txt

I'd like to request commands for Ground Services -> Refuel -> Refuel Truck Ground Services -> Refuel -> Interior Refuel/Defuel panel So that I can map keyboard shortcuts to these pop-ups. Thanks!

I'd like to also a popup toggle for the 2D Refuel Truck. I can make a new thread if necessary, but it seemed related.

Thanks Bob, you're absolutely right. I've edited my original post to reflect that.

With a TO N1 of about 89%, pitch of 5.5 units and about 10-12% range of travel on my T16000M into the full pitch range I was rotating to about 22 degrees before 250 AGL. With that same setup, at 4.4 units, I was closer to about 15 degrees at 250 AGL. Through 1000 AGL, I'm still setting the elevator trim to just outside of the green band to settle on 8-10 degrees of pitch for the transition into FD sync. Part of the challenge, obviously is the joystick. As I have to go hands off to manipulate the mouse. I suspect I'd be in better shape with a yoke, being able to apply constant positive pressure with my non-mouse hand. As a result I've tried to bind 95% of my needs to my Streamdeck so I can keep my hand on the joystick as often as possible during manual flight, so I don't have to be perfectly in trim.

For me, with the Thrustmaster T16000M I've been finding 4.4-4.6 to be a better setting with a vanilla controller profile. I was finding anything north of 5.0 the plane was leaping off the runway and blowing through 15 degrees of pitch on take off roll.

From the Collins ProLine 21 manual: On the MFD Plan Map, when the flyover attribute is added, the flight plan route is drawn as a line through the flyover waypoint. An arrowhead that points toward the waypoint that follows the flyover waypoint indicates an offset from the next course because of the flyover

This has been the recommendation on other threads. Popup Icing Display - Utilities - X-Plane.Org Forum

First de-ice in a while with the new 1.4 update and radio calls were fine. So probably operator error on my end, as I've yet to see anyone else report the issue as well.

Ah, alright. I understand now. Thanks!

Huh? Yes, I know they do. What I wrote in my initial post is that I can set a keyboard command for say altitude up and altitude down. When I press and hold the key on my keyboard the altitude knob will spin (albeit slower than the TBM) until I release the key. On the CL650 the knob that is used to change the parameters for the baro minimums, despite having a command will not continue to spin the knob. If you press and hold the bound command down the knob will only increment the baro minimum to 10 and then stop. A second key stroke, 20 and then stop. What I've requested is that the keyboard binding functions like the heading, course, speed or altitude knob The command I'm referring to (and requesting the consideration for change) is: CL650/DCP/1/menu_data_down DCP 1 MENU DATA knob down CL650/DCP/1/menu_data_up DCP 1 MENU DATA knob up

Odd, I've done it 4 times now and I've never gotten a call.

Fresh NVIDIA driver set and no crash. Thanks!

Is it possible to implement the de-ice truck letting you know over the com that they're done and driving off? There's an initial announcement of procedure but no conclusion.

Log.txt is attached First CTD with the aircraft in 30+ flights, latest version of XP-11 & CL650 Last line of the backtrace is... 2022-01-28 11:54:21 CL650[waas_api.c:205]: Failed to download WAAS API data: server responded with error 404 (Not Found) --=={This application has crashed!}==-- But full log is attached. I can strip all the add-ons/plugins and redo the flight but it won't be for another several hours and wanted to get the ticket logged. Log.txt

I must be missing something. I don't hear anything. I did the install (confirmed the file and the folder is in my scripts folder) but did not tweak any settings in the LUA file. I understood the instructions to only warrant editing the file if you wanted V2 & positive rate (everything else was 'automatic'). I have my speeds entered but just silence. Did ya'll change the default volume sound? Is the sound impacted by wearing or not wearing the headset inside the aircraft?

That's correct. Well fudge, I guess it's the particular save state on a specific airframe. Which is odd. When I went to go build a clean log file, I cannot reproduce the problem in non-persistent mode or a new airframe. Only my default (slight modified) C&D state on a specific airframe can I reproduce the problem. Disregard, I'll just purge the airframe.

I've attached the .fms output from simbrief that I attempted to fly today on FSEconomy. As far as I can tell, this is a valid/active airport with published charts via skyvector and navigraph. I can successfully configure the airport as a departure point in the Toliss A319, Zibo 738x (latest update), Flight Factor 757F and a current Garmin GTN database. The field has two asphalt runways (5198ft & 6500ft). AirNav: KMIE - Delaware County Regional Airport KMIEKTPA01.fms

An update & some clarifications as I successfully completed a 5nm before airport insertion on a flight just now into a non STAR'd arrival routing. Regarding why I built the route this way @Rodeo, I was flying into MYGF with approach on (but no center) and the TAF for airport implied a possible shift in winds. So that waypoint you see below the disco is actual the IAF for the RNV 06 into MYGF. I've also seen a half dozen real world Garmin videos where the example of arrival planning for Un sequenced arrivals was taught to do the ATK -5 or -10nm from the field. I was looking to artificially setup a VNAV profile. Similar to the video that @Tord referenced. My thought process was, if I'm at pattern altitude (ish) 5-10 NM from the field, I had flexibility to either fly the 06 visually, pick up the IAF, circle to land on 24 or overfly the field and come back on the 24 approach. The 1500 AGL gave me options and some vertical guidance, as a supplemental solution to the rule of 3. Why it didn't work this time, is because what you can't see on the previous page of the FMS is that my waypoint before MYGF is actually the VOR at the field (ZFP) and I bet it was confused on how to create the -5 NM waypoint from the field because it would have been before ZFP on my routing. After I did some debugging on the route (after the successful -5nm planned KLIT arrival), after removing ZFP it allowed me to do the -5nm ATK waypoint off MYGF. TL;DR - Operator error, ATK works just fine. Ensure that the waypoint it's creating isn't further away from the sequenced waypoint before the point you're looking to ATK against.

I'm practicing some along track waypoints. Currently enroute to MYGF and expecting the RNAV 06 (based on forecasted winds). However, what I'm attempting to do is put a waypoint, 5nm ahead of the airport as you can see via the attached images. My understanding to create this FMS programming. Add the waypoint to the flight plan Ensuring it's sequenced after the previous point (no discos) Then select the waypoint and do / -Xnm (where X is the distance before the waypoint) Then click the waypoint to insert it before In doing that I'm presented with the message you see: Along track WPT N/A I'm doing something wrong! Any advice? The FMS primer documentation doesn't cover this concept so I'm trying to reference what information I've found online regarding the documentation.

Appreciate it. If it's not possible, all good. Holding down a key should be possible, works on all the other knobs.

You're absolutely right. I was just hoping for similar performance between the two knobs from the same developer.

Thanks @BlackBird_GR. You beat me to it. There is a 50-second delay. Personally, anything <250 pounds I don't bother correcting. At anything over 250 pounds, the transfer pump is on long enough to always trigger the EICAS / and audio alert to where setting an independent monitor doesn't seem necessary.

Zero tests. The aircraft is completely cold & dark, no de-icing required. I am using the FBO fueling process, it's actually faster than the manual process because it's synchronous. I put on ~ 3000 lbs. of fuel and gave myself 5 minutes on "when are you leaving" phase of the FBO experience. The IRS alignment process is 6-minutes, so that's about as fast as you'll ever go through a legitimate take off sequence. In my case, I was 100% ready to go at 6-minutes. Like engines running, door closed, passengers seated. Truthfully, a normal flow for me is 12 to 15 minutes. But I tried a "speed run" to see how fast I could theoretically get off the ground.