Win 8.1 update creating problems

[adler58]

*** Moved to main Support Forum from User Contributions - please post all support requests here in the main support forum ***

An update to Windows 8.1 installed on my PC in date 3rd January 2020, concerning a NET Framework language pack update, caused two problems with my FSX-SE installation:

1) My usual Skydemon interface between PC and Android device (Bluetooth GPS) refused to work;

2) IVAP disconnections every 45 (or about) seconds.

I think both problem were FSUIPC-related. Perhaps a FSUIPC is necessary for the FSX version (4.x).

Anyway, a Windows system restore at the restore point of 3rd January fixed both problems 😉

Edited January 8, 2020 by John Dowson
Moved to support forum

[John Dowson]

4 hours ago, adler58 said:

Perhaps a FSUIPC is necessary for the FSX version (4.x).

What do you mean by this? FSUIPC is always optional! If you mean an update/fix, then I do not think so. There is already a specific version available for the latest FSX-SE beta.

No idea what your problem was or if it was FSUIPC related, but as you have supplied no logs or detailed information of the problem, and you have restored, we cannot really help.

John

[adler58]

Thank you John,

The problem of a IVAP disconnection every 45 seconds or about is recurring, I searched for it on google and many users report that thing since years, but I did not find a fix.

I have suspected this problem was FSUIPC-related because two problems appeared at one time and both of them are related to communications between FSX and external software, which is one of the FSUIPC functionalities. I looked at what was changed on my PC since the last successful FSX flight and saw a Windows 8.1 update concerning NET Framework applied the 3rd of January, so I restored the previous PC state and this fixed both problems.

I apologize for the misunderstanding... I should have written "Perhaps a FSUIPC update is necessary for the FSX version (4.x)", I forgot to write the word "update"

I have got (regularly purchased at simmarket and registered) the latest version of FSUIPC4, released in 2018. But now I see the newer FSUIPC4 version for FSX-SE beta, so I will update to this one.

Moreover, I will not install NET Framework updates anymore in future... or will be very careful with them 😉

Edited January 8, 2020 by adler58
clarifying english text and explanation

[John Dowson]

If you are going to use the FSX-SE beta, please see this post as the FSUIPC version for this release has some restrictions:

John

 

[adler58]

Thanks John,

I currently have the latest standard version, FSUIPC 4.974 (february 2018). From february 2018 to now, many Windows updates have been applied and I think the latest one caused my problems described above

I don't use FSX-SE beta, I use the standard FSX-SE, so I would apply the 4.974c only for being the newest one available of FSUIPC 4, so taking into account all Windows updates occurred in time

Edited January 8, 2020 by adler58

[John Dowson]

There are no changed in the FSUIPC 4.974c version accept for the facilities that have been disabled (see post mentioned previously).

We have had no detailed reports of problems with FSUIPC4 relating to recent windows updates, and so cannot investigate. Note also that FSUIPC4 is now closed for further development. However, if a windows update did seriously affect FSUIPC4 then we would certainly investigate.

Cheers,

John

[Pete Dowson]

45 minutes ago, adler58 said:

The problem of a IVAP disconnection every 45 seconds or about is recurring, I searched for it on google and many users report that thing since years, but I did not find a fix.

I have suspected this problem was FSUIPC-related because two problems appeared at one time and both of them are related to communications between FSX and external software, which is one of the FSUIPC functionalities.

Further to what John says, I should point out that IVAP does not use FSUIPC and is certainly not dependent upon it for its connection.

So, you really need to seek IVAP assistance. They must have a Support Forum?

Pete

 

[adler58]

Thanks Pete,

I will try to contact the IVAP staff. It is important to know it does not use FSUIPC... perhaps it uses NET Framework and the update affected it.

But the other problem, Bluetooth GPS (Android app) not receiving FSX aircraft position, is probably related to FSUIPC because the GPS data sent by bluetooth come from FSUIPC (it is requested to check the boxes GGA etc. in FSUIPC)

[Pete Dowson]

59 minutes ago, adler58 said:

But the other problem, Bluetooth GPS (Android app) not receiving FSX aircraft position, is probably related to FSUIPC because the GPS data sent by bluetooth come from FSUIPC (it is requested to check the boxes GGA etc. in FSUIPC)

Changes in Windows, no matter what the update, don't affect the low level device access which FSUIPC uses for GPSout. 

What are your current GPSout settings (in FSUIPC4.INI)? Maybe the coms port number or name has changed? That's be the first thing I'd check.

Also, FSUIPC will log what it is attempting to send if you add these lines to the [General] section of the FSUIPC4.INI file:

Debug=Please
LogExtras=4

Check the logging -- make sure it is showing what you'd expect to be sent. if it is, and it isn't arriving, it will most likely be a problem with the port number or name. If it isn't right, then it's your settings.

Pete