Jump to content
The simFlight Network Forums

asessa

Members
  • Posts

    91
  • Joined

  • Last visited

Posts posted by asessa

  1. 13 minutes ago, John Dowson said:

    That is quite old now. Latest official version is 7.0.7 (released this morning). I have also released 7.0.8a, a beta release with native support for up to 128 buttons  - see Announcements if interested in that.

    John

     

    wow , i just updated it to 7.0.6 yesterday night 🙂

  2. 1 hour ago, MarkStallen said:

    The offset 0C46 does not work with A320 FBW nor 0C47

    It works only if you push button in sim.

    In this way i have Abrake led ON lighted-on and DECEL light-on when it decelerate at landing.

    If i push button on my panel i have Abrake led ON lighted-on in sim nor on panel and DECEL doesn't work.

    I will have to try to add custom LVARS to MF , it now possible but i have to study how 😄 

  3. 25 minutes ago, Alemonb said:

    Ok, for the inputs I used your way with events in MF and it works fine now.

    I just already have the issue with DECEL lights that doesn't bright. Tried 0x0C46 & 0x0C47 without any success.

    For decel this work for me

    ABRK LO DECEL= FSUIPC Offset 0x0C46 , Trasform = if($=1,1,0) , PRECONDITION ABRK LO ON = 1
    ABRK MED DECEL= FSUIPC Offset 0x0C46 , Trasform = if($=1,1,0) , PRECONDITION ABRK MED ON = 1
    ABRK MAX DECEL = FSUIPC Offset 0x0C46 , Trasform = if($=1,1,0) , PRECONDITION ABRK MAX ON = 1

  4. 7 hours ago, Alemonb said:

    Hello,

    I've downloaded last version of FSUIPC 7.0.6 (1st march 2021) and try to set AUTOBRAKES LO/MED/MAX working with DECEL lights on MSFS 2020 (1.14.5.0 last version).

    But I have two troubleshooting :

    1. When I set AUTOBRAKES from OFF to MED or MAX it always set firsto to LOW. I have to set again to MED or MAX and it works fine at the second times.
    2. I don't have DECEL light even if in MSFS 2020 it lights on.

    I use the exactly same configuration than asessa (excepted for LED ON but normaly no impact on my issues) :

    INPUT

    ABRK LO = FSUIPC Offset 0x2F80 , Set Value  = if($=0,2,0)
    ABRK MED = FSUIPC Offset 0x2F80 , Set Value  = if($=0,3,0)
    ABRK MAX = FSUIPC Offset 0x2F80 , Set Value  = if($=0,4,0)

    OUTPUT 

    ABRK LO ON= FSUIPC Offset 0x0260 , Trasform  = if($=1,1,0)
    ABRK MED ON= FSUIPC Offset 0x0260 , Trasform  = if($=2,1,0)
    ABRK MAX ON = FSUIPC Offset 0x0260 , Trasform  = if($=3,1,0)

    ABRK LO DECEL= FSUIPC Offset 0x0C46 , Trasform = if($=1,1,0) , PRECONDITION ABRK LO ON = 1
    ABRK MED DECEL= FSUIPC Offset 0x0C46 , Trasform = if($=1,1,0) , PRECONDITION ABRK MED ON = 1
    ABRK MAX DECEL = FSUIPC Offset 0x0C46 , Trasform = if($=1,1,0) , PRECONDITION ABRK MAX ON = 1

    Thanks for your help,
    Alexis

    With which aircraft and version of it ?  
    I noted it doesn't work now with A320Nx custom AP version

  5. 22 hours ago, John Dowson said:

    I think that's up to them. The problem is that all MF users aren't necessarily FSUIPC users (and vica-versa).

    I think the best long term solution would be (barring MSFS providing direct access to lvars via SimConnect!) for a single open-source WASM module that provides access to lvars/hvars and also does event processing. Basically a combination of the functionality offered by the MF WASM module and the FSUIPC one.

    Yes . The last version of MF give us the possibility to fireup MSFS/A320nx/CJ4 events directly, but for output it use fsuipc offset.

    So the problem is read the value from sim for the custom lvar.

     

  6. 1 hour ago, John Dowson said:

    Yes, shouldn't be a problem to use this with any other WASM module. If any other WASM module is using the same event numbers as the FSUIPC WASM then that will cause problems. However, if that occurs, you can change the event numbers that the FSUIPC WASM uses via the ini files. Not needed for the MF WASM.

    Ok thanks, i will do a check in the weekend.

    I think also MF should update its software to read lvars from fsuipc, do you think?

  7. 30 minutes ago, MarkStallen said:

    The chronometer and the landinggear and brake lights coming from a Visual Basic Program working with FSUIPC.

    Be sure that in your events.txt contains :

    XMLVAR_Autobrakes_Level_OFF#0 (>L:XMLVAR_Autobrakes_Level)
    XMLVAR_Autobrakes_Level_LOW#1 (>L:XMLVAR_Autobrakes_Level)
    XMLVAR_Autobrakes_Level_MED#2 (>L:XMLVAR_Autobrakes_Level)
    XMLVAR_Autobrakes_Level_MAX#3 (>L:XMLVAR_Autobrakes_Level)

    Then it works. (You can't give a parameter, but you have to use all the commands seperate)

    Ok, i will try 

    Thanks

  8. 17 minutes ago, MarkStallen said:

    For the pop-outs I use Window Title changer and Win Layout manager. When I start-up I have to pop-out the panels all together after that pop-out apart and give them a name (1,2, 3--6) with Title changer. Then in lay-outmager I saved those names with their position and size so I can run that preset. Costs about one minut.

    Thanks , i will try 

  9. On 3/3/2021 at 3:45 PM, MarkStallen said:

    Here they are :

    MSFS2020 - MobiFlight WASM Events - Google Spreadsheets

    for instance in events.txt in the community/mobiflight-event-module/modules:

    XMLVAR_Autobrakes_Level_MED#2 (>L:XMLVAR_Autobrakes_Level)

    A320_Neo_PFD_BTN_LS_1#(>H:A320_Neo_PFD_BTN_LS_1)

    in the evt-file call them with :

    XMLVAR_Autobrakes_Level_MED

    A320_Neo_PFD_BTN_LS_1

    It's not possible to give a parameter by yourself. I'm using custom offsets to keep up.

    If you open op the aircraft behaviours in the developermode. Then you can find all LVars and Hvars used and put them in the events.txt and xxxx.evt als described above. Everything is now working on my DIY cockpit. All buttons, switches and roterary's. Lights like LDG gear and Auto brk etc. I programmed via Visual Basic and FSUIPC. 

     

    plate.jpg

    thumbnail_20210303_130328.jpg

    Hi Marks, i'm using the XMLVAR_Autobrakes_Level_xxx with MF and my Autobrake Panel and A320Nx Custom AP+FBW but :

    XMLVAR_Autobrakes_Level_MED activates the LOW button

    XMLVAR_Autobrakes_Level_MAX activates the MED button

    For MAX i have to use the fsuipc event Autobrake with value of 4.

    Can you confirm ?

    ps.

    Great home cockpit's set! Ho do you popup that chronometer texture?

    And Do you know a method to save all popuped windows so i haven't to popup they at every flights?

     

  10. Hi this is my conf : 

    INPUT:

    ABRK LO = FSUIPC Offset 0x2F80 , Set Value  = if($=0,2,0)
    ABRK MED = FSUIPC Offset 0x2F80 , Set Value  = if($=0,3,0)
    ABRK MAX = FSUIPC Offset 0x2F80 , Set Value  = if($=0,4,0)

    OUTPUT 

    ABRK LO ON= FSUIPC Offset 0x2F80 , Trasform  = if($=2,1,0)
    ABRK MED ON= FSUIPC Offset 0x2F80 , Trasform  = if($=3,1,0)
    ABRK MAX ON = FSUIPC Offset 0x2F80 , Trasform  = if($=4,1,0)

    ABRK LO DECEL= FSUIPC Offset 0x0C46 , Trasform = if($=1,1,0) , PRECONDITION ABRK LO ON = 1
    ABRK MED DECEL= FSUIPC Offset 0x0C46 , Trasform = if($=1,1,0) , PRECONDITION ABRK MED ON = 1
    ABRK MAX DECEL = FSUIPC Offset 0x0C46 , Trasform = if($=1,1,0) , PRECONDITION ABRK MAX ON = 1

    Hope it help you

    Regards

     

  11. 9 minutes ago, MarkStallen said:

    Would be very nice. But if you mean by "pushing in the sim" that you select these on the microsoft simulator screen, that works for me too. I was selecting autobrake lo and med via FSUIPC on my vrinsight-panel and I can't get that to work. It works in the vanilla A320 but not with the FBW mod.

    Yes, unfortunately. If i send LO or MED (2 and 3) via fsuipc offset the A32nx doesn't receipt the value

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