mtjoeng

Was searching quite a while for 'autobrake' but 'autoskid' was in the events.txt

have UseProfiles=Files my airplane profiles don't load very well - sometimes -, which I notice when taking off and using profile commands, I then have to pause the sim, open FSUIPC and click/check the 'ProfileSpecific' box. Any chance this is something specific, or just my installation quirk? using 7.3.7 (MSFS beta 10)

ok, now you have me really confused 🙂 its magic then, I'll check EDIT: not working anymore .. pff

The 'universal' TripleUse at Github showed a [auto] entry in the FSUIPC7.ini, u need that and the TripleUseAssignments.lua will work This is not in the download sample files! [Auto] 1=TripleUse now TripleUseAssignments.lua btnFunc = { { 6, 17, "_FLAPS_INCR", "_FLAPS_DOWN", "_FLAPS_UP"} } does that, single, double tap, long tap

Isn't this how it should be (almost)? MSFS shows the STD altitude while actual pressure is 30.16 and actual altitude is 41232 So before your ACARS recorded from P3D/FSX an adjusted output that transmitted (ATC) FL Now you either need to find a new output from MSFS that transmits FL or you have to calculate the FL from the true pressure altitude I'd say?

Testing TripleUse.lua load In the FSUIPC7.ini: [LuaFiles] 1=ipcReady 2=LINDA .. 10=TripleUse 11=Asobo737 .. ipcReady.lua ipc.runlua('linda') ipc.runlua('TripleUse') tried 2 buttons from 4=Logitech G940 Throttle and 6=DSD Flight Series Button Controller THUS line 21 / 22 in TripleUse.lua joy = 4 btn = 6 or the other one, these values the only changes in TripleUse.lua and per the FSUIPC button recognition: joy = 6 btn = 17 the default actions per TripleUse.lua tried in MSFS default B787 from default cockpit view: if timebutton(false) then -- First press / release counts: see if there's another if timebutton(true) then -- got another press in time, look for release if timebutton(false) then -- this was a double press, send VIEW RIGHT ipc.control(65676) end else -- This was a single press, send VIEW LEFT ipc.control(65680) ignorepress = false end else -- This was a longer press, send VIEW FORWARD ipc.control(65674) end does nothing what am I missing? ?

I think a 0-state read is missing in the latest LINDA file at the moment, only inc dec work (I notified on the forum)

7.3.4 loading ok here perhaps you try without a fsuipc ini file

What is your 'rotary' switch? Part of a button box, otherwise on a joystick? Use LINDA plug and play for windows devices. Install LINDA 4.1.4a https://www.avsim.com/forums/topic/583434-linda-414a-msfs-2020-compatible-4-mar-2022/ it will install linda.exe in your FSuipc folder Download and copy the folders of Beta PMDG 737 for MSFS v0.3 (17 May 2022) so these PMDG definitions are added to the LINDA subfolders https://www.avsim.com/forums/topic/618937-beta-pmdg-737-for-msfs-v03-17-may-2022/ Run LINDA after FSuipc is loaded, check joysticks LINDA found at first run, check if install is OK, go to your 'rotary' device, if you rotate, the interface will point to the action spots for Up and Down, now define the action in this case AUTOBRAKE, by clicking the interface action spot of the rotary, scroll PDMG module function, scroll down choose Autobrake, choose from the list of option Autobrake i.c. Increase, Autobrake Decrease etc, if you have spare buttons these can be dedicated selections (1 2 3 Max) This is the easiest.

You'd better ask John, I'm a cut and paste programmer 🙂 But basically the easiest format would be I saw somewhere else, indeed put the code in a 'pmdgautobrake.lua' file but then you need to add code that does the PDMG thing, use the <pmdgautobrake> parameter block to hop to the desired action. When 'pmdgautobrake.lua' is a recognizable macro file, with <pmdgautobrake> as the named macro you should find in the fsuipc dropdown, and then create the parameter list that reads the state first from a LVar (as per the example here), and then executes the necessary stops by control values. It's not easy, at all, but a lot easier if you know how it works, you start by dissecting sample files (ask John 🙂.

That's how i do things :). Of course you can. Depending on the state of your startup, mine is 'ready 'TAXI'' and has the autobrake in RTO, so my Voice command then when wheels off ground at the "positive rate" callout is, 'Autobrake off', that simply rotates 1 increase Up. VoiceAttack can also do a 'condition' which "0" is set at my flight start, so RTO would be this 0, Off would be 1, and calculates how many steps off the given condition are needed to get to the new position and make sure to assign the new condition for after.

function PMDG_MPNL_AUTOBRAKE_show () ipc.sleep(200) local Abtxt local ABpos = ipc.readLvar('switch_460_73X') if ABpos == 0 then Abtxt ="rto" elseif ABpos == 10 then Abtxt = "off" elseif ABpos == 20 then Abtxt = "1" elseif ABpos == 30 then Abtxt = "2" elseif ABpos == 40 then Abtxt = "3" elseif ABpos == 50 then Abtxt = "max" end DspShow ("ABRK", Abtxt, "AutoBrk", Abtxt) end function PMDG_MPNL_AUTOBRAKE_move (ABsel) if ABsel == nil then return end local ABpos = ipc.readLvar("L:switch_460_73X")/10 if ABpos > ABsel then for i = 1, (ABpos - ABsel), 1 do ipc.sleep(150) PMDG_MPNL_AUTOBRAKE_dec () end elseif ABpos < ABsel then for i = 1, (ABsel - ABpos), 1 do ipc.sleep(150) PMDG_MPNL_AUTOBRAKE_inc () end end end PMDG_EVT = 66587 is simply the standard msfs Rotor Brake control attached full file (still missing HUD controls, no one knows) LINDA PMDG actions.lua

I always peak in the LINDA cfg options.lua by ScotFlieger shows ways to do this (which myself I simplify or have VoiceAttack do the if-state-then for a execution) but this is full proper lua: -- ## Auto Brake -- 460 function PMDG_MPNL_AUTOBRAKE_inc () if ipc.readLvar("L:switch_460_73X") < 50 then ipc.control(PMDG_EVT, 46007) end PMDG_MPNL_AUTOBRAKE_show () end function PMDG_MPNL_AUTOBRAKE_dec () if ipc.readLvar("L:switch_460_73X") > 0 then ipc.control(PMDG_EVT, 46008) end PMDG_MPNL_AUTOBRAKE_show () end function PMDG_MPNL_AUTOBRAKE_cycle () if ipc.readLvar("L:switch_460_73X") < 50 then ipc.control(PMDG_EVT, 46007) else PMDG_MPNL_AUTOBRAKE_RTO () end end function PMDG_MPNL_AUTOBRAKE_RTO () if ipc.readLvar("L:switch_460_73X") ~= 0 then PMDG_MPNL_AUTOBRAKE_move (0) end DspShow ("ABRK", "RTO", "AutoBrk", "RTO") end function PMDG_MPNL_AUTOBRAKE_OFF () if ipc.readLvar("L:switch_460_73X") ~= 10 then PMDG_MPNL_AUTOBRAKE_move (1) end DspShow ("ABRK", "off", "AutoBrk", "off") end function PMDG_MPNL_AUTOBRAKE_1 () if ipc.readLvar("L:switch_460_73X") ~= 20 then PMDG_MPNL_AUTOBRAKE_move (2) end DspShow ("ABRK", "1", "AutoBrk", "1") end function PMDG_MPNL_AUTOBRAKE_2 () if ipc.readLvar("L:switch_460_73X") ~= 30 then PMDG_MPNL_AUTOBRAKE_move (3) end DspShow ("ABRK", "2", "AutoBrk", "2") end function PMDG_MPNL_AUTOBRAKE_3 () if ipc.readLvar("L:switch_460_73X") ~= 40 then PMDG_MPNL_AUTOBRAKE_move (4) end DspShow ("ABRK", "3", "AutoBrk", "3") end function PMDG_MPNL_AUTOBRAKE_MAX () if ipc.readLvar("L:switch_460_73X") ~= 50 then PMDG_MPNL_AUTOBRAKE_move (5) end DspShow ("ABRK", "MAX", "AutoBrk", "MAX") end BTW PMDG_EVT = 66587 which is the standard MSFS 'rotor brake' where PMDG puts its controls in the parameter of

That's the solution, cleared 123..0 I'll keep track of the MobiFlight HubHop preset list, thanks

Figured out how this events.txt file works (by comparing notes with the Mobiflight website). PMDG 737 is too WIP so some controls were missing but the solutions rather simple (if you know it it's simple) and added to the bottom of the events.txt f.i //PMDG/B737-700/MPNL PMDG_MPNL_AUTOBRAKE_inc#46007 (>K:ROTOR_BRAKE) PMDG_MPNL_AUTOBRAKE_dec#46008 (>K:ROTOR_BRAKE) //PMDG/B737-700/Additonal PMDG_GLSD_AP_P_reset#33901 (>K:ROTOR_BRAKE) PMDG_GLSD_AT_P_reset#34001 (>K:ROTOR_BRAKE) PMDG_GLSD_FMC_P_reset#34101 (>K:ROTOR_BRAKE) PMDG_GLSD_MCP_AP_BANK_inc#38902 (>K:ROTOR_BRAKE) PMDG_GLSD_MCP_AP_BANK_dec#38901 (>K:ROTOR_BRAKE) PMDG_GLSD_EFIS_FPV#36301 (>K:ROTOR_BRAKE) PMDG_OVHD_EXTLT_TURNOFF_LEFT_on#11501 (>K:ROTOR_BRAKE) PMDG_OVHD_EXTLT_TURNOFF_RIGHT_on#11601 (>K:ROTOR_BRAKE) This events.txt you said is going to be part of a next release. Please consider like Mobiflight does, to allow for a events.user.txt (or something) so to read a separate user added controls file. BTW the right modifier version FSuipc you let me test works like a charm, then again MSFS has the awful habit of having single key bindings 'bleed though' so most of right modifier bindings don't work because the single keystroke bleeds through, f.i. 12345..0 with right modifiers don't work for they will activate ATC option presses, and most alphabet do not either. The available somewhat 'free' keystrokes that work with rights bindings I found were F9 F10 F11 F12 ` ] [ \ ; mixed with RALT (fortunately Ralt works) RCTRL RSHFT this creates 60 something options for my Voiceattack PMDG macro commands, and I used them all.