Recent Posts

Pages: [1] 2 3 ... 10
1
Are there any official staff members monitoring this forum? This issue has been reported by players in the iniBuilds, Fenix, and Microsoft Flight Simulator official communities as well. Is there any channel I can use to directly contact the developers?
2
Umberto,

We demand to know if you, or your team, are going to fix this problem with Louisville!!! I demand that this problem be fixed or refund my money! Don't give me this business that it works on your machine, it should work, or to run the live update!!!! Everyone has tried it and followed your instructions to the T and it still does NOT WORK!!! THIS is PROOF that it DOES NOT work!!! I'm fed up with posting here and you don't even reply nor lift a finger to investigate as to why the problem exist and what you or your team are going to do about this ONGOING PROBLEM!!! Just because it works on your machine DOES NOT mean that the problem doesn't exist!!!! YOU have been proven that the problem exist but YOU just continue to ignore that fact!!!! YOU need to post here what you intend to do about this!!!! You can't seem to get it through your head that this problem is ongoing because of YOUR live update and YOU just ignore that fact!!! I'm fed up with this lack of support and business practice and YOU just don't give a crap about investigating what the problem is!!!! I paid you money for this addon and DEMAND this this problem be fixed!!!! You seem to think that you have no accountability and you're not required to provide us support simply because you say it works on your machine!!!! The FACT is that this problem NEVER occurred until AFTER running a live update!!!! We're NOT posting here just for no reason!!!! We come here for support, and it is YOUR responsibility to see to it that our problems get fixed!!!! YOU have been proven that this addon DOESN'T work and YOU continue to ignore that FACT!!!! Yes, I'm very very very very angry because you don't seem to agree that this is an ongoing problem and the fact that YOU don't give a crap, YOUR LACK of support, and YOUR business practice!!!! This forum is supposed to be the place to come to for support and YOU are NOT providing it!!!! I've posted here multiple times and others have posted here proving that the addon DOESN'T work and YOU just ignore us!!!! I doubt YOU even come to this post and WE can ALL see that YOU have NO intentions to fix this problem!!!!

Ken.
3
For Lufthansa cabin crew members the same since last update to 3.7.3., no Lufthansa uniform, but generic with red scarf, no badge on uniform. PMDG 737-700. Aircraft config ICAO code is DLH.

I fixed my above topic by without the simulator running going into the D:\msfs\community\pmdg-aircraft-737-liveries directory which is my community directory on drive D: and the pmdg 737 liveries directory in there. I then placed the "mslayoutconfigurator.exe" file into that directory (downloaded from Github) and dropped the layout.json file onto the "mslayoutconfigurator.exe" with the mouse to update by this action the layout.json file.

After that having started MSFS2020 again and loading the PMDG-700 Lufthansa Livery the correct uniform showed up.
All working now.

That did not help for me.
I just compared the file before and after the layot generation and there was nothing add or removed.
Would be interested what has been changed in your file before and after.


BR
4
GSX Support MSFS / Universal Installer not locating ARPTS
« Last post by Dreamflight767 on Today at 05:36:37 am »
Hello:

I bought a few add-on airports for FS2020 this weekend.  I'm trying to disable jetways in the Universal Installer but the "Search Pattern" does not locate any airports.  Thank you.  GSX is up-to-date with 3.7.3.  I also tried to do a manual update of GSX as well.
5
Charlotte KCLT for MSFS / Re: Terrain issue with MSFS24 KCLT
« Last post by Floridaman on Today at 02:16:40 am »
I have the same issue with KCLT in SU3 the bump is there.
6
GSX Support MSFS / Re: No Services at Arrival Airport since Update 3.7.3
« Last post by lehbird on Today at 01:59:11 am »
Ok, thank you. Just very odd as I never had the problem before and now I have it 100% of the time.
7
Screenshot of event log....

8
GSX Support MSFS / Re: couatl64_MSFS2024.exe randomly crashing in the background
« Last post by 72westy on December 04, 2025, 11:02:35 pm »
I also ran the following commands (w/admin rights) and all completed successfully and without error/s. In the following order:

Dism.exe /online /Cleanup-Image /checkhealth

Dism.exe /online /Cleanup-Image /scanhealth

Dism.exe /online /Cleanup-Image /Restorehealth

sfc /scannow

Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

Dism.exe /Online /Cleanup-Image /StartComponentCleanup

RESTARTED computer as the last step.

I did prior to the aforementioned event log (on this page) deactivate and uninstall GSX and the sim (MSFS2024 - SU3) ran without any event log/s showing up for several days.

System specs:

MSI Codex Series R2 B14NUC7-095US
Windows 11 Home 25H2 26200.7309
i7 14700F
MSI Pro B760 VC Wifi II (AMI BIOS 7D98vBG 2025-09-04)
RTX 5060ti OC - Drivers 581.80
32GB DDR5 5600mhz
2TB MSI M482 nVME (C:)
Neo Forz a NFS011SA31T-60 SCSI Disk Device (E:)
Kingspec SATA SSD 4TB (I:)
4TB SPCC SSD 4TB (D:)
4TB Crucial CT4000P3PSSD8 nVME (F:) MSFS20/24 Installed here
Seagate Backup+ Drive (G:)
650w Gold PSU
9
GSX Support MSFS / Re: couatl64_MSFS2024.exe randomly crashing in the background
« Last post by 72westy on December 04, 2025, 10:56:40 pm »
Received these December 02, 2025...(MSFS 2024 SU3)


Log Name:      Application
Source:        Application Error
Date:          12/2/2025 1:50:24 PM
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Keywords:     
User:          DESKTOP-AFGL0LD\usnao
Computer:      DESKTOP-AFGL0LD
Description:
Faulting application name: couatl64_MSFS.exe, version: 5.0.0.6196, time stamp: 0x6915c947
Faulting module name: clr.dll, version: 4.8.9323.0, time stamp: 0x68c9b9f3
Exception code: 0xc0000005
Fault offset: 0x000000000000657c
Faulting process id: 0x29C8
Faulting application start time: 0x1DC63D2B7606078
Faulting application path: C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 0e4f3635-b11a-46db-b9a6-5bfcb5db42fd
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
    <EventID>1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2025-12-02T21:50:24.6014621Z" />
    <EventRecordID>88107</EventRecordID>
    <Correlation />
    <Execution ProcessID="8652" ThreadID="22396" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-AFGL0LD</Computer>
    <Security UserID="S-1-5-21-2400603791-3703659137-366786281-1002" />
  </System>
  <EventData>
    <Data Name="AppName">couatl64_MSFS.exe</Data>
    <Data Name="AppVersion">5.0.0.6196</Data>
    <Data Name="AppTimeStamp">6915c947</Data>
    <Data Name="ModuleName">clr.dll</Data>
    <Data Name="ModuleVersion">4.8.9323.0</Data>
    <Data Name="ModuleTimeStamp">68c9b9f3</Data>
    <Data Name="ExceptionCode">c0000005</Data>
    <Data Name="FaultingOffset">000000000000657c</Data>
    <Data Name="ProcessId">0x29c8</Data>
    <Data Name="ProcessCreationTime">0x1dc63d2b7606078</Data>
    <Data Name="AppPath">C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe</Data>
    <Data Name="ModulePath">C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll</Data>
    <Data Name="IntegratorReportId">0e4f3635-b11a-46db-b9a6-5bfcb5db42fd</Data>
    <Data Name="PackageFullName">
    </Data>
    <Data Name="PackageRelativeAppId">
    </Data>
  </EventData>
</Event>


Log Name:      Application
Source:        .NET Runtime
Date:          12/2/2025 1:50:24 PM
Event ID:      1023
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-AFGL0LD
Description:
Application: couatl64_MSFS.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFE6293657C (00007FFE62930000) with exit code 80131506.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1023</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2025-12-02T21:50:24.1097232Z" />
    <EventRecordID>88106</EventRecordID>
    <Correlation />
    <Execution ProcessID="10696" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-AFGL0LD</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: couatl64_MSFS.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFE6293657C (00007FFE62930000) with exit code 80131506.
</Data>
  </EventData>
</Event>
10
GSX Support MSFS / Re: VDGS showing wrong TTD
« Last post by EDWvManuel on December 04, 2025, 06:46:59 pm »
Perfect, I had -17:00. When can we expect the update?
Pages: [1] 2 3 ... 10