• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

ISerializableGaugeCCallback

Q

qsysk

Messages
10
Country
greece
Hello Boys and Girls

I am new to the forum but i have two questions for you.

Q1:
lets look at gauges.h

class NetOut;
class NetIn;

class ISerializableGaugeCCallback: public IGaugeCCallback {
public:
virtual bool Serialize(NetOut& netout) = 0;
virtual bool Deserialize(NetIn& netin) = 0;
};

Does anyones knows the structure of NetOut and NetIn classes..

I am trying to exchange data in a multilayer environment..
this can be done with standard gauges module and with simconnect
probably it can be done with the use of the class described above.. but currently is not feasible because NetIn and NetOut are unknown. :confused:

Q2:

I experimented for a while with SimConnect_WeatherRequestCloudState and i got some weird results. The clouds returns where depicted as boxes with no intermediate values, only 0x00 and 0xFF, is that correct??
 
I wonder if this gives us a clue (gauges.h):

typedef void SERIALIZE_CALLBACK( PGAUGEHDR gauge_header, BYTE* pBuf);
typedef SERIALIZE_CALLBACK *PSERIALIZE_CALLBACK;

// return true if successful
typedef bool DESERIALIZE_CALLBACK( PGAUGEHDR gauge_header, BYTE* pBuf );
typedef DESERIALIZE_CALLBACK *PDESERIALIZE_CALLBACK;

meaning, we'd have to make our own implementation. I'm just now looking at all this SimConnect stuff, so I have no idea. =)

Patrick
 
I am very much afraid that quite a bit of stuff in gauges.h is there for their (that is ACES') own use, and that without the other #include files they use, a lot of stuff will remain forever a mystery... :censored:
 
Could be, but it just looks like one can program a gauge much like a com-object, completely in C++, rather than having to use the C-like method of the samples.

Although the Interfaces are not derived from IUnknown, interestingly they contain the same interface as if they did. Sort of a COM one-off. :D

I asked Engaged if she'd do a post on using the Interfaces, so maybe we'll get lucky.

Patrick
 
You must log in or register to reply here.
Back
Top