Encoding error message shown on screeen

[virtuali]

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.

[virtuali]

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.

[fpvsteve]

Sure - here is the link:

- Edit: Link removed for privacy and respect to VA -
Steve

[virtuali]

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.

[fpvsteve]

Perfect - glad we got to the bottom of it, thanks Umberto.

[fpvsteve]

Just confirming - amending the string to "" in the aircraft.cfg has fixed the issue I was having.

[tcttvfm]

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)

[virtuali]

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.

[tcttvfm]

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

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)}

[virtuali]

The video is useless, I already know from the small panic log it happened while loading. I need a complete log, nothing else.

[tcttvfm]

and where can I find the log?
Please tell me). path to the log)

[tcttvfm]

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.

[virtuali]

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.

[tcttvfm]

Running in mode: Microsoft Flight Simulator

[virtuali]

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.