Well it’s known that 5.123 causes issues with v4.2 and the recommendation is to use 5.122 until Pete returns from vacation and releases a new working version.

 

Rodrigo are you saying that you had a similar texture corruption issue and downgrading to fsuipc 5.121 solved it?

I also have ASP4, GSX and other simconnect addons. No problem with any of them using FSUIPC 5.121. Have not tried 5.122 though.

I have updated both Client AND Content, and applied all the new patches and updates for the addons.

Everything is already working correctly after reinstalling. I never knew what happened. ?????

I had the same issue and a few others but managed to fix by deleting the generated files.  Go to the main P3D folder, click on "delete generated folders" wait for the black box to close.  Restart the sim.  you have to re-enter your settings but this fixed it for me (or at least it has appeared to).  FSUIPC 5.122

I have never used the ‘delete generated files’ command.  My fear is that all Addons except those which utilize the Addons.xml setup will have to be setup again.  Question, which are the critical cfg files that should be backed up before running the delete command?

 

This is a very frustrating issue. I open GSX and request boarding and everything is fine. Once that is complete i bring up the GSX menu again to request pushback and it quickly flashes and automatically requests deboarding. This has only happened since upgrading to 4.2. After confirming its not related to FSUIPC it then becomes more frustrating. We have FSDT saying there is nothing wrong there end and no update is needed, We then have Lockheed saying changes to SimConnect were made and developers need updates to be compatible with 4.2 This is just going round and round in circles and no one seems to know what to do to fix it. 

This workaround is a huge pain, but I'm now just using the mouse to select menu options to avoid this issue. Hope there's a fix ASAP.

8 hours ago, Mejjo said:

not related to FSUIPC

I've used FSUIPC 5.1.21 (non registered) and had the same issue with GSX/ASP4. After deleting all FSUIPC files in my v4 installation folder this didn't reoccur. Umberto from FSDT states that he doesn't use FSUIPC and without it everything works fine - as I can affirm.

2 hours ago, elButz said:

I've used FSUIPC 5.1.21 (non registered) and had the same issue with GSX/ASP4. After deleting all FSUIPC files in my v4 installation folder this didn't reoccur. Umberto from FSDT states that he doesn't use FSUIPC and without it everything works fine - as I can affirm.

Hey

That is strange as if i remove FSUIPC i still have the issue. 

11 hours ago, Mejjo said:

We have FSDT saying there is nothing wrong there end and no update is needed, We then have Lockheed saying changes to SimConnect were made and developers need updates to be compatible with 4.2 This is just going round and round in circles and no one seems to know what to do to fix it. 

The various reports from several users that either didn't had the problem to begin with, or had the problem, but fixed it in several ways, such as using the "delete generated files" command, or reverting to an older FSUIPC version, should be proof enough there's no update required for the affected applications, which are NOT just GSX, but any application that uses the Simconnect menu.

As I've said, the problem with the menu appeared at some time during the beta, and it was fixed by LM with a subsequent build, and they said it required the content update.

So, maybe, there are many issues connected, so you might have to do all of this:

- Install P3D using the Full installer, not just the Client

AND

- Don't use the latest FSUIPC

AND

- Try the "Delete Generated Files" option in the P3D folder.

The only thing SURE, it's nothing that has anything to do with GSX.

13 minutes ago, virtuali said:

The various reports from several users that either didn't had the problem to begin with, or had the problem, but fixed it in several ways, such as using the "delete generated files" command, or reverting to an older FSUIPC version, should be proof enough there's no update required for the affected applications, which are NOT just GSX, but any application that uses the Simconnect menu.

As I've said, the problem with the menu appeared at some time during the beta, and it was fixed by LM with a subsequent build, and they said it required the content update.

So, maybe, there are many issues connected, so you might have to do all of this:

- Install P3D using the Full installer, not just the Client

AND

- Don't use the latest FSUIPC

AND

- Try the "Delete Generated Files" option in the P3D folder.

The only thing SURE, it's nothing that has anything to do with GSX.

Hi

I have tried all of these except the delete generated files. I've used this feature in the past and it completely screwed my third party addons and i had to reinstall all of them. I'm using a full install of 4.2 and have checked it with both FSUIPC and without. Its got to be an issue with P3D. 

Hi,

I've tried using the "delete generated files". After I did it I ran EZCA2 config.exe, installed fsuipc 5.122 and added my backed up scenery.cfg. I've changed back all the settings manually. The problem is still here tho..

I just tested (after running the delete generated files script) and unfortunately the same thing happens!  Worse still my addons are all screwed up!!!!!!!!!!!  A bit word not allowed at that.

I am going to try one more thing.  I am going to delete all the file sin my p3d root\modules folder (which are all FSUIPC related and test....

3 minutes ago, Hilkiah said:

I just tested (after running the delete generated files script) and unfortunately the same thing happens!  Worse still my addons are all screwed up!!!!!!!!!!!  A bit word not allowed at that.

I am going to try one more thing.  I am going to delete all the file sin my p3d root\modules folder (which are all FSUIPC related and test....

Ouch.. I wish you had seen my post above about the deleting generated files... I did that before and it completely screwed my addons. I'm now totally lost at what to do to fix this. Lockheed just keep referring me to the debugging steps. They simply refuse to accept that it might be something with P3D. 

D

4 minutes ago, Mejjo said:

Ouch.. I wish you had seen my post above about the deleting generated files... I did that before and it completely screwed my addons. I'm now totally lost at what to do to fix this. Lockheed just keep referring me to the debugging steps. They simply refuse to accept that it might be something with P3D. 

Do you use chaseplane?