Jump to content
The simFlight Network Forums

the.gamer112

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by the.gamer112

  1. On 5/28/2019 at 4:54 PM, Pete Dowson said:

    Currently, if you really need to intercept those events and stop them going though I'm afraid you'll need to interface direct to SimConnect. Even then, for PMDG, it isn't guaranteed that you'll be able to do it.

    I don't need them to be stopped from going through, but I need to see when one of the events are happening (Every event triggers or gets triggered by a button press inside the cockpit)

    On 5/28/2019 at 4:54 PM, Pete Dowson said:

    PMDG tend to do their own thing, taking the events at the same priority level as my own .

    Would it be possible to increase the priority for IPC to handle these events first? That way IPC would intercept the event, make it possible for me to process it extrnally, and then send it on...

    I'm using FSUIPC 4.974b btw

     

    Fabian

  2. On 5/22/2019 at 8:17 PM, Luke Kolin said:

    Do you have the right encoding? These are 16-bit unicode characters IIRC.

    The way to request it out of IPC is (in lua):

    text, powered = ipc.readStruct("5400","1215STR")  --read 1215 character string from offset 5400 (Left CDU)

     

    after decoding from unicode-escape the text is formatted as followes:

    symbol(as string), color(hex), flags(x01, x02 or x04 not sure if combinations possible)

    so, as an example:

    0\x00\x01 would show a small 0 in default color (green on monochrome screen, white on LCD)

    F\x02\x04 would show a normal F in dark green (dark because of the x04 flag, inop/unavailable)

  3. 5 minutes ago, Pete Dowson said:

    Did you enable CDU broadcasts as instructed in the Offsets PDF?

    Yup

    6 minutes ago, Pete Dowson said:

    As with most all of the offsets populated from PMDG aircraft, the format of the data is documented by PMDG, not by us (it is their aircraft after all).  This would be in the .h document referenced right at the start of the Offsets PDF.

    I know, but since i'm using FSUIPC offset, for which the documentation in this case unfortunately are unclear I hoped you could help me out.

    (My biggest issue is the formatting)

    I assume this is the part I should get my info out of?

     

    struct PMDG_747QOTSII_CDU_Cell
    {
        unsigned char    Symbol;            
        unsigned char    Color;                    // any of PMDG_747QOTSII_CDU_COLOR_ defines
        unsigned char    Flags;                    // a combination of PMDG_747QOTSII_CDU_FLAG_ bits
    };

    // 747QOTSII CDU Screen Data Structure

    #define CDU_COLUMNS    24
    #define CDU_ROWS    14

    struct PMDG_747QOTSII_CDU_Screen
    {
        PMDG_747QOTSII_CDU_Cell Cells[CDU_COLUMNS][CDU_ROWS];    
        bool Powered;                            // true if the CDU is powered
    };

     

    I tried reading the offset at 4500 as str and this is the rawstring my function returns:

    \x00\x00 \x00\x00N\x00\x00 \x00\x00N\x00\x00 \x00\x00N\x00\x00 \x00\x00N\x00\x00 \x00\x00N\x00\x00-\x00\x00<\x00\x00 \x00\x00 \x00\x00I\x00\x015\x00\x00I\x00\x015\x00\x00I\x00\x015\x00\x00G\x00\x015\x00\x00G\x00\x015\x00\x00-\x00\x00I\x00\x00 \x00\x00 \x00\x00R\x00\x011\x00\x00R\x00\x011\x00\x00R\x00\x011\x00\x00P\x00\x011\x00\x00P\x00\x011\x00\x00-\x00\x00N\x00\x00 \x00\x00 \x00\x00S\x00\x01\xb0\x00\x00S\x00\x01\xb0\x00\x00S\x00\x01\xb0\x00\x00S\x00\x01\xb0\x00\x00S\x00\x01\xb0\x00\x00-\x00\x00D\x00\x00 \x00\x00 \x00\x00 \x00\x002\x00\x00 \x00\x002\x00\x00 \x00\x002\x00\x00 \x00\x002\x00\x00 \x00\x002\x00\x00-\x00\x00E\x00\x00 \x00\x00 \x00\x00L\x00\x016\x00\x00C\x00\x016\x00\x00R\x00\x018\x00\x00L\x00\x018\x00\x00R\x00\x018\x00\x00-\x00\x00X\x00\x00 \x00\x00 \x00\x00 \x00\x00.\x00\x00 \x00\x00.\x00\x00 \x00\x00.\x00\x00 \x00\x00.\x00\x00 \x00\x00.\x00\x00-\x00\x00 \x00\x00 \x00\x00 \x00\x00 \x00\x003\x00\x00 \x00\x002\x00\x00 \x00\x003\x00\x00 \x00\x003\x00\x00 \x00\x003\x00\x00-\x00\x00 \x00\x00 \x00\x00 \x00\x00 \x00\x00 \x00\x00 \x00\x00 \x00\x00 \x00\x00 \x00\x00 \x00\x00 \x00\x00 \x00\x00 \x00\x00-\x00\x00 \x00\x00 \x00\x00P\x00\x00 \x00\x00W\x00\x00 \x00\x00W\x00\x00 \x00\x00W\x00\x00 \x00\x00W\x00\x00 \x00\x00W\x00\x00-\x00\x00 \x00\x00 \x00\x00O\x00\x00 \x00\x000\x00\x00 \x00\x000\x00\x00 \x00\x000\x00\x00 \x00\x000\x00\x00 \x00\x000\x00\x00-\x00\x00 \x00\x00 \x00\x00S\x00\x00 \x00\x000\x00\x00 \x00\x000\x00\x00 \x00\x000\x00\x00 \x00\x000\x00\x00 \x00\x000\x00\x00-\x00\x00 \x00\x00 \x00\x00 \x00\x00 \x00\x00'

  4. Hello,

    I'm quite new to IPC, and i'm wondering if anybody knows how to read the CDU offsets of the QOTS2 v3 because the documentation only gives me the offsets.

    I only want to read the left CDU (5400-57FF) for now, but i'm only getting some weird formatted gibberish from IPC.....

    I'm running FSUIPC 4.974b with FSX:SE

     

    Best regards and thanks before,

    Fabian Gallinat

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