RonMont

They do work for me.

Was going to exactly suggest that. Been using it for years, and it is flawless with the 3 aircraft I fly.

Did you check the CBs?

As I understand it, this is a X-Plane issue, not a Hotstart issue. Not too sure if or when it is expected to be corrected.

@spearlman It works; in my case (I'm using the beta v1.8-beta42), I had to exclude 3 datarefs: CL650/glass/heat_on CL650/avatar/laser_pointer_lamp CL650/avatar_self/laser_pointer_lamp Thanks again for this tip :-)

Thanks a lot for the information; one last question, as you did mention running X-Plane through a debugger: did you find that line above in the X-Plane log, or through the debugger?

I haven't tried it yet, as I have no idea how to exclude that dataref in the drt_ignore.txt (i.e. what is the format of the entry should be), plus, you are saying that that txt file should be in /resources/plugins. I kind of suspect it should be in the /resources/plugins/datarefTool_v... folder, no? I didn't want to mess with it without being sure. Thanks for inquiring!

As is the case for all FlyWithLua scripts, you put it here: \Resources\plugins\FlyWithLua\Scripts

Thanks for the tip! I will try that at my end too, as I also think that DRT is much more useful than the native one.

In the TAKEOFF section of PERF INIT, page 2 if I recall correctly (not in X-Plane right now)

3.0 would not cause the nose to come up at 80 kts, as it is more nose down than 5.0. But still, you should be between 5 and 6, depending on your TOW.

Maybe your trim is too high? Make sure it is between 5.0 and 5.6. My personal preference is 5.0, with a CG of 22%.

I stand corrected

Many errors concerning line 11 of your flight plan, for waypoint AMOTA: Line 3647: 2024-01-31 16:44:21 CL650[fpl_ser.c:780]: Error loading FPL: line "11 AMOTA UN747 40000.000000 37.605556 -5.251667" produced error "NOT ON AIRWAY" Line 3684: 2024-01-31 16:54:11 CL650[fpl_ser.c:780]: Error loading FPL: line "11 AMOTA UN747 40000.000000 37.605556 -5.251667" produced error "NOT ON AIRWAY" Line 3718: 2024-01-31 18:06:03 CL650[fpl_ser.c:780]: Error loading FPL: line "11 AMOTA UN747 40000.000000 37.605556 -5.251667" produced error "NOT ON AIRWAY" Line 3722: 2024-01-31 18:06:43 CL650[fpl_ser.c:780]: Error loading FPL: line "11 AMOTA UN747 40000.000000 37.605556 -5.251667" produced error "NOT ON AIRWAY" Line 3742: 2024-01-31 19:17:56 CL650[fpl_ser.c:780]: Error loading FPL: line "11 AMOTA UN747 40000.000000 37.605556 -5.251667" produced error "NOT ON AIRWAY" Line 3756: 2024-01-31 19:21:13 CL650[fpl_ser.c:780]: Error loading FPL: line "11 AMOTA UN747 40000.000000 37.605556 -5.251667" produced error "NOT ON AIRWAY" And yet, it is on the airway, so go figure!

If I understand your question well, then the answer is yes. I have done a few such visual approaches and it worked very well. When selecting the RWY, it will offer you to specify a distance from the runway to trace; I usually put 5 or 10nm. This puts a vector line to the RWY at the specified distance on the NAV display. It also inserts a waypoint called RX (or TX, can't remember well right now) automatically at that distance. I then fly it in VNAV, and LNAV to that automatically inserted waypoint, setting the ALT to the RWY threshold ALT + 100, and it works very well. Hope this helps.