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

Simconnect failing after screensaver/suspend mode

S

Simon853

Messages
516
Not strictly a developer question this, other than I developed the SimConnect client app that's suffering, but I have a customer who's reporting that my aircraft (that includes a SimConnect client in a C gauge) stops working after his computer's screensaver cuts in or the PC goes to sleep/shuts down.

He says he has to reinstall FSX SP2 to get it to work again. Has anybody ever come across anything like this before? It's a new one on me..

I know its the SimConnect client failing because I have a light that starts flashing on a 2D panel if it doesn't receive any Simconnect event callbacks within a two second period.

Cheers,

Si
 
Hi Folks

Simon -
Reinstalling seems an extreme & last resort solution.

The following scenario is just a WAG - :D

- Customer's not using named pipes
- Customer's using a SimConnect IP address/port configuration, on a PC who's IP is DHCP assigned.

Customer's PC goes to sleep.
DHCP server releases and reassigns the IP to a different PC.

Customer's PC, awakened or rebooted,
and DHCP assigns it a new IP.

Customer launches FSX.
All SimConnect calls are now routed from customer's PC to that different PC.

As I said, just WAGuesses. :D

HTH
ATB
Paul
 
Last edited:
Since the SimConnect client is in a gauge, it should be using the internal bypass mechanism (so not using Named Pipes or TCP/IP, but an internal direct memory/function pointer sort of interface).

FSX in general isn't designed to work correctly across a suspend/resume process, or even the screen saver kicking in. In general it does work fine in these cases, but there's no knowledge within the app when these things happen, so no way for it to recover things like shutdown communications protocols (TCP/IP or named pipes or even a multiplayer session) or the fact that something like the in-memory local bypass mechanisms pointers may have "moved" after the suspend/resume possibly - not sure if that could happen or not).

No idea why your customer would need to reinstall FSX though, I would think at worst, just a reboot would be needed if just closing and restarting FSX didn't fix the problem (I know rebooting is sometimes needed to get clients on a second computer to connect correctly again). In fact for a gauge, just switching aircraft and then switching back might fix the problem.

On the screen saver cutting in issue, I wouldn't expect that to cause any issues at all (since the sim keeps running under the screen saver) unless the machine is part of domain that forces it to a lock screen when clearing the screen saver (the lock screen causes some issues for DX based apps, similar to trying to run in a remote desktop environment - which FSX doesn't support and specifically checks for).
 
Thanks for the responses. The feedback I have from the user appears to suggest that a reboot doesn't solve it and he has to reinstall, but that doesn't make any sense to me either. (Unless I suppose he has some kind of malware on his system that is trying to insert itself into dlls or whatever and breaking their operation..)

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