Encoding error message shown on screeen

[firferion]

With the beta version, the same problem occurs. What else can be done? It’s impossible to play.

[virtuali]

Could you perhaps provide access to an older version of GSX Pro while you work on this issue?

We just can't, if you run an update CHECK now, there's an additional information in the log about it. It won't fix the error, but it would help us understanding where is happening. So update, and provide a log from the updated version.

[KuT]

Hi Umberto!

I have the same problem. I found a workaround:

- You need to translate the simulator language into English.

My case:

URSS Airport from Digital Design. When loading, I get an error. My language in the simulator is RUSSIAN. I go to the simulator menu, change the simulator language to ENGLISH and you can immediately press the GSX button and it will work.

In the log in the attachment, up to line 618, the language was RUSSIAN.

and an error appeared: "emulateText_MSFS [GSX] 'utf-8' codec can't decode byte 0xd1 in position 31: unexpected end of data RED 6".

Then I switched to English and everything worked.

Problems only in this airport. In the same ULLI from Digital Design, or UUDD there are no problems.

There are also no gaps in other scenes from other authors.


UPD:

Forgot to add for reference:

I have Win 11, MSFS2024 Steam, GSX version 2.5.4 (complete reinstallation (according to your advice due to problems with pink textures)

The aircraft does not matter, PMDG or ini A350. The airport itself is important.

I did not change anything in audio devices and folders. This airport and GSX in it worked fine in version 3.4.7, then I updated ONLY GSX, lg 3.5.3, and the problem appeared. Today I deleted GSX via the installer and installed it from scratch, since there was a problem with pink catering textures.

[gaspa77]

Ciao Umberto, here is my last log file....could you help me please?

This is very strange, and it doesn't seem to be related to audio at all, like the other users who had audio drivers with non-western characters. It seems to be related in some way to the airport data. Are you using a 3rd party scenery ?

Yes, in this case I'm departing from MMMX Airport 3rd party scenary buyed directly from the shop inside MSFS2020...made by FlyMex

I tried to delete the third party version of Mexico City airport and use only the defoult version of MSFS2020 but the problem is still the same and identical. I have also tried other airports both third party and it is not for now the problem for me remains only on Mexico City MMMX. Can you do anything to help me find a solution, please?

[virtuali]

In the log in the attachment, up to line 618, the language was RUSSIAN.

Have you made this log using the latest version (3.5.4) which came out today ? As I've said, we added extra diagnostic that would help use understand where the error is coming from.

[firferion]

Could you perhaps provide access to an older version of GSX Pro while you work on this issue?

We just can't, if you run an update CHECK now, there's an additional information in the log about it. It won't fix the error, but it would help us understanding where is happening. So update, and provide a log from the updated version.

New log after update. Сhanging the game locale to en_us removes the error

[KuT]

In the log in the attachment, up to line 618, the language was RUSSIAN.

Have you made this log using the latest version (3.5.4) which came out today ? As I've said, we added extra diagnostic that would help use understand where the error is coming from.

YES, that's right.

I reinstalled it an hour and a half ago and ran it, reproduced it and packed the log for you.

[virtuali]

I reinstalled it an hour and a half ago and ran it, reproduced it and packed the log for you.

Just to be sure, please do it again, run an update CHECK again and try another log. There's supposed to be something else other than just the error.

[KuT]

I reinstalled it an hour and a half ago and ran it, reproduced it and packed the log for you.

Just to be sure, please do it again, run an update CHECK again and try another log. There's supposed to be something else other than just the error.

The installer said that the latest 3.5.4 and installed 3.5.4.

At 16:44 UTS I clicked the check button. The installer did the check and finished. I launched the simulator, set the Russian language, loaded the same URSS airport from digital design.

The error was reproduced, I attached the log, but I did not see anything new in it ; (

There is a build number in the log, can you confirm that this is the one I need? If not - is there an offline installer (the main thing is that all airport configs are saved. I'll go crazy setting all this up again ; )) )

If necessary - write to me, we can tinker with the debug or something that will help you fix the problem, since I can reproduce it stably.

[nobleord]

I had this issue with 3.5.3, all seemed to work fine at the departure airport KSLC (a scenery from fs.to) [the only oddity was that it used a different push operator than selected], but when choosing my arrival gate after landing (KPHX - a scenery from fs.to) GSX had this encoding error.  I had no GSX issues with the KPHX scenery in prior GSX versions.

I added the log file entry in the INI, when MSFS2020 is running I see that it appears to have created a file with > 10KB size.  However once I close the sim, the log file reverts to 0KB.  I have updated to 3.5.4.  So not sure how to get you a log post flight if it wipes the file contents.

[gaspa77]

In the log in the attachment, up to line 618, the language was RUSSIAN.

Have you made this log using the latest version (3.5.4) which came out today ? As I've said, we added extra diagnostic that would help use understand where the error is coming from.

I updated via the FSDT Installer to version 3.5.4. Then I did the update again using FSDT Live Update. Afterwards, I returned to the installer and performed the Check using the appropriate button. I then entered the MSFS2020 simulator again and set the departure from Gate 32 at Mexico City's airport (ICAO) MMMX. The problem persists. I am attaching the new log file after the update as per your latest instructions and requests. I hope you can resolve the issue. Please... Let me know, thanks.

[virtuali]

Can you try another update CHECK now ? I've added logs in other place of the code, perhaps we'll find something.

[GONGM1N]

problem solved after I switched MSFS language to English

[virtuali]

problem solved after I switched MSFS language to English

Well,. that's not a real solution, we want to fix it with every language.

[KuT]

Can you try another update CHECK now ? I've added logs in other place of the code, perhaps we'll find something.

Yes, no problem. At 19:02 Zulu started checking.

I did everything according to the same scheme as before.

Log in the attachment. I didn't see anything new. Perhaps by the build version you can determine whether the update I downloaded was the one you made the fix in.