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

Gauges and FSX threads

mendiola_loyola

Resource contributor
Messages
520
Country
peru
Dear All:

Does FSX create a new thread when it loads a new gauge (dll) or does it run
the gauge(dll) inside the FSX main thread (in process).

If the answer is NO, It could be interesting that gauges run on separated threads to use multicore processors.

Thanks.
Alfredo Mendiola Loyola
 
By design, all gauge code is executed "in process" of the main FS thread, AFAIK.

There are probably some methods to move select portions of a gauge's code to a separate thread, but that's way beyond my abilities.
 
Yes, the panel system works in the main FS thread. And, using the Gauge SDK function to read simulation variables, they are not thread safe so, if you create a separate thread yourself, and call those functions from the other thread, you might run into threading issues and crashes.

A typical example would be using timers to poll flight sim variables: there are many kind of timers available in Windows, and the more modern and flexible ones, like the multimedia timers, are all using separate threads so, they'll not work very well within a gauge. The only one that is safe to use, is the SetTimer call, because it's not using a separate thread.

Of course, if you only use Simconnect calls to interface with FSX, there shouldn't be any threading issues at all, since Simconnect is designed to run between whole different apps.

Of course, moving to a separate thread something that is only relevant to your own code, like a complex calculation or the loading of a big database in the background, you shouldn't run in threading issues with FSX, and it's something you might use.
 
Last edited:
Back
Top