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

No callback sample and the SimConnect_GetNextDispatch function

Messages
1
Country
us-newyork
Hello everyone,

I'm running the no callback sim connect sample from the MSFS SDK to learn about the SimConnect_GetNextDispatch function. For some reason, the SimConnect_GetNextDispatch function is returning E_FAIL and nothing is happening. If you are wondering, I did not modify anything.

Any ideas for why the function is returning E_FAIL? Does the sample work on your end?
 
It works perfectly within Prepar3D and AFAICS, the MSFS sample is lifted directly from the P3D SDK. This really leaves one of two possible answers:

1. The SDK samples are not installed correctly (unlikely)
2. It doesn't work in the MSFS SDK (most likely as the SDK is unfinished, broken and really not yet fit for use. Four years into MSFS and it's still not at v1.0).
 
Back
Top