Mixture lever in 114TC not working
-
Ron, in another thread you mentioned that your FSUIPC myevents.txt file already has a couple of Black Square mixture entries in it.
Iām working on a simple one-line fix that you should be able to paste straight into that file.
Can you copy and paste those existing Black Square mixture lines here?
I just need to see the numbers in them so I can make the new line match your setup exactly.
Just paste those lines here for now.
-
It's great you're hangin' in there Sad. I'll calm down once/if this weather ever gets sensible again. I'll leave it alone for a few days and come back to it.
-
Key binds to move a lever? If that's the case I won't bother to update. There comes a point when 'cleverness' sucks the fun out of things.
Can you hear that? It's the sound of the will to live going down the drain.
Yes, I'm a grumpy old man.@Ron-Attwood Perhaps some of you can give me some insight here. On every system, with every application I have tried, with every piece of hardware I have tried, the most basic native control binding for mixture has always worked. I have also tried
K:MIXTURE1_SETon every system I have had the opportunity to, and it has always worked without fail., including for condition levers. Yet, I still occasionally get complaints of these two "easy" methods not working, while the L:Var is included as backup. I know that doesn't help solve the immediate problem, but perhaps after three years, someone can help explain why this is happening? I would really appreciate any thoughts. -
@fredgarven Hi Fred. Yes I do, these are the entries in myentries.txt
// Blacksquare Duke Mixture
BS_Mixture_1#$Param 327.680 / 50 + (>L:BKSQ_MixtureLeverPosition_1)
BS_Mixture_2#$Param 327.680 / 50 + (>L:BKSQ_MixtureLeverPosition_2)
L:BKSQ_IgnitionPosition_1
L:BKSQ_IgnitionPosition_2
L:BKSQ_ConditionLever_0
Left Ignition Switch K:MAGNETO1_INCR/DECR - OR -
L:BKSQ_IgnitionPosition_1
Right Ignition Switch K:MAGNETO2_INCR/DECR - OR -
L:BKSQ_IgnitionPosition_2
Don't ask me how I got them, it was when I first got a BS something. This is getting very embarrassing. I have FSUIPC and have had it for years. All my axis, buttons and key presses are through it. When 2020 came along I was appalled at the control setup so everything went on FSUIPC.
Isaid I'd leave it alone for a while but needless to say I couldn't let it rest. Lo and behold BS_Mixture_1 suddenly worked! My head hurtsAs an experiment I'll go and try the FSUIPC settings again
I'll be back. -
Right. Both the Turbo and non Turbo work with BS_MIXTURE_1 via FSUIPC7
I'm now going to leave well alone.
I've not managed to satisfactorily get the magnetos to increase/decrease. They go from Off to Starter and from mag 3 to off. Not been able to do the old magneto test with them. Bonanza and 114
But that's for another day... -
@Ron-Attwood Perhaps some of you can give me some insight here. On every system, with every application I have tried, with every piece of hardware I have tried, the most basic native control binding for mixture has always worked. I have also tried
K:MIXTURE1_SETon every system I have had the opportunity to, and it has always worked without fail., including for condition levers. Yet, I still occasionally get complaints of these two "easy" methods not working, while the L:Var is included as backup. I know that doesn't help solve the immediate problem, but perhaps after three years, someone can help explain why this is happening? I would really appreciate any thoughts.@Black-Square I wish I had some real insight for you, but I don't. I own all of your planes except the Velocity. From the Dukes onward, I've used Axis and Ohs for control bindings, and it's always been a crap shoot. I always start with default MSFS events and vars to keep it as simple as possible. But every plane inevitably has some that don't work the way they should (or at least the way I expect), and that's the point where I dig into the assignments listed in the manual. For any of those that don't work, I use the dev menu behaviors tool, and the Axis and Ohs "watch simulator events" dialog. But they both have their own failings: the behaviors tool doesn't always list bindings, so I have to inspect the code displayed and try to glean what I can do from that. And the simulator events dialog sometimes displays native events that are being triggered by code -- and often I can't bind those events directly and the dialog doesn't indicate what to use. There are a couple other tricks I use in Axis and Ohs, and I'm always learning. For example, just a couple days ago, I discovered I can use to program virtual button presses on an axis I create (for the Just Flight F28, where the fuel levers are seemingly not on an axis).
Needless to say, due to the trial-and-error nature of this process, it sometimes takes a couple hours for me to bind a single plane, but it'd be awesome if I could just import an already existing control profile and have most of the assignments work out of the box.
Usually I start by binding just enough to get into the air, fly until I want to switch to autopilot, and then do the rest while the plane hums along happily on its own lol
-
@Ron-Attwood Perhaps some of you can give me some insight here. On every system, with every application I have tried, with every piece of hardware I have tried, the most basic native control binding for mixture has always worked. I have also tried
K:MIXTURE1_SETon every system I have had the opportunity to, and it has always worked without fail., including for condition levers. Yet, I still occasionally get complaints of these two "easy" methods not working, while the L:Var is included as backup. I know that doesn't help solve the immediate problem, but perhaps after three years, someone can help explain why this is happening? I would really appreciate any thoughts.@Black-Square Is it OK to use the default MSFS 2024 axis binding for mixture in the TC and normal variants? I believe the binding equates to AXIS_MIXTURE_SET.
I like to leave my axis bindings for the sim to look after and use MobiFlight for all my non axis controls.
-
@Black-Square Is it OK to use the default MSFS 2024 axis binding for mixture in the TC and normal variants? I believe the binding equates to AXIS_MIXTURE_SET.
I like to leave my axis bindings for the sim to look after and use MobiFlight for all my non axis controls.
@craighl4 That's absolutely the easiest thing to do. It's what I do, in fact
-
@craighl4 That's absolutely the easiest thing to do. It's what I do, in fact
@Black-Square Awesome. Thanks for confirming.
-
Is it feasible to bind the increase/decrease for the mixture to keypresses instead of a controller axis? I tried assigning it to every variation of Mixture 1 increase/decrease and couldn't get anything to work. The only thing that did have any effect was binding it to Mixture 1 axis. But I don't have an axis, so that's not particularly helpful.
-
@Woolies said in Mixture lever in 114TC not working:
I use the default Axis 0-100% for mixture no problems
I have apparently been using Mixture 1 Axis (-100 to 100) based on the bindings from the Bonanza that I copied for the Commander; an initial test showed that it seemed to work ok based on observed travel of the virtual lever and the engine running rough near cutoff, but I switched to Mixture 1 Axis (0 to 100) since the manual calls for the 0 to 100 values.
I'll have to fix that next time I fly my other Black Square planes.
-
@Woolies said in Mixture lever in 114TC not working:
I use the default Axis 0-100% for mixture no problems
I have apparently been using Mixture 1 Axis (-100 to 100) based on the bindings from the Bonanza that I copied for the Commander; an initial test showed that it seemed to work ok based on observed travel of the virtual lever and the engine running rough near cutoff, but I switched to Mixture 1 Axis (0 to 100) since the manual calls for the 0 to 100 values.
I'll have to fix that next time I fly my other Black Square planes.
@jmarkows I don't believe this is necessary. Nick confirmed that AXIS_MIXTURE_SET is OK to use. This equates to the -100 to 100% axis. I get full mixture lever travel when I use this axis.
I like to keep the same axis assignments for my different aircraft types (e.g. single prop airplane) to simplify my controller profiles in MSFS 2024. The MSFS aircraft such as the 172 need the -100 to 100 mixture axis to get full lever travel on my setup.
I then use MobiFlight for all non-axis assignments and have configurations per aircraft.
-
The mixture in the 114TC doesn't work with ctrl shift F2 or F3 to decrease it and increase it. The same is happening also to the non turbo Commander as well
@awash2002 It should work with all native bindings. Can you tell me specifically what you have bound to those keys?
-
Since the new patch, my standard mixture up/down binds that ive used for everything in 2024 and 2020 no longer work in the 114 turbo or non turbo. They still work in other planes Ive tried. I can still move the mixture with the mouse, but the binds dont work anymore. Buttons on my TWCS throttle bound to " decrease mixture" and "increase mixture". No external software involved. Sounds like same issue as @awash2002 but im curious if theirs worked before the patch.
-
Same. It worked for me earlier today since I bought the plane. This evening I found out there was an update. I installed it. The mixture is not working anymore. Thrustmaster Warthog HOTAS user. I mapped it to the Increase/Decrease Mixture, as I do for every GA plane with a mixture control. It was fine until the update.
-
Since the new patch, my standard mixture up/down binds that ive used for everything in 2024 and 2020 no longer work in the 114 turbo or non turbo. They still work in other planes Ive tried. I can still move the mixture with the mouse, but the binds dont work anymore. Buttons on my TWCS throttle bound to " decrease mixture" and "increase mixture". No external software involved. Sounds like same issue as @awash2002 but im curious if theirs worked before the patch.
@rinkerbuck Your post was a the key. I found the issue. It was a find-and-replace error. All bindings seem to be working again on my end. I'll publish an update asap for this. Thanks, everyone. Sorry for the mistake.
-
@rinkerbuck Your post was a the key. I found the issue. It was a find-and-replace error. All bindings seem to be working again on my end. I'll publish an update asap for this. Thanks, everyone. Sorry for the mistake.
@Black-Square default set pitot heat key-bind not working in 1.1 as well***
CPL MIFR š
-
yay! Thanks for your work on this.
