Jump to content
The simFlight Network Forums

Cuantreau

Members
  • Posts

    89
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Cuantreau

  1. 23 minutes ago, John Dowson said:

    This is not correct. Why don't you consult the documentation if you do not know how to use a facility before posting....
    The correct format should be:

    [Auto.PMDG 737-700]
    1=Lua PMDGAutoBrake

    In your lua file,why didn't you just change the variables at the top of the file? Doesn't really matter, but you didn't change the last event.button call:
     

    That last one should probably be:
        event.button(4, 135, "PMDG_MPNL_AUTOBRAKE_MAX")\

    Any further issues, try looking at the documentation first, and also check your log file (you can add appropriate logging) which should tell you what is happening.

     

    Ok John, will try, thanks a lot

  2. 9 hours ago, John Dowson said:

    First, use the number for your device - I suspect that it is 0, but you can confirm by looking at the  joy letter / id mapping in the [Joy\names] section of your FSUIPC7.ini.
    Second, the lua must be auto-ran - add it to your [Auto] section, or, better still, your [Auto.xxx] section (where xxx is the name of the profile you use for the PMDG 737).
    You do not need  to make any assignments to the lua. Anu issues, activating logging for Lua Plugins and show me your FSUIPC7.ini and FSUIPC.log files.

    Not 100% sure what this means, but looks ok to me. keep this thread updated if you hear anything, thanks.

    Ok John, for the number (it's 4).

    For the second part I've added

    [Auto.PMDG 737-700]
    1=PMDGAutoBrake.lua

    Here are the files including my edited PMDGAutoBrake.lua one

    Thank you very much

    PMDGAutoBrake.lua

  3. 7 hours ago, John Dowson said:

    No. If the lua is auto-running, why assign a button to start it? You cannot assign a button to a function in a lua script.
    To use the lua, you need to add some event.button calls which would call the appropriate lua function when one of your rotary buttons was detected.
    I have put together a script for you to try this - download to your FSUIPC7 installation folder and change the following variables to match your hardware:
        

    The script should be auto-started, preferably from a PMDG profile section: PMDGAutoBrake.lua

    (NB. script not tested as I don't have this aircraft!]

    What happened? Did you look at the log or try logging *Buttons & Keys + Events) to see what is happening? There is no point just saying 'it doesn't work'...
    Also, if writing your own presets, you should test the calculator code first using the Add-ons->WASM->Execute Calculator Code menu option, to check that it has the desired affect.

    Otherwise you could follow the advice of @mtjoeng and install LINDA...

    Hello John, I tried with the PMDGAutoBrake.lua you provided, can't seem to make it to work. This is what I'm doing. Copy the .lua to FSUIPC install folder, edit it by replacing myJoynum with A (which is the letter shown when I press the button I wish to assign in fsuipc with running sim), replace myRtoButton with 30, myOffButton with 31, etc. Then look for the PMDGAutoBrake.lua from Select for FS Control ticked and find it in "control sent when button pressed" section. But the rotary switch I use is not responding to that. What am I doing wrong here? Thx.

  4. 15 minutes ago, John Dowson said:

    There is an Export presets button at the bottom of the search grid - I presume you can use that, although I have never tried.

    You shouldn't modify the events.txt file, as ant changes will get overridden when you next install FSUIPC7. If you want to add events, use the myevents.txt file. However, you can just use the update events.txt file I posted earlier, as suggested by @adnanso. This will be included in the next FSUIPC7 update, hopefully tomorrow but maybe the day after.

    Event files are different - these are for custom events. You could use these, but you would then also need to install the MobiFlight WASM module which handles these. Presets are an alternative that are executed by the FSUIPC WASM module.

    John

    Thank you John, always so helpful man!

  5. On 5/14/2022 at 6:56 PM, adnanso said:

    Hello @Cuantreau I've added the events you are asking for to the Mobiflight Contribution website  around the same time you created this topic 😉

    PMDG_B737-7_FUEL_CUT_OFF_LEVER1_DN#(L:switch_688_73X) 100 div 0 == if{ 68801 (>K:ROTOR_BRAKE) }
    PMDG_B737-7_FUEL_CUT_OFF_LEVER1_UP#(L:switch_688_73X) 100 div 1 == if{ 68801 (>K:ROTOR_BRAKE) }
    PMDG_B737-7_FUEL_CUT_OFF_LEVER2_DN#(L:switch_689_73X) 100 div 0 == if{ 68901 (>K:ROTOR_BRAKE) }
    PMDG_B737-7_FUEL_CUT_OFF_LEVER2_UP#(L:switch_689_73X) 100 div 1 == if{ 68901 (>K:ROTOR_BRAKE) }

    just add them to your ...\FSUIPC7\events.txt and voilà ! also,  if my undesrtanding is good, they will be automatically included with the next FSUIPC update.

    adanso, couldn't get them to work, I added to the events .txt file in fsuipc folder, but shouldn't there be an .evt file for that to work in the EventFiles folder? thanks

  6. On 5/14/2022 at 6:56 PM, adnanso said:

    Hello @Cuantreau I've added the events you are asking for to the Mobiflight Contribution website  around the same time you created this topic 😉

    PMDG_B737-7_FUEL_CUT_OFF_LEVER1_DN#(L:switch_688_73X) 100 div 0 == if{ 68801 (>K:ROTOR_BRAKE) }
    PMDG_B737-7_FUEL_CUT_OFF_LEVER1_UP#(L:switch_688_73X) 100 div 1 == if{ 68801 (>K:ROTOR_BRAKE) }
    PMDG_B737-7_FUEL_CUT_OFF_LEVER2_DN#(L:switch_689_73X) 100 div 0 == if{ 68901 (>K:ROTOR_BRAKE) }
    PMDG_B737-7_FUEL_CUT_OFF_LEVER2_UP#(L:switch_689_73X) 100 div 1 == if{ 68901 (>K:ROTOR_BRAKE) }

    just add them to your ...\FSUIPC7\events.txt and voilà ! also,  if my undesrtanding is good, they will be automatically included with the next FSUIPC update.

    Thanks man, will check it out.

  7. 4 hours ago, John Dowson said:

    Did you check the SDK, or list the lvars to see what is available? Controls for the MSFS version of the PMFG 737 may not be the same as used by the P3D version.
    There doesn't seem to be much for the auto-brake on the MF HubHop preset list at the moment, just one that shows the following lvar for the AutoBrake Disarm Annunciator State: L:switch_459_73X

    John

    John, MSFS or PMDG's SDK? Thanks

  8. On 5/14/2022 at 10:03 PM, johnk515 said:

    In my P3D 4.5 PMDG 737, I have a spreadsheet that has to control codes for all the PMDG 737 events.  Unfortunately I can't get them to work in msfs 737. In P3D I could either use a toggle switch or on/off switch I.E. anti coalition lights event ID 69757.  It works great there, only if they would work in msfs.

    Yes, same thing for the autobrake, can't map them as i did in p3d.

  9. 38 minutes ago, Andre92 said:

    I use the a button for the fuel levers. The honeycomb throttle has a detent at the bottom part of all throttles/axis which triggers a button.

     

    125=PL,24,C66587,68801 	-{ROTOR_BRAKE}-
    126=UL,24,C66587,68801 	-{ROTOR_BRAKE}-
    127=PL,27,C66587,68901 	-{ROTOR_BRAKE}-
    128=UL,27,C66587,68901 	-{ROTOR_BRAKE}-

    It looks like this in my ini file (Buttons section), where L is the letter assigned to my Honeycomb throttle on my setup.

    Andre

    Thanks a lot Andre, will make it work

  10. 4 hours ago, Andre92 said:

    So had some spare 30 minutes to try again.
    The Throttle 1 Dec (and #2) does work. I believe you have to add a parameter (not 0), for it to work.

    I've now set it up on my Honeycomb Throttles to have a single Throttle 1 dec when the reverse levers are pulled, this gives you idle reverse. When pulling the throttles through the detent, Throttle 1 dec is pressed repeatedly, so you get full reverse. This allows you to choose between idle and full reverse.
    When the reverse lever is released Throttle 1 cut stows the reverser.

    I programmed the fuel lever (idle cutoff) on the detent of axis 2 and 5. On press and release of the detent button they are toggled.

    André

    Andre, so your fuel levers a axis or a single button for each lever like mine? Didn't get how you did it? Could you elaborate a bit more please, thanks man.

  11. 8 hours ago, Andre92 said:

    Hello,

    Struggling with the 737 as well..:-)

    The reverser works for me when i assign it on an Axis as described above (direct to FSUIP Calibration). Setting a button to Engine 1 dec does not work for me (which normally works on other planes). I will experiment some more when i have the time.


    The fuel lever / idle cutoff can be toggled through the Rotor brake function.
    Fuel lever 1 is 688
    Fuel lever 2 is 689.

    To assign a toggle function for this, assign the Rotor Brake to a button with the parameter 68801 or 68901.
    The 01 means left mouse click.

    You can download an Excel file with all the event numbers here:
    https://forum.pmdg.com/forum/main-forum/pmdg-737-for-msfs/182499-737-lvars-simevents-etc-list

     

    Kind Regards,
    Andre

    Andre, you're the man !!!!!!!!! Thanks so much man, how did you find this?. Fuel levers where the last buttons that I was missing in my throttle quadrant assignments.

  12. 3 minutes ago, John Dowson said:

    Thanks @Cuantreau - that looks like a pretty standard throttle config for jets with a button to activate reversers (rather than using an axis), so I am surprised others are having difficulties. The only difference to a standard set-up is in using Throttle Set with a parameter of -1 rather than Throttle Cut, but I guess that does the same thing...

    You are welcome, the idle/cutoff for the start levers was a no go unfortunately. Tried all fuel and mixture MSFS keyboard assignments but none worked, so couldn't assign them to FSUIPC obviously.

  13. This is my throttle quadrant (throttletek with button reversers not axis) config through FSUIPC. Note on the last pic, that's how i configure the button reversers to my liking, what throttle set with -1 on parameters give me is the ability to set reversers and choose whether to leave them and they'll increase to max (81% aporx), or release them as soon as i set them, that keeps them in idle until i vacate the runway, then when i want them off i set the thrust a bit and they retract/close. Hope it helps. Will try your suggestions John and let you know. Thanks a lot.

    Untitled.png

    Untitled1.png

    Untitled2.png

    Untitled3.png

    • Like 1
  14. 6 minutes ago, hvw said:

    Let's just wait and see what happens then. I kept on trying to assign the throttle in the same way as I did under P3D/FSX as it worked perfectly there with the help of FSUIPC of course, till I found out this to be impossible in MSFS' 737. I now will use my joystick's throttle in such a way that I only can use thrust idle and up to max thrust forward. The reversers I will activate through the F2 key. When I will be using the 737 that is, I still do prefer the FBW A320Neo 🙂 . Thanks, John

    I could do it the exact same way I did it in p3dv5 and fsx as you said. Had no issues whatsoever to make them work with MSFS and the 737-700.

  15. Hi John , firstly thanks for the quick reply, you and your brother are awesome. Secondly, I have no issues with throttles assignment and calibration through FSUIPC, it's the fuel cutoff and idle lever in the new aircraft and the impossibility to assign them to a button that could trigger them, but that would need an SDK release by PMDG I suppose. Hope you can get it before we do and work to add the off-sets. Thanks again very much!

  16. 2 hours ago, dafyddp3d said:

    Hi Fabio

    Quick query - I've just installed version 4.5.2201.12 on my p3d m/c, but the enhanced and standard P3D versions are showing version 4.5.2112.10. The MSFS version correctly shows version 4.5.2201.12. I'm assuming all three files should be the same version number.

    Cheers

    Dave Nash

    Edit - Correction, the standard version shows as 4.5.2102.9

    My 4.5.2201.12 installation is also showing old versions for the three sims, none is showing this new installed v.4.5.2201.12

     

×
×
  • 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.