jfjoubert

Maybe this can help? Look at the section "Exclude files or folders from scanning" https://support.avg.com/SupportArticleView?l=en&urlname=Use-Mac-AVG-AntiVirus

@SHaines Glad I could assist... I assume most users with yokes won't have this issue if the yoke has a spring detent for the pitch axis. I now make a point to check that the joystick is centered.

The only time I had this "issue" was when my joystick (a classic Sidewinder FF2) was ever so slightly off centre on the pitch axis. Moving it back to centre stopped the "bobbing". This was however without the EFM.

Make sure you have Experimental Flight Model enabled.

Glad I could help...

Rudder trim is done from the "hat switch" on the left handle of the yoke... YL and YR for Yaw Left and Yaw Right. For takeoff you should trim your rudder to the right of centre but not quite on the green mark... I think this might also depend on your takeoff weights etc., not 100% sure. You can also map your joystick buttons to Yaw trim left and Yaw trim right.

It's also interesting to see how the strobe light increases in intensity as the engine is starting up...

Yes... you can use a FlyWithLua script. Take a look at this post and the Mixture.lua script from @Ch.Cole.

Please try the attached script... I have used your axis number for the flaps, but you should just change the mixture axis to your number again. This code will move the flap lever to the following positions based on your axis: > 90% = UP Between 45% and 55% = TO < 10% = LDG You can change the values in the script to suit your needs. If your axis is working the wrong way around just reverse the axis in the Joystick settings in X Plane. Mixture.lua

No probs... I will take a look and see if I can get the flaps working for you. Sit tight...

In the FlyWithLua menu just select the "return all quarantined script files" to get your file back. Also undo the changes you made for the flaps to get it back to a working state with your throttle and reload the script in FlyWithLua menu. This should at least give you a working throttle again. You can send me you axis numbers for your prop and flaps and I will see if I can adapt the script to work for flaps.

Hi, My method above might not be the best (or correct) one... I tried using a completely different axis and I used the "write axis assignments to log" FlyWithLua macro. This particular axis showed up in the log.txt as number 4, but using this value in the script didn't work. It's the displacement axis in the list below. clear_all_axis_assignments() set_axis_assignment( 4, "displacement", "normal" ) set_axis_assignment( 25, "right toe brake", "normal" ) set_axis_assignment( 26, "left toe brake", "normal" ) set_axis_assignment( 27, "yaw", "normal" ) set_axis_assignment( 50, "nosewheel tiller", "normal" ) set_axis_assignment( 75, "roll", "normal" ) set_axis_assignment( 76, "pitch", "normal" ) set_axis_assignment( 77, "nosewheel tiller", "normal" ) set_axis_assignment( 78, "throttle", "normal" ) So what I ended up doing was to open DataRefTool and and in the filter window at the bottom type "sim/joystick/joy_mapped_axis_value". Make your DataRefTool window wider so you can see most of the axis values. Now move the particular joystick axis that you've mapped and look in the list to see which value is changing. Count the position and subtract 1... The array starts at 0. This should be the actual number of the axis that you can use in the script. In my case the actual number was 15. Go figure... Try this and see if it works for you.

Hi Tom, Apologies, I should have been more clear... this issue is only when trying to use these datarefs from a FlyWithLua script.

O, and ixeg/733/fuel/fuel_qty_test_act dataref is also not working properly.

Hi Tom, I can confirm that the following datarefs are not working as expected: ixeg/733/caution/caution_ap_rst_act ixeg/733/caution/caution_at_rst_act ixeg/733/caution/caution_fmc_rst_act Whenever you reference them as a dataref() from within a FlyWithLua script and you set them as writable you get constant "clicking" sound in the cockpit. Also, there are no indicators for when the lights are on on these buttons. I would imagine that if you really want to be pedantic then you should have 2 indicators for the AP and AT buttons... red and orange. One thin I would like to mention is the following: Could you make sure that whenever you create a command, especially for buttons and swithces, that they will work correctly when using the command_once() function? I have seen in some 3rd party planes (not the IXEG) as well as some standard X Plane commands that they don't always work as expected when you execute them with command_once(). As long as you bind them to a keyboard or joystick button, or if you programatically execute the command_begin() followed by a short delay and then the command_end, then they work fine. Just a thought...

Yes you can... the easiest way is to simply reuse the existing code in this script and just change it for the flaps. So you will need to add the following: A dataref for the flap handle (You can use the X Plane default "sim/flightmodel/controls/flaprqst" and make it writable as well. A dataref for your flap axis from the joystick... you will have to look up your axis number again. In the getvalue() function just add the code to check the flap axis dataref for the 3 ranges (up, takeoff, landing) and then set the flap handle dataref to 0 (UP), 0.5 (TO) or 1 (LDG). No need to use commands in the sethandle() function. That's it.

All you have to do is to replace the axis number in the mixture.lua script with the number for your prop 1 axis. Try this: Load the TBM in X Plane Map your prop 1 axis under Joysticks From the X Plane menu select Plugins - FlyWithLua - Write Debug file Open the FlyWithLua_Debug.txt file in the root folder of your X Plane install Search for "clear_all_axis_assignments()" in this file The next couple of lines will contain all your axis assignments with their respective numbers Take the value for prop 1 and replace "28" in the following line in the mixture.lua script DataRef("mixture_axis", "sim/joystick/joy_mapped_axis_value", "readonly", 28) --Replace 28 with your prop 1 axis value Reload all Lua script files.

You're welcome.

Have a look at this FlyWithLua script courtesy of @Ch.Cole. Should work fine with the CH Eclipse Yoke.

Thanks Litjan... these 3 datarefs are actually the exception rather than the rule. As far as I can see most other datarefs in the IXEG are fine for cockpit builders.

Not sure why these datarefs have this behaviour... I have come across this in some other 3rd party aircraft as well. The moment you reference a dataref as "writable" then you get the constant repeating as if you're holding down a button. The only workaround I could find is to use "Classic code" in your FlyWithLua script. The recommended way is to use a magic metatable. (You can read up on this in the FlyWithLua manual) Here's a sample of using a magic metatable: IXEG_ATAlarm = dataref_table("ixeg/733/caution/caution_at_rst_act") --Creates the Lua magic metatable logMsg("AT Alarm value is " .. IXEG_ATAlarm[0]) -- Prints the current value of the dataref in the Log.txt file of xplane IXEG_ATAlarm[0] = 1 --Sets the value of dataref to 1 Note that you have to reference the table variable with a zero index for all datarefs that are not arrays. Also keep in mind that for this particular dataref when you set the value to 1 it is like pressing the button once, but it will stay in the pressed position. You have to set it back to 0 to release it again. The problem with this is that when you set it to 1 and then back to 0 in your script, the execution is so fast that it will in effect ignore the release of the button. You'll need a flight loop callback, keep track of when you've set the value to 1 and after enough time has elapsed (+- 100ms is usually enough), set the value back to 0. Hope this helps... PS: Maybe if you ask @Litjan nicely (again) they can look into adding some custom commands for cockpit builders to avoid having to use "workarounds".

It seems as though IXEG have not exposed these lights via datarefs. The majority of IXEG annunciators and indicators are exposed as datarefs with _ann or _ind at the end of the dataref name... but I couldn't find any for AP, AT and FMC alerts. Maybe if you ask @Litjan nicely they can look into adding it in a future update.

You must map your button in the X Plane menu to IXEG - 733 - autopilot - Disengage AT.

Hot Start TBM 900 "Boeing Style" Livery View File A fictional blue and white livery based on the Boeing style. To install, unzip and place in your X-Aviation TBM-900 livery folder. Submitter jfjoubert Submitted 04/12/2020 Category General Aviation Livery For http://www.x-aviation.com/catalog/product_info.php/take-command-hot-start-tbm-900-p-158 X-Plane Version(s) X-Plane 11