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.

There were X-Plane 12 issues with screen and clickable zones handling, on multiple monitor setups. Nothing to do with the CL60 as such. Those have been fixed by LR in one of the latest updates; have you updated to the latest X-Plane 12 version?

That is very strange; I have never had the issue you describe in the almost 6 months now that I've been flying the CL60 at a rate of about 12-15 flights a week. Only thing that comes to mind is to make sure that your VNAV is definitely engaged, i.e. not only seeing the VNAV lights lit up in green on the MCP, but actually making sure that the PFD actually shows that it is active (VALTS for example).

No to both questions. I use VS only in situations where PATH is lost, either because I missed the TOD and need to catch up with the glide path, or if I execute a DIRECT TO that puts me above the glide path.

@PilsI think finally I managed to create a pull request after all. Hope it was done right

Hi Pils, Working with some guys on the FlyWithLua XPlane.org forum, I ended up with a script that works. The idea was to add a loop function in the script that makes the script wait for the datarefs to be available before running. I spent an hour trying to figure out how to do a pull request on Github, but only managed to create an Issue, and was not able to link a pull request to it. Here's the script that works. Thanks and have a good day! CL650_xsaitekpanels(APN4).lua

Any idea why the script automatically goes to the Scripts (Quarantined) folder? Sorry, but I have no idea what a "pull request" is

Hi Pils! Never knew about the existence of that script! Thanks so much! For some reason, it keeps being shifted to the Quarantined scripts folder, every time I load the CL. The X-Plane log claims that the datarefs don't exist, even though I do know they exist, as confirmed with Dataref Editor. FlyWithLua Info: Start loading script file E:\X-Plane 12/Resources/plugins/FlyWithLua/Scripts/CL650_xsaitekpanels.lua FlyWithLua Error: The DataRef "abus/CL650/ARINC429/L-FCC-1/words/FCC/0/ALT_SEL" does not exist. FlyWithLua Error: The DataRef "abus/CL650/ARINC429/L-FCC-1/words/FCC/0/VS_TGT_TGT" does not exist. FlyWithLua Error: The DataRef "abus/CL650/ARINC429/L-FCC-1/words/FCC/0/IAS_SEL" does not exist. FlyWithLua Error: The DataRef "abus/CL650/ARINC429/L-FCC-1/words/FCC/0/HDG_SEL" does not exist. FlyWithLua Error: The DataRef "abus/CL650/ARINC429/L-FCC-1/words/FCC/0/CRS_SEL" does not exist. FlyWithLua Info: Finished loading script file E:\X-Plane 12/Resources/plugins/FlyWithLua/Scripts/CL650_xsaitekpanels.lua FlyWithLua Error: The error seems to be inside of script file E:\X-Plane 12/Resources/plugins/FlyWithLua/Scripts/CL650_xsaitekpanels.lua FlyWithLua Info: 2nd Moved Bad Script to E:\X-Plane 12/Resources/plugins/FlyWithLua/Scripts (Quarantine)/CL650_xsaitekpanels.lua FlyWithLua Info: Load exit file. However, when I move the script back in the Scripts folder, after loading the aircraft, and then do a "Reload all LUA script files" from the plugins menu, it loads it fine, and everything works as designed. I'm baffled by this; probably a question of timing, like the script loads before the datarefs are loaded? I will keep investigating. In the meantime, if you have an idea about that behavior, I would appreciate your comment. Thanks a lot for your script; it would deserve to be found more easily however.

Hi everyone! So far, with @Pils's CL650_xsaitekpanels.ini file, the multipanel was displaying 0s only, instead of the ALT, VSPEED, HDG, COURSE, etc. I've been digging into it lately, to try and make those displays work, and I managed to find the datarefs. I now got the HDG showing properly, by using abus/CL650/ARINC429/FDCU-1/words/FCC/0/HDG_SEL. I have also found the following datarefs for ALT and IAS, but the values are in meters for the ALT, and in meters/second for the IAS: abus/CL650/ARINC429/FDCU-1/words/FCC/0/ALT_SEL abus/CL650/ARINC429/L-PFD-1/words/FCC/0/IAS_SEL For the VS value, I've only found datarefs that have values that I cannot decipher, but certainly don't look like 1000, 2000, 2400, etc; the values are not in feet per minute. I certainly would appreciate someone pointing me in the right direction for finding those datarefs. Thanks in advance!

Just look at the pedals themselves, in the aircraft, and observe their movement. You can also use the X-Plane Data Output feature to monitor the values of braking.

Ah! Thanks!