Author Topic: GSX remains in "deep sleep" when arriving. Menu is still at the Origin...  (Read 297 times)

FerrevmVnion

  • Jr. Member
  • **
  • Posts: 95
Hi,

i dont know how to explain the problem properly .... i try it in a short way:

- At the Origin GSX works fine, no issues ...
- When opening the Menu to select a parking position, GSX shows still the origin airport
- A restart via Menu seems to start as the menu closes ... but when re-opening the menu ... still the origin airport
- Kill Couatl64_MSFS2024.exe, Couatl64_boot.exe via the task manager doesnt change anything ... menu still at the origin airport
- I think what helps to get GSX awake is a combination of first klling the processes, switch to (what ever menu it is by ESC), leave it by ESC and then restart Couatl64_MSFS2024.exe (not the boot digends) ... im not sure about the right order of this spell, but kind this way it works...

Just look by yourself and hopefully you can provide some helpful ideas to get behind this spell of getting GSX back to life.
Disable GSX Option in cruise is unchecked. if i should bet on something it would say 'simconnect' but only as "ESC-ing" is involved in this spell.


Richard1000

  • Newbie
  • *
  • Posts: 42
Used to get this too, but recently all seems OK. Maybe a recent update fixed it?
Richard

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51917
    • VIRTUALI Sagl
According to the log shown in your video, after you restarted the Couatl engine, GSX worked normally, and it tried to tell you can't use GSX when you have the engines running. But since you disable the (all useful) aural alerts, you couldn't hear the warning.

FerrevmVnion

  • Jr. Member
  • **
  • Posts: 95
Yes, i forgot about the engines ... but the problem is to get gsx back to the state on which it is able to provide Ground Service when engines are shutdown ... thats the main problem :)

FerrevmVnion

  • Jr. Member
  • **
  • Posts: 95
@Virtuali .... it happend again... the log off the "died" GSX-Session just stops shortly after departure (unfortunetly there are no timestamps),
but last -

modified timestamp of windows shows 14.03.2025 20:20 UTC
Take-Off Roll at 20:15 UTC.


WER shows  a .NET Runtime Error of coutl64_msfs2024.exe at 20:20 UTC
Code: [Select]
-
- <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-03-14T20:20:59.9401622Z" />
  <EventRecordID>113543</EventRecordID>
  <Correlation />
  <Execution ProcessID="23440" ThreadID="0" />
  <Channel>Application</Channel>
  <Computer>BASTI-PC</Computer>
  <Security />
  </System>
- <EventData>
  <Data>Anwendung: Couatl64_MSFS2024.exe Frameworkversion: v4.0.30319 Beschreibung: Der Prozess wurde aufgrund eines internen Fehlers in der .NET-Laufzeit beendet. bei IP 00007FFBA2DB657C (00007FFBA2DB0000) mit Exitcode 80131506.</Data>
  </EventData>
  </Event>


Followed by another error (clr.dll) at

Code: [Select]
- <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-03-14T20:21:00.1766725Z" />
  <EventRecordID>113544</EventRecordID>
  <Correlation />
  <Execution ProcessID="22496" ThreadID="6168" />
  <Channel>Application</Channel>
  <Computer>BASTI-PC</Computer>
  <Security UserID="S-1-5-21-1266669442-3539115018-2653650737-1001" />
  </System>
- <EventData>
  <Data Name="AppName">Couatl64_MSFS2024.exe</Data>
  <Data Name="AppVersion">5.0.0.5594</Data>
  <Data Name="AppTimeStamp">67a63a4a</Data>
  <Data Name="ModuleName">clr.dll</Data>
  <Data Name="ModuleVersion">4.8.9290.0</Data>
  <Data Name="ModuleTimeStamp">67214bca</Data>
  <Data Name="ExceptionCode">c0000005</Data>
  <Data Name="FaultingOffset">000000000000657c</Data>
  <Data Name="ProcessId">0x5b90</Data>
  <Data Name="ProcessCreationTime">0x1db9517b44fd8b3</Data>
  <Data Name="AppPath">C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS2024.exe</Data>
  <Data Name="ModulePath">C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll</Data>
  <Data Name="IntegratorReportId">23ed04a4-c916-4cb8-a550-fa4d45027774</Data>
  <Data Name="PackageFullName" />
  <Data Name="PackageRelativeAppId" />
  </EventData>
  </Event>



Any idea.... i dont like these .net issues, .net repair tools doesnt work (or im too stupid too get it work)

In advanced (sfc /scannow) done (as alsways: nothing found, firewall turned off, GSX and all folders are excluded of anti virus)
« Last Edit: March 14, 2025, 11:05:13 pm by FerrevmVnion »