FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: flare_alfred on December 27, 2024, 08:11:43 am
-
I previously asked about an issue where I could no longer select a sound device with GSX PRO and no sound came out at all, but it was resolved by deleting CouatlAddons.ini and restarting the computer.
However, after the latest update, sound has stopped coming out again.
The error log is below.
<Couatl.errFile>
[KIAH2] is active
Live Update failed, HTTP header has no ETag
Main Menu loaded
Slew mode False
Common onAppStart
createDefaultContainer
Current locale is Japanese_Japan.932
Initializing audio...
Error initializing AudioManager: 'charmap' codec can't decode byte 0x81 in position 24: character maps to <undefined>
Simulator version (from MAIN.DLL) 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
Cleared menu entries
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
GSX SimStart
It's clear that sound initialization has failed, but please tell me the cause and solution.
<data>
・Windows10 64bit Japanese
・Sound Blaster Audigy Rx
・open AL 11 installed
・Antivirus software has been excluded.
thank you.
-
I asked an acquaintance who is knowledgeable about the error, and it seems that it's clearly caused by double-byte code.
It's been a long time since the double-byte code problem was first reported, but it still hasn't been fixed.
I hope it will be fixed soon.
-
I haven't received a response from the FSDT team, but is it really that difficult to fix this bug?
Many people are experiencing the same symptoms, and it's very frustrating to have this problem occur every time there's an update.
Please take action as soon as possible.
-
Yes, it's very difficult, if not impossible, to fix this problem, since it seems to be caused only by some audio drivers running in Asian versions of Windows.
-
Sometimes sound works if I delete CouatlAddons.ini while MSFS is running and then restart the MSFS, so it might just be that audio initialization has failed.
If this is resolved, how long do I have to wait?
Or are there no plans to fix this problem?
Thanks.
-
Why did sound suddenly stop working when it had been working before?
Did you change anything?
Please let me know what to do, even if it's just a temporary fix.
-
We haven't changed anything in the sound handling since we added support for multiple audio devices, back in October 2023, with a few hotfixes in the following weeks, but nothing after that has changed.
-
Understood.
But it is true that many people are facing the same problem.
How do you respond to this?
Are you going to leave this issue alone?
Or are you planning to fix it?