Jump to content
The simFlight Network Forums

dcutugno

Members
  • Posts

    12
  • Joined

  • Last visited

Posts posted by dcutugno

  1. Thank you Pete, yes was monitoring the offset in FSX change, when opened the log i found the errors, corrected those and now is working well!

     

    In SB4 the 0 is for Normal (on), so it's inverted.

    i will publish the script for ohers to use as it's requested feature from some of us.

    Unfortunately IDENT in NGX737 is not mapped...

  2. function SquawkMode(offset, value)
         
         if value <> 0 then
             ipc.writeUB("7b91",0)
         else
             ipc.writeUB("7b91",1)
         end
     end
     event.offset("65CD", "UB", "SquawkMode")
    
    

    Hi Peter, i'm using this script to monitor the change in XPDR mode in the PMDG 737NGX and change the SB4 mode automatically but nothing seems to work, can you point me in the right direction?

    Here is the script:

     

  3. Peter you're the man! Your support is great!

    At the moment i can't try it in my sim to see the results, can you tell me if it is better using my lua script or assign it directly in fsuipc .ini? Ok now it will be great if you can add copy to offset xxxx in the interface tabs and we will be ok, i think it is one missing function in the FSUIPC not only for the AST, 'cause many Interface like FDS or opencockpit use Joystick emulation. So it will be great if we can program or re-route a joystick axis value to the specific offset.

    Best regards,

  4. And "AST" is, what, please? Is this related to the EPIC project I mentioned, because that is what is supposed to be using that offset area?

    AST is a company like Projec Magenta but they do a more specific Airbus suite.

    Yes, but why? What is forcing you into this weird round-about way of doing things? This is what I don't understand. What application is deliberately using private offsets, designated for other things, and then somehow by magic expecting axis values to appear there?

    Why isn't this AST, whatever it is, using the facilities available to it?

    Don't know why they use those specific offsets, the only thing i know is that they use the 4898 take the values then control the fs flaps by using their logic 'cause the airbus logic acts different on flaps.

    As you can see we asked in their forum but nothing happens so i have had to invent some way to do this, maybe they used an epic card before but now it is useless.

    If i used a pots in an opencockpits card we can use SIOC, but using a joystick card i was forced thanks to LUA to reprogram it...

    [LATER]

    I found "airsimtech"'s website. They appear to be using FSUIPC commercially, for very expensive packages, without an agreement or license, and furthermore, they are using offsets without requesting any allocation. I don't really think you can expect me to support them in such circumstances? In any case, if they are forcing you into the roundabout methods you seem to be asking for, they are doing things wrong in the first place. I respectfully suggest you deal with them on this matter. :-(

    Regards

    Pete

    So can't you help us on that?

  5. The 4898 is used for Flaps logic in AST, what the 4898 need is the a value passed by an axis it is basically a flap lever.

    So the point is this we need a custom facility to Calibrate an axis, name it for example custom axis 1 then assign the constantly updated values to an offset in this case 4898.

    What i did you can understand in the lua logic script, i assigned an axis from my joystick card i took Mixture4('cause it is unused in my setup) then pass the values to offset 4898.

    Hope i explained myself.

  6. Hi Peter, i would like to ask if it is possible to include this option directly in FSUIPC main interface, what i need is to pass a joystick axis value to an offset to resolve this problem what i did is to use a lua script but i would feel more comfortable if you can do this natively you can follow the discussion regarding this in the ast forum http://www.airsimtech.com/forum/forum_pD=286&PN=1

    Also another thing is that i saw that now you can limit the range instead of -16383, but use full travel of the axis what i need is from -4096 to +16383 needed for AST throttle how i can obtain this?

    Thank you for your support.

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