Jump to content
The simFlight Network Forums

mtjoeng

Members
  • Posts

    223
  • Joined

  • Last visited

Posts posted by mtjoeng

  1. 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)

  2. 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

  3. 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?

    On 2/14/2022 at 8:13 PM, chanchu81 said:

    The SUR Acars windows is the app developed by my team using the 0574 offset to record the altitud. but as you see when the Sim is in FL400, the SUR Acars is reading FL410.

     

  4. 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?

    ?

     

  5. 6 hours ago, John Dowson said:

    --
    -- Change the following to match your joysyick and button numbers
    --
    local myJoynum = 0 
    local myRtoButton = 0
    local myOffButton = 0
    local my1Button = 0
    local my2Button = 0
    local my3Button = 0
    local myMaxButton = 0

    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)

  6. 56 minutes ago, 737Andi said:

    I tried it with these presets..I assigned them to the different switch positions via fs control and Parameter "1".

    Unfortunately it did not work

    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.

     

  7. 29 minutes ago, 737Andi said:

    So if I put this lua file in my modules folder, have it automatically loaded via an entry in the FSUIPC.ini under [Auto] section and assign it to each position of my hardware rotary as .lua script it will work?

    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 🙂.

     

  8. 18 minutes ago, 737Andi said:

    My idea was to simply ignore the current rotary position by going to decrease as much as possible

    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.

     

  9. 19 minutes ago, John Dowson said:

    But that script/extract is also missing the functions
         PMDG_MPNL_AUTOBRAKE_move(numberOfpositions)
         PMDG_MPNL_AUTOBRAKE_show ()

    
    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

  10. 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

     

  11. 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.

     
     
     
     
     
     
     
     
     
  12. ..\pmdg-aircraft-737\Documentation\PMDG\PMDG_NG3_VC_700.xml
    is too complex

    the action.lua is a lot easier to extract from

    The parameters are from the yesterday released LINDA module Beta PMDG 737 for MSFS v0.3 (17 May 2020) action.lua
    "<X>:\FSUIPC7\LINDA\aircrafts\PMDG 737\actions.lua"

    https://www.avsim.com/forums/topic/618937-beta-pmdg-737-for-msfs-v03-17-may-2020/
    by ScotFlieger

     

     

     

  13. How do I/what's the simplest to create PMDG events functions list/file/luas/mcro to assign in Fsuipc (I'm a bit confused and rusty)
    extracting is possible from LINDA PMDG action.lua, the ipc.control parameters for PDMG rotor brake (PMDG_EVT 66587)

    useful f.i.:
    PMDG_GLSD_MCP_AP_VNAV    38601
    PMDG_GLSD_MCP_AP_LVLCHG    39101
    PMDG_GLSD_MCP_AP_HDGSEL    39201
    PMDG_GLSD_MCP_AP_LNAV    39701
    PMDG_GLSD_MCP_AP_VORLOC    39601
    PMDG_GLSD_MCP_AP_APP    39301
    PMDG_GLSD_MCP_AP_ALTHLD    39401
    PMDG_GLSD_MCP_AP_VS    39501
    PMDG_GLSD_MCP_AP_CMDA    40201
    PMDG_GLSD_MCP_AP_CMDB    40301
    PMDG_GLSD_MCP_AP_CWSA    40401
    PMDG_GLSD_MCP_AP_CWSB    40501
    PMDG_GLSD_MCP_AP_TOGA    68401
    PMDG_GLSD_MCP_AP_MASTER_on    40601 (toggle)
    PMDG_PED_ENG1_cutoff    68801
    PMDG_PED_ENG2_cutoff    68901
    etc

    I don't think I have to read the LVar state, just want push the button

     

  14. I 'll do a new post but I can extract ipc.control parameters from the LINDA PMDG action.lua (and keep the nameing),
    and then don't know how to go about it 🙂 PDMG rotor brake (PMDG_EVT 66587)
    f.i.
    PMDG_GLSD_MCP_AP_VNAV    38601
    PMDG_GLSD_MCP_AP_LVLCHG    39101
    PMDG_GLSD_MCP_AP_HDGSEL    39201
    PMDG_GLSD_MCP_AP_LNAV    39701
    PMDG_GLSD_MCP_AP_VORLOC    39601
    PMDG_GLSD_MCP_AP_APP    39301
    PMDG_GLSD_MCP_AP_ALTHLD    39401
    PMDG_GLSD_MCP_AP_VS    39501

     

  15. (Test fresh Reboot, WASM list shows up first check)
    (my Windows 10 PC does weird sometimes with 150 Firefox tabs open, after long documents, a spreadsheet, a couple of video's running and a list of background operations and such)

    for instance LAlt+RShift+RCtrl+Z set to trigger Cessna 414 Lua Control Autopilot Toggle works OK
    tested a dozen more
    my Logitech keyboard has a right "Alt GR" key, that works,
    f.i LAtl+RAlt+R set to trigger Cessna 414 Lua Control Auto Altitude Arm Toggle works OK

    (Set Alt+F / Ralt+F does not work, triggers FSUIPC window 🙂)

    ample possibilities now, I'll reprogram and add to my VoiceAttack profile, everything seems to work

    great job THX

    Downloaded v7.3.4d

     

  16. downloaded, random quick tests on the ground, seems to work

    (had some weird path issue, WASM not listing,

    had to click Filemanager (TotalCommander) to enter folders /Utils /EventFiles /HvarFiles - FSUIPC_WAPID.dll path? - after which lists showed up,

    I'll check some more with system reboot later, prob that, flysimware aircraft cessna 414a uses list of LVar command in Lua control file, and does not work with this WASM error, but does when folders accessed - ? how ? - )

    Thx better test tonight after system Reboot

  17. This is for use with VoiceAttack voice commands. VoiceAttack uses only Left/Right- Shift Control Alt Win modifiers, Tab and Menukey are simply secondary keys in VoiceAttack and Winkey not quite usable in Windows 10 because of the added Windows 10 Winkey shortcut keys (Taskbar progs), which leaves only 3 usable Left modifiers, which run short when one wants to make easy rememberable shortcuts with alphabet reference.

    Is why.

     

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.