March 25, 20242 yr I can’t find support page from manufacturer so I’m here asking now. I have my bravo TQ mapped in FSUIPC. I’ve tried axis conditioner 1 set and axis mixture 1 set. No bindings in MSFS controls. The mixture will not leave cutoff unless I manually just click the up arrow. Can somebody help me.
March 25, 20242 yr I use Spad.next and had the same issue. I believe the solution I implemented is this one below (from a user called Ape42, who posted the solution on a forum somewhere, but I don't actually know where it was... it was a partial screenshot I'd saved to my phone many months ago): Sorry! @JYW was right... This is the incorrect snippet. See my solution a few posts down: Edited March 25, 20242 yr by Redge Right info!
March 25, 20242 yr Despite hours of messing with it, I've never manged to assign the condition lever in the BSq TBM850. It's the first lever I've never been able to crack in terms of assigning it to my hardware. 😡😄 (This is with Lorby AAO). Really bugs me having to click an axis lever with the mouse, but I've learned to live with it. Bill 😎FS2024 • Currently in 'GA mode' : A2A Comanche 2024 & Aerostar • Black Square C208, Bonanzas, Barons, TBM850, Dukes • COWS DA40 & DA42 • Bluesky Grumman AA5 • FSW Legacy, C24R Sierra & C414 • Echo Falco F8L • FFX HJET, Visionjet and P180 2024 • Got Friends A32 Vixxen • FSReborn Sirius TL3000, Sting S4 and Piper M500 • Flyboy Rans S6S • Skyward DA50RG • SWS Zenith CH701, RV-8, RV-10, RV-14, PC12 • Milviz C310R • Air Foil Labs Bristell B23 TrackIR • BeyondATC • PMS GTN Payware • RealTurb • Axis & Ohs • FS Realistic Pro9800X3D • RTX 3080 • 64GB DDR5-6000Former PPL IR, grounded by diabetes. Now UK NPPL(M)
March 25, 20242 yr 24 minutes ago, Redge said: I use Spad.next and had the same issue. I believe the solution I implemented is this one below (from a user called Ape42, who posted the solution on a forum somewhere, but I don't actually know where it was... it was a partial screenshot I'd saved to my phone many months ago): What you quoted seems to be about state saving rather than being able to assign the condition lever to a hardware axis? Or have I missed something? If you add those pieces of code, what variable do you then set your hardware axis to? Would love to get it working and be able to assign the lever 👍 Edited March 25, 20242 yr by JYW Bill 😎FS2024 • Currently in 'GA mode' : A2A Comanche 2024 & Aerostar • Black Square C208, Bonanzas, Barons, TBM850, Dukes • COWS DA40 & DA42 • Bluesky Grumman AA5 • FSW Legacy, C24R Sierra & C414 • Echo Falco F8L • FFX HJET, Visionjet and P180 2024 • Got Friends A32 Vixxen • FSReborn Sirius TL3000, Sting S4 and Piper M500 • Flyboy Rans S6S • Skyward DA50RG • SWS Zenith CH701, RV-8, RV-10, RV-14, PC12 • Milviz C310R • Air Foil Labs Bristell B23 TrackIR • BeyondATC • PMS GTN Payware • RealTurb • Axis & Ohs • FS Realistic Pro9800X3D • RTX 3080 • 64GB DDR5-6000Former PPL IR, grounded by diabetes. Now UK NPPL(M)
March 25, 20242 yr @JYW - you're right, that was the incorrect snippet. Sorry! @steelrfan85 - I applied the fix a long time ago, so had forgotten what I actually did. But I've found the solution: I use vJoy to assign the following key commands (each to a different vJoy "button"): CONDITION LEVEL 1 CUT OFF - vJoy Button #2 CONDITION LEVER 1 LOW IDLE - vJoy Button #3 CONDITION LEVER 1 HIGH IDLE - vJoy Button #4 In Spad, I then have the following logic (in pseudo code): If MIXTURE_AXIS <= 25 (SET LVAR:CONDITION_LEVER_CUTOFF_1 to 0) && (SEND SET_FUEL_VALVE_ENG1 Event 0) && (Press & Release vJoy Button #2) If MIXTURE_AXIS >= 26 && MIXTURE_AXIS <=74 (SET LVAR:CONDITION_LEVER_CUTOFF_1 to 1) && (SEND SET_FUEL_VALVE_ENG1 Event 1) && (Press & Release vJoy Button #3) If MIXTURE_AXIS >=74 (Press & Release vJoy Button #4) I hope this helps! Edited March 25, 20242 yr by Redge
Archived
This topic is now archived and is closed to further replies.