Ch.Cole

I mean... did you even look at the topics in the forum? the issue was there, even in the title... By the way, it's "should have", not "should of".

re 3) check with the TQ viewer that your hardware and in-cockpit levers are not out of synch (the line should be in the box). Otherwise you can't move them. That's intended, I think.

3) seems to be correct according to archen on discord. Pilot Altimeter is digital, the other two are mechanical.

Hi, I threw together a script vor the BN2T that implements an idle detent. How to use: - copy the script to your FlyWithLua script folder - assign Throttles 3 and 4 for left and right engine - assign a button to FlyWithLua/BN2T/detent_pressed (Press Throttle Detent) Notes: -Due to X-Plane, this only works correctly with running engines -I've implemented a warning "Check throttles" that pops up if your Hardware throttles are below idle and the levers are still on the idle stop. You can remove that by commenting line 49 by putting double dashes in front of do_every_draw("write_idle_warning()") Feedback is welcome! PS: If you only have one axis available, use the -one axis.lua and assign Throttle 5 BN2T-Throttle.lua BN2T-Throttle-one axis.lua

I think he's not talking about the ALT preset, but the minimums.

Check my lua-script

Having a Honeycomb Alpha, I was surprised that I could only bind toggle commands for the lights, which can lead to hardware/cockpit desynchronisation. So I made the attached script. It allows you to assign on and off to: - both landing lights combined - Taxi, Nav, Beacon, Strobes, Wing The commands can be found under FlyWithLua/SF34/ SF34 Lights Commands.lua

I wrote a script for myself. Assign Prop 3 and 4, not 1 and two, and adjust your deadzones. Feel free to ask if you need further information. SF34_Condition_Levers.lua

Try this. I assume you have flywithlua installed? The command is FlyWithLua/SF34/Hold_Brakes_reg . SF34 Commands.lua

Would a lua-script help you, that holds the brakes while a button is pressed help you?

Besause that does not work, as far as I tested. You have different commands. change the airspeed in IAS and the VS in VS-mode.

Hi, I threw together a quick script that allows you to bind two commands (FlyWithLua/SF34/PitchWheel_up and ..dn) to a button that allow you to simulate the pitch wheel in both IAS and VS mode. Minor issue is that the IAS gets changed in increments of 2kts. Solved with update, see below. Feedback is welcome.

That't typical behaviour for carburettor icing, which obviously depends on weather. you can have carb icing at 15C on low throttle settings. this lua-script pops up values is you have carb icing, or you can assign the command FlyWithLua/BN2P/Toggle_CarbIceDisplay to display it constantly. if PLANE_ICAO == "BN2P" then CarbIce = dataref_table("sim/flightmodel/engine/ENGN_crbice") create_command("FlyWithLua/BN2P/Toggle_CarbIceDisplay", "Toggles the CarbIceDisplay", "CI_displaytoggle()", "", "") showCID = 0 function CI_displaytoggle() if showCID == 0 then showCID = 1 else showCID = 0 end end function show_CarbIce() if showCID == 1 or (CarbIce[0] + CarbIce[1]) > 0.02 then draw_string(50, 70, "L Carb Ice: " .. math.floor(CarbIce[0]*1000)/1000) draw_string(50, 50, "R Carb Ice: " .. math.floor(CarbIce[1]*1000)/1000) end end do_every_draw("show_CarbIce()") end Carb icing is most pronounced in high humidity air with low throttle settings.

You could use DataRefTool and go hunt the datarefs and commands yourself. If there are any you can't find, just post them here, and we can help you find them.

Did you try the lua-script? You can also use it to get the axis values.

Thanks for the warning. I was trying to use Murphy's law, as in "Great, the day after I wrote this script the update is out and all was for naught"

NewSaab version out, doesn't work any more. Does anyone have need for this anyway? The attached lua file binds the PL friction lever to the Prop 3 axis and the CL friction lever to the Prop 4 axis. Just drop the file into the scripts folder of flywithlua. If you have problems, uncomment the line that says "do_every_draw", (remove the "--") so that you can see the values on screen. This will help finding the cause.

If he had stopped after the first sentence, I had agreed. The next two, I wholeheartedly disagree with, though

Did you try the script as-is? The 28 should just be the internal axis number X-Plane assigns to the Mixture 1 (the "1" is important!) axis, so no need for you to change it. If it doesn't work, you can remove the two dashes in line six in the lua-file (in front of do_every_draw), so you get a raw data output on the left side of the screen that will help us to find the issue.

So Mixture for cut off - lo idle - hi idle Prop to move to flight idle Throttle for rev-taxi-flight? Would be possible, I think. What should happen if prop says flight idle but mixture says low idle? What should happen if prop says idle but the throttle is not in idle?

Hi, I don't quite understand what you are trying to do. What do you want to use the Prop axis for? Do you want to use the mixture axis and the prop axis as well as the throttle axis all to control one virtual lever?

It was either trying to increase your pitch in pitch mode, or your v/s in v/s mode. Since both didn't increase, it continued to trim up. Basically, it's expected behaviour.

Why would you activate the AP on the ground? Obviously your pitch won't change with the trim, so the AP tries to trim more.

Allt the commands are "assignable" in the config window for your controllers, aren't they?

I don't quite understand... Just yesterday I bound switches like the fuel pumps or the lights to on/off switches. What exactly are you trying to do?