FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: GONGM1N on May 29, 2025, 09:59:38 pm
-
After the latest 3.5.3 update, an error shows "UTF-8 CODEC CANT DECODE BYTE IN POSITION XX: UNEXPECTED END OF DATA" whenever I click on the GSX menu, I tried reinstalling GSX and profiles, but nothing changed
-
A startup log would be useful. See the Sticky thread here how to create one-
-
Please see my log attached below
-
Anyone installed latest version running SU16 beta and can feedback pls?
-
Hi, I've get the same problem and error after the last update 3.5.3 last night in MMMX airport by FlyMex. "UTF-8 CODEC CANT DECODE BYTE 0xC3 IN POSITION 31: UNEXPECTED END OF DATA". How can I resolve It? Any Help?, please...
-
Hi, I've get the same problem and error after the last update 3.5.3 last night in MMMX airport by FlyMex. "UTF-8 CODEC CANT DECODE BYTE 0xC3 IN POSITION 31: UNEXPECTED END OF DATA". How can I resolve It? Any Help?, please...
Same as the previous posted, I need your log.
-
UPDATE: This error only shows up when I fly in US airports, other airports in China, Canada or Europe are working perfectly fine
-
Hi, I've get the same problem and error after the last update 3.5.3 last night in MMMX airport by FlyMex. "UTF-8 CODEC CANT DECODE BYTE 0xC3 IN POSITION 31: UNEXPECTED END OF DATA". How can I resolve It? Any Help?, please...
Same as the previous posted, I need your log.
Ciao Umberto, here is my last log file....could you help me please?
-
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 ?
-
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 ?
Hey, I just found out that the error only shows in US airports, other airports I tried, such as ZBAA, ZSPD, CYYZ, EGLL, LOWI, VHHH are working fine, they include default airports, asobo made airports and 3rd party airports. The only difference between them I believe is the ICAO code. I am not an expert in coding, but maybe the code of airports (the letter "K") messed up with something that causing errors of GSX. I just want to share the information I have for now. :)
-
Couatl starts up, but when I try to open the in‑game GSX panel I get an error. This only happens at the UNNT airport; everything seems to work fine elsewhere. No other add‑ons are installed. I’ve tried disabling services and jetways in the GSX settings, but that didn’t help.
-
I think it must be related to the airport name in the Navdata. What language is your MSFS set to ?
-
I think it must be related to the airport name in the Navdata. What language is your MSFS set to ?
it's Chinese simplified
-
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
-
Could you perhaps provide access to an older version of GSX Pro while you work on this issue?
-
With the beta version, the same problem occurs. What else can be done? It’s impossible to play.
-
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.
-
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.
-
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?
-
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.
-
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
-
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.
-
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.
-
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.
-
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.
-
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.
-
Can you try another update CHECK now ? I've added logs in other place of the code, perhaps we'll find something.
-
problem solved after I switched MSFS language to English
-
problem solved after I switched MSFS language to English
Well,. that's not a real solution, we want to fix it with every language.
-
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.
-
Yes, no problem. At 19:02 Zulu started checking.
I need to be absolutely sure you are using the latest update, because I still don't see the extra diagnostic, can you try the Offline Installer instead ? This way, we are sure you are not affected by a network replication delay, so if we still don't see any extra diagnostic, it means I need to search in other parts of the code the error happens.
-
Can you try another update CHECK now ? I've added logs in other place of the code, perhaps we'll find something.
Ciao Umberto, I've done like you say...another udate CHECK right now...same problem at the MMMX airport. I've made the new .log file for you hope can help you for resolve...please..
-
Yes, no problem. At 19:02 Zulu started checking.
I need to be absolutely sure you are using the latest update, because I still don't see the extra diagnostic, can you try the Offline Installer instead ? This way, we are sure you are not affected by a network replication delay, so if we still don't see any extra diagnostic, it means I need to search in other parts of the code the error happens.
If you tell me where to get an offline installer 3.5.4, I'll be happy to try it. ; ) In this forum i found installer from 29 may( 3.5.3? )
It won't affect my ready-made airport configs, will it?
I'll just make a backup if it does (they'll be deleted or reset). But I'd like to know about it from you in advance ; )
-
If you tell me where to get an offline installer 3.5.4, I'll be happy to try it. ; ) In this forum i found installer from 29 may( 3.5.3? )
The forum post is not updated, the installer is.
-
If you tell me where to get an offline installer 3.5.4, I'll be happy to try it. ; ) In this forum i found installer from 29 may( 3.5.3? )
The forum post is not updated, the installer is.
You can simulate the problem yourself by selecting the game language to ru_ru and loading at the UNNT or URSS airports.
-
If you tell me where to get an offline installer 3.5.4, I'll be happy to try it. ; ) In this forum i found installer from 29 may( 3.5.3? )
The forum post is not updated, the installer is.
Hi Umberto!
Yesterday and today at 14:00Z I did a check in the regular installer. Then I downloaded it offline and installed it. Then I launched it using the same scenario as before. Everything is the same. I didn't see any new information.
From the interesting thing, if you switch the simulator to English, run GSX, switch back to Russian - GSX will work )
I have a hypothesis that the problem is in the airport name in the bgl file (In particular for URSS - Community\digitaldesign-airport-urss-sochi\scenery\obj.bgl )
I did some research to rule out different things:
- Tried saving the configuration file in different encodings. Didn't help.
- Tried deleting the configuration file so that GSX would generate a new one. The story here is that if the configuration file does not exist, with the Russian language in the Simulator, when starting GSX we apparently get the error about which this thread is, BUT the configuration file is still not created. After translating the simulator into English - everything is fine, the file is created. But with it, if you switch back to Russian, GSX still does not work.
- Visited StackOverFlow and other resources. As I understand it, this is a common problem for python. Perhaps the problem is that the BGL file has a translation into Russian, GSX tries to read it, insert it in its encoding into the DB, but it can't because the DB with such encoding doesn't work or can't accept it. or accepts it and crashes. You know better here, I don't know the GSX code.
I hope my ideas and guesses will help you.
-
I'm quite sure it has something to do with the encoding of the airport name. We don't read the .BGL file, we get data from Simconnect. In theory, Python 3 should solve all encoding issues, because it's natively unicode, but maybe something else is not, or we just need to changes things we had to do to make it work in Python 2.
But yes, we should have enough data to investigate it and replicate it.
-
I'm quite sure it has something to do with the encoding of the airport name. We don't read the .BGL file, we get data from Simconnect. In theory, Python 3 should solve all encoding issues, because it's natively unicode, but maybe something else is not, or we just need to changes things we had to do to make it work in Python 2.
But yes, we should have enough data to investigate it and replicate it.
Is there anything else I can help with?
As suggested above, I can find you a freeware airport if you don't have URSS and help you reproduce it locally. search for you?
-
I'm quite sure it has something to do with the encoding of the airport name. We don't read the .BGL file, we get data from Simconnect. In theory, Python 3 should solve all encoding issues, because it's natively unicode, but maybe something else is not, or we just need to changes things we had to do to make it work in Python 2.
But yes, we should have enough data to investigate it and replicate it.
Is there anything else I can help with?
As suggested above, I can find you a freeware airport if you don't have URSS and help you reproduce it locally. search for you?
Man, I've the same problem as you in City of MEXICO, olso in the default ones of MSFS2020. . I think that GSX must to resolve this problem not just for URSS airport... It's a problem somewhere everywhere..
-
I'm quite sure it has something to do with the encoding of the airport name. We don't read the .BGL file, we get data from Simconnect. In theory, Python 3 should solve all encoding issues, because it's natively unicode, but maybe something else is not, or we just need to changes things we had to do to make it work in Python 2.
But yes, we should have enough data to investigate it and replicate it.
Is there anything else I can help with?
As suggested above, I can find you a freeware airport if you don't have URSS and help you reproduce it locally. search for you?
Man, I've the same problem as you in City of MEXICO, olso in the default ones of MSFS2020. . I think that GSX must to resolve this problem not just for URSS airport... It's a problem somewhere everywhere..
I missed the point that this is also present at standard airports.
If so, then Umberto has a default S2R and you are absolutely right that it is not worth fixing on URSS.
-
I'm quite sure it has something to do with the encoding of the airport name. We don't read the .BGL file, we get data from Simconnect. In theory, Python 3 should solve all encoding issues, because it's natively unicode, but maybe something else is not, or we just need to changes things we had to do to make it work in Python 2.
But yes, we should have enough data to investigate it and replicate it.
Is there anything else I can help with?
As suggested above, I can find you a freeware airport if you don't have URSS and help you reproduce it locally. search for you?
Man, I've the same problem as you in City of MEXICO, olso in the default ones of MSFS2020. . I think that GSX must to resolve this problem not just for URSS airport... It's a problem somewhere everywhere..
I missed the point that this is also present at standard airports.
If so, then Umberto has a default S2R and you are absolutely right that it is not worth fixing on URSS.
In URSS without addon same problem.
-
Hello everyone.
Simulator 2024, UNKL airport.
At different times during loading the simulator and at the airport parking lot, the Couatl file is overwritten.
I am attaching two files. I hope this will help.
-
The simulator was in Russian and after updating gsx a similar problem appeared. Switched the simulator to English - gsx started and began to work! Please fix this problem!
-
Of course we'll fix this problem! There's no need to stress it, not having issues with encoding is supposed to be one benefit or switching from Python 2 to 3! I'm sure there must be some part of the code which had workarounds that might not be needed anymore, of something related to the interaction with Simconnect as well, which we need to fix.
You provided enough data to replicate it, so we can work at it now.
-
In some airports (LGIR HTZA UGSB) gsx doesn't work and shows error as on photo.
-
I merged your post because there was already a thread open about this, which confirmed we are working on it.
-
So what's the problem? Maybe you could still open access to an older version? Because right now half of the airports with GSX are simply unavailable.
-
Have you tried updating now ?
-
Have you tried updating now ?
I have version 3.5.5 installed, but the problem still persists.
-
I have version 3.5.5 installed, but the problem still persists.
I haven't asked if you have version 3.5.5 reported, I asked if you tried to update now. With now being now. The version hasn't changed, but we want to wait a bit to announce a new version, and get some feedback from affected users before.
That's why I asked it you tried to do an update now, and see if it's fixed, because your feedback IS useful.
-
I have version 3.5.5 installed, but the problem still persists.
I haven't asked if you have version 3.5.5 reported, I asked if you tried to update now. With now being now. The version hasn't changed, but we want to wait a bit to announce a new version, and get some feedback from affected users before.
That's why I asked it you tried to do an update now, and see if it's fixed, because your feedback IS useful.
Everything’s fine; I checked at the airports where I had the error.
-
Hello!
I confirm, I went through the old case that I wrote earlier - everything works now.
-
Hi, I did a new check and a new update this afternoon. I also confirm that for now everything seems to be working and the problem I had in Mexico City (MMMX) has disappeared! Great! Great work and intervention!
-
It it helps this is my log file.
Simulator: MSFS 2020
Aircraft: Inibuilds A320neo (Default aircraft w/ MSFS)
Airport: EGGD (Bristol) stock scenery
I have run "CHECK" on FSDT installer, all is up to date
---
Running in mode: Microsoft Flight Simulator
SharedMemInterface connected
Python 3.7.9 Stackless 3.7 (tags/v3.7.9-slp-dirty:8ad319a856, May 22 2021, 22:48:12) [MSC v.1916 64 bit (AMD64)]
wxPython 4.2.0
Couatl v5.0 (build 5792)
log started on Thu Jun 5 20:05:00 2025
connecting to SimConnect...
connected to SimConnect
connected to bglmanx
Simulator version: 11.0.282174.999
RunningMode::pathToInstalledPackages C:\Users\Steve\AppData\Roaming\Microsoft Flight Simulator\Packages
Loading addons
Loading addon common
Addon common loaded
Loading addon LiveUpdate
Addon LiveUpdate loaded
requesting AddOn list to bglmanx
Slew mode False
bglmanx list contains 33 AddOn(s)
Loading addon LFSB
Addon LFSB loaded
Loading addon GSX
Current sim directory is C:/Program Files (x86)/Addon Manager/couatl64
Addon GSX loaded
Loading addon GSX.airports.kiah_fsdt_MSFS
Addon GSX.airports.kiah_fsdt_MSFS loaded
Loading addon KIAH2
Addon KIAH2 loaded
Loading addon GSX.airports.kord_v2_fsdt_MSFS
Addon GSX.airports.kord_v2_fsdt_MSFS loaded
Loading addon GSX.airports.ksdf_fsdt_MSFS
Addon GSX.airports.ksdf_fsdt_MSFS loaded
Loading addon GSX.airports.lszh_fsdt_MSFS
Addon GSX.airports.lszh_fsdt_MSFS loaded
Loading addon GSX.airports.cyvr_fsdt_MSFS
Addon GSX.airports.cyvr_fsdt_MSFS loaded
Loading addon GSX.airports.keyw_fsdt_MSFS
Addon GSX.airports.keyw_fsdt_MSFS loaded
Loading addon GSX.airports.kclt_fsdt_MSFS
Addon GSX.airports.kclt_fsdt_MSFS loaded
Loading addon GSX.airports.lfeq_fsdt_MSFS
Addon GSX.airports.lfeq_fsdt_MSFS loaded
Starting system monitors
[KIAH2] is active
resetVars() with Simconnect
Common onAppStart
createDefaultContainer
Current locale is English_United Kingdom.1252
Initializing audio...
Available devices:
OpenAL Soft on Speakers (2- Razer BlackShark V2 Pro)
OpenAL Soft on Q32G2WG3 (NVIDIA High Definition Audio)
OpenAL Soft on Headphones (AudioPro X5 Microphone)
OpenAL Soft on Realtek Digital Output (Realtek(R) Audio)
Created OpenAL device: OpenAL Soft on Speakers (2- Razer BlackShark V2 Pro)
Device info:
Major version: 1
Minor version: 1
Frequency: 48000
Refresh: 50
Sync: 0
Mono sources: 255
Stereo sources: 1
Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_DEDICATED ALC_EXT_disconnect ALC_EXT_EFX ALC_EXT_thread_local_context ALC_SOFT_device_clock ALC_SOFT_HRTF ALC_SOFT_loopback ALC_SOFT_loopback_bformat ALC_SOFT_output_limiter ALC_SOFT_output_mode ALC_SOFT_pause_device ALC_SOFT_reopen_device
Context info:
Vendor: OpenAL Community
Version: 1.1 ALSOFT 1.23.1
Renderer: OpenAL Soft
Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX-RAM AL_EXT_ALAW AL_EXT_BFORMAT AL_EXT_DOUBLE AL_EXT_EXPONENT_DISTANCE AL_EXT_FLOAT32 AL_EXT_IMA4 AL_EXT_LINEAR_DISTANCE AL_EXT_MCFORMATS AL_EXT_MULAW AL_EXT_MULAW_BFORMAT AL_EXT_MULAW_MCFORMATS AL_EXT_OFFSET AL_EXT_source_distance_model AL_EXT_SOURCE_RADIUS AL_EXT_STATIC_BUFFER AL_EXT_STEREO_ANGLES AL_LOKI_quadriphonic AL_SOFT_bformat_ex AL_SOFTX_bformat_hoa AL_SOFT_block_alignment AL_SOFT_buffer_length_query AL_SOFT_callback_buffer AL_SOFTX_convolution_reverb AL_SOFT_deferred_updates AL_SOFT_direct_channels AL_SOFT_direct_channels_remix AL_SOFT_effect_target AL_SOFT_events AL_SOFT_gain_clamp_ex AL_SOFTX_hold_on_disconnect AL_SOFT_loop_points AL_SOFTX_map_buffer AL_SOFT_MSADPCM AL_SOFT_source_latency AL_SOFT_source_length AL_SOFT_source_resampler AL_SOFT_source_spatialize AL_SOFT_source_start_delay AL_SOFT_UHJ AL_SOFT_UHJ_ex
Using EFX 1.0 extension, with 4 auxiliary send(s)
Using EAX reverb
Created OpenAL device: OpenAL Soft on Speakers (2- Razer BlackShark V2 Pro)
Device info:
Major version: 1
Minor version: 1
Frequency: 48000
Refresh: 50
Sync: 0
Mono sources: 255
Stereo sources: 1
Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_DEDICATED ALC_EXT_disconnect ALC_EXT_EFX ALC_EXT_thread_local_context ALC_SOFT_device_clock ALC_SOFT_HRTF ALC_SOFT_loopback ALC_SOFT_loopback_bformat ALC_SOFT_output_limiter ALC_SOFT_output_mode ALC_SOFT_pause_device ALC_SOFT_reopen_device
Context info:
Vendor: OpenAL Community
Version: 1.1 ALSOFT 1.23.1
Renderer: OpenAL Soft
Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX-RAM AL_EXT_ALAW AL_EXT_BFORMAT AL_EXT_DOUBLE AL_EXT_EXPONENT_DISTANCE AL_EXT_FLOAT32 AL_EXT_IMA4 AL_EXT_LINEAR_DISTANCE AL_EXT_MCFORMATS AL_EXT_MULAW AL_EXT_MULAW_BFORMAT AL_EXT_MULAW_MCFORMATS AL_EXT_OFFSET AL_EXT_source_distance_model AL_EXT_SOURCE_RADIUS AL_EXT_STATIC_BUFFER AL_EXT_STEREO_ANGLES AL_LOKI_quadriphonic AL_SOFT_bformat_ex AL_SOFTX_bformat_hoa AL_SOFT_block_alignment AL_SOFT_buffer_length_query AL_SOFT_callback_buffer AL_SOFTX_convolution_reverb AL_SOFT_deferred_updates AL_SOFT_direct_channels AL_SOFT_direct_channels_remix AL_SOFT_effect_target AL_SOFT_events AL_SOFT_gain_clamp_ex AL_SOFTX_hold_on_disconnect AL_SOFT_loop_points AL_SOFTX_map_buffer AL_SOFT_MSADPCM AL_SOFT_source_latency AL_SOFT_source_length AL_SOFT_source_resampler AL_SOFT_source_spatialize AL_SOFT_source_start_delay AL_SOFT_UHJ AL_SOFT_UHJ_ex
Using EFX 1.0 extension, with 4 auxiliary send(s)
Using EAX reverb
Created OpenAL device: OpenAL Soft on Speakers (2- Razer BlackShark V2 Pro)
Device info:
Major version: 1
Minor version: 1
Frequency: 48000
Refresh: 50
Sync: 0
Mono sources: 255
Stereo sources: 1
Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_DEDICATED ALC_EXT_disconnect ALC_EXT_EFX ALC_EXT_thread_local_context ALC_SOFT_device_clock ALC_SOFT_HRTF ALC_SOFT_loopback ALC_SOFT_loopback_bformat ALC_SOFT_output_limiter ALC_SOFT_output_mode ALC_SOFT_pause_device ALC_SOFT_reopen_device
Context info:
Vendor: OpenAL Community
Version: 1.1 ALSOFT 1.23.1
Renderer: OpenAL Soft
Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX-RAM AL_EXT_ALAW AL_EXT_BFORMAT AL_EXT_DOUBLE AL_EXT_EXPONENT_DISTANCE AL_EXT_FLOAT32 AL_EXT_IMA4 AL_EXT_LINEAR_DISTANCE AL_EXT_MCFORMATS AL_EXT_MULAW AL_EXT_MULAW_BFORMAT AL_EXT_MULAW_MCFORMATS AL_EXT_OFFSET AL_EXT_source_distance_model AL_EXT_SOURCE_RADIUS AL_EXT_STATIC_BUFFER AL_EXT_STEREO_ANGLES AL_LOKI_quadriphonic AL_SOFT_bformat_ex AL_SOFTX_bformat_hoa AL_SOFT_block_alignment AL_SOFT_buffer_length_query AL_SOFT_callback_buffer AL_SOFTX_convolution_reverb AL_SOFT_deferred_updates AL_SOFT_direct_channels AL_SOFT_direct_channels_remix AL_SOFT_effect_target AL_SOFT_events AL_SOFT_gain_clamp_ex AL_SOFTX_hold_on_disconnect AL_SOFT_loop_points AL_SOFTX_map_buffer AL_SOFT_MSADPCM AL_SOFT_source_latency AL_SOFT_source_length AL_SOFT_source_resampler AL_SOFT_source_spatialize AL_SOFT_source_start_delay AL_SOFT_UHJ AL_SOFT_UHJ_ex
Using EFX 1.0 extension, with 4 auxiliary send(s)
Using EAX reverb
resetVars() with Simconnect
GSX is starting
[GSX] Simulator version is 11.0.282174.999
isPBRAvailable returned False
isRTTAvailable returned False
GetSimObjectsFolder() returned C:\Program Files (x86)\Addon Manager/MSFS/fsdreamteam-gsx-pro/SimObjects
GetAdditionalSimObjectsFolder() returned C:\Program Files (x86)\Addon Manager/MSFS/fsdreamteam-gsx-world-of-jetways/SimObjects
GetAdditionalSimObjectsFolderV5() returned
gateDistanceThreshold = 25 m
[KIAH2] started
Preloading pyglet image library...
GSX started
Start searching for add-on Packages
Packages that contain manifest.json with gsx-pro in dependencies:
Creating model cache...
Model cache loaded
Preload operators thumbnails...
Preload operators thumbnails DONE
requestFacilityData EGGD
GSX SimStart
requestFacilityData DONE EGGD
Loading airport EGGD
Loading user customizations from C:\Users\Steve\AppData\Roaming\Virtuali/GSX/MSFS\eggd-dul5nb.ini
USER airplane title reported by Simconnect is Airbus A320neo FlyUK
Loading aircraft.cfg from C:\Users\Steve\AppData\Roaming\Microsoft Flight Simulator\Packages\Official\Steam\microsoft-aircraft-a320neo\SimObjects\Airplanes\microsoft-aircraft-a320neo
Loading engines.cfg from C:\Users\Steve\AppData\Roaming\Microsoft Flight Simulator\Packages\Official\Steam\microsoft-aircraft-a320neo\SimObjects\Airplanes\microsoft-aircraft-a320neo
Loading flight_model.cfg from C:\Users\Steve\AppData\Roaming\Microsoft Flight Simulator\Packages\Official\Steam\microsoft-aircraft-a320neo\SimObjects\Airplanes\microsoft-aircraft-a320neo
Loading gameplay.cfg from C:\Users\Steve\AppData\Roaming\Microsoft Flight Simulator\Packages\Official\Steam\microsoft-aircraft-a320neo\SimObjects\Airplanes\microsoft-aircraft-a320neo
Loading systems.cfg from C:\Users\Steve\AppData\Roaming\Microsoft Flight Simulator\Packages\Official\Steam\microsoft-aircraft-a320neo\SimObjects\Airplanes\microsoft-aircraft-a320neo
Error [Errno 2] No such file or directory: 'C:\\Users\\Steve\\AppData\\Roaming\\Microsoft Flight Simulator\\Packages\\Official\\Steam\\microsoft-aircraft-a320neo\\SimObjects\\Airplanes\\microsoft-aircraft-a320neo\\aircraft.cfg' parsing C:\Users\Steve\AppData\Roaming\Microsoft Flight Simulator\Packages\Official\Steam\microsoft-aircraft-a320neo\
this airplane has 0 exits
Model: "A20N" (length: 4)
Title: "Airbus A320neo FlyUK" (length: 20)
Airplane major/minor version 320/0
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 8: unexpected end of data
{'User Pos': (51.38552221090828, -2.715355490996312, 188.121 m, 3.70941 m, 357.30049839136586, 0.006596315038104643, 0.006981316953897476, -0.0011480536621357794, 3.6576000000000004, 1.0), 'Airport': 'EGGD'}
---
-
It it helps this is my log file.
Simulator: MSFS 2020
Aircraft: Inibuilds A320neo (Default aircraft w/ MSFS)
Airport: EGGD (Bristol) stock scenery
I have run "CHECK" on FSDT installer, all is up to date
I tried the default A320 NEO at default EDDG, and it works fine, no issues. I see you have a custom GSX profile for it, so please ZIP it and ATTACH to a post (never quote long logs, always use the ATTACH function), so I can check if it might be related to something in the profile.
-
The file is attached.
I think the customisation is simply clicking on the relevant option in GSX to allow the aircraft at a parking space that is too small (I forget which option it is). Wingspan perhaps?
However - I did have the same issue at EGSH (Norwich) and I do not have a custom profile for that airport.
Thanks,
Steve
-
So, to help you diagnose the issue loading the same aircraft into 2020 the following error pops up. (see attachment)
There is no custom airport profile for this airport (EGSH -> Norwich), and it is completely stock scenery.
-
And here is the log file for that scenario.
I had to rename it to .txt to upload it.
-
I think the customisation is simply clicking on the relevant option in GSX to allow the aircraft at a parking space that is too small (I forget which option it is). Wingspan perhaps?
That was I thought but, I tried with your profile, which only customized Parking 29, and it works with no errors.
Your profile also didn't set the correct Wingspan, so I got the "Airplane too small" message, which is normal. I entered the customization page, set the Wingspan, and everything works with no errors.
-
I believe I've identified the cause of the issue ... it must the livery I am using (although it did work fine previously).
I loaded the "Default - White" livery, and there is no problem 👍
If you wish, I can send you any configuration files from the offending livery to see if you can identify the problem? Please tell me which files are required and I will attach them.
-
And here is the log file for that scenario.
This log is very different: the first one shows you were parked at Bristol, this one shows you are located at Lat/Lon 0,0, that is even before the simulator is loading. which is very strange, because GSX is not even supposed to check the airport unless the loading process completed.
-
If you wish, I can send you any configuration files from the offending livery to see if you can identify the problem? Please tell me which files are required and I will attach them.
Can this livery be downloaded ? If yes, please post a link.
-
Sure - here is the link:
- Edit: Link removed for privacy and respect to VA -
Steve
-
Sure - here is the link:
Thanks alot, in fact the problem IS the livery aircraft.cfg DOES contain an encoding error, in the atc_id line, the problem is you need a proper text editor or an hex editor to notice that, because if you open it with plain Notepad, it "looks" like 4 spaces, but they are not, this is what it really is, from an hex dump:
atc_id = " ‎‎" ;
The problem is, this encoding error is being sent to the sim, so it corrupted the string we get from Simconnect itself! You can fix it easily by replacing the line with either a valid atc_id, or just 4 spaces or just nothing, like this, using empty double quotes.
atc_id = ""
Of course, we'll look into this for a better solution on our side, so we won't be stopped by a corrupted livery file.
-
Perfect - glad we got to the bottom of it, thanks Umberto.
-
Just confirming - amending the string to "" in the aircraft.cfg has fixed the issue I was having.
-
Hello everyone. After updating to version 3.5.5, GSX PRO stopped working, simulator msfs 2020. The error keeps giving out endlessly. I provide you with the error logs. couatl v5.0 (build 5792)
panic log started on Fri Jun 6 09:37:49 2025
problem raised by addon <no traceback available>
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 8: unexpected end of data
{'User Pos': (0.0004080348298211941, 0.01397450300629543, 4.76642 m, 4.76642 m, 0.0001643087326757503, 0.01013402451562407, -0.003490658476948738, 8.74908466839379e-05, 4.611624034881592, 1.0)}
Reinstalling and deleting folder AppData\Roaming\virtuali did not help. Before updating version 3.5.5 everything worked fine)
-
Hello everyone. After updating to version 3.5.5, GSX PRO stopped working, simulator msfs 2020. The error keeps giving out endlessly. I provide you with the error logs. couatl v5.0 (build 5792)
Your post has been moved because you posted it without checking there was another thread about it.
The problem with the Russian language encoding has been fixed in the latest update, but the version number hasn't changed, because we want to get some feedback about it before announcing it fixed.
So, first run an update CHECK now, to be sure you have the latest version of all files. If that doesn't work, try the OFFLINE installer instead. If still doesn't work, provide a complete log and describe exactly where this happens.
-
I recorded a video of this error))). I'm sending you the log)
I tried to update, it gives the same error.https://youtu.be/KkVTgRstSwA (https://youtu.be/KkVTgRstSwA)
couatl v5.0 (build 5792)
panic log started on Fri Jun 6 20:41:32 2025
problem raised by addon <no traceback available>
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 8: unexpected end of data
{'User Pos': (0.00040803073839481115, 0.01397450300629543, 4.76623 m, 4.76623 m, 0.00013246154357770786, 0.010129351165796892, -0.003490658476948738, 8.755020621750958e-05, 4.611624034881592, 1.0)}
-
The video is useless, I already know from the small panic log it happened while loading. I need a complete log, nothing else.
-
and where can I find the log?
Please tell me). path to the log)
-
I'll send you what I found. I don't know if it's here or not.
\AppData\Roaming\virtuali
Couatl.err
couatl v5.0 (build 5792)
panic log started on Fri Jun 6 20:41:32 2025
problem raised by addon <no traceback available>
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 8: unexpected end of data
{'User Pos': (0.00040803073839481115, 0.01397450300629543, 4.76623 m, 4.76623 m, 0.00013246154357770786, 0.010129351165796892, -0.003490658476948738, 8.755020621750958e-05, 4.611624034881592, 1.0)}
_______________________________________________________
couatl64_boot
06.06.2025 20:34:19: Couatl64_boot Log started
06.06.2025 20:34:19: Working folder set to C:\Program Files (x86)\Addon Manager\couatl64 according to FSDT registry root key
06.06.2025 20:34:19: Thread "couatl64_MSFS.exe" added to monitoring
06.06.2025 20:34:19: Starting couatl64_MSFS.exe
06.06.2025 20:34:19: Process Couatl64_MSFS started successfully with ID 24492
06.06.2025 20:34:20: Connected to Couatl64 shared memory
06.06.2025 20:41:20: No processes found for couatl64_MSFS.exe during update
06.06.2025 20:41:20: Process is null or has exited. Attempting to restart.
06.06.2025 20:41:20: RESTARTING couatl64_MSFS.exe
06.06.2025 20:41:20: Process Couatl64_MSFS started successfully with ID 23232
06.06.2025 20:41:20: Setting focus back to FlightSimulator
06.06.2025 20:41:20: SetForegroundWindow for FlightSimulator
06.06.2025 20:42:20: No processes found for couatl64_MSFS.exe during update
06.06.2025 20:42:20: Process is null or has exited. Attempting to restart.
06.06.2025 20:42:20: RESTARTING couatl64_MSFS.exe
06.06.2025 20:42:20: Process Couatl64_MSFS started successfully with ID 23376
06.06.2025 20:42:20: Setting focus back to FlightSimulator
06.06.2025 20:42:20: SetForegroundWindow for FlightSimulator
06.06.2025 20:42:45: MSFS has exited
06.06.2025 20:42:45: Task was cancelled.
-
You posted the auto restarter log, which is not what I need. You must post the Couatl.log instead. There's a Sticky thread in this folder which explains how to enabled it and where it is.
Also the GSX manual, of course, Page 38.
-
Running in mode: Microsoft Flight Simulator
-
Running in mode: Microsoft Flight Simulator
Please do not quote the log, but ZIP it and ATTACH it to a post, as explained in the Sticky thread I discussed before. The reason for this, is the forum software can change it, and (especially when dealing with encoding issues), we need to look at the actual file, not its interpretation from the forum software that might alter it.
-
ok
-
Can you check the livery used and post your aircraft.cfg ( ZIPPED!!! ) ? Your error seems very similar to this one:
https://www.fsdreamteam.com/forum/index.php/topic,33282.msg209440.html#msg209440
-
Here is the file, question, everything worked before the update)
-
I updated the file and now everything works)))). Thank you)))