Couatl Debug Window - how to disable ?

[achmedfsx]

Since the update today morning, I get a window "Couatl Debug Window" ~30 seconds after the Prepar3D (4.5 HF3) logo appears. Another 30 seconds later, the Prepar3D "scenario" Window appears.

If I close the "Couatl Debug Window" while P3D is running, GSX and XPOI aren't visible in P3D "Addon" menu any longer and the add-on manager tells me that GSX and XPOI run in "trial mode".

I found Couatl.ini in C:\Users\Achmed\AppData\Roaming\Virtuali with logFile="" so I changed it to logFile="couatl.log" assuming that the log would go either to the "Couatl Debug Window" or the logFile, but it only fills the couatl.log in addition to  the "Couatl Debug Window" (same content). The "Couatl Debug Window" is shown further.

As I never have seen this "Couatl Debug Window" before and it doesn't show any error at P3D startup, just these few messages until the P3D scenario window appears, I don't think it's needed.:

Code: [Select]

ython 2.7.16 Stackless 3.1b3 060516 (default, Mar  9 2019, 21:32:11) [MSC v.1500 64 bit (AMD64)] wxPython 3.0.2.0
couatl v4.8 (build 4800)
log started on Sat Aug 20 21:12:58 2022

connecting to SimConnect...
connected to SimConnect
connected to bglmanx

So is it possible to disable this "Couatl Debug Window" ?

[virtuali]

Try this installer, it's not MSFS-specific, it's just an offline copy of the files you were *supposed* to get from the servers:

http://www.fsdreamteam.com/forum/index.php/topic,26480.msg175191.html#msg175191

Before we can look into possible issues, we need to be sure you get the right files.

[achmedfsx]

Sorry, didn't find time because of the nice motorbike weather...now this evening, I executed the "Addon Manager.exe" from your link (after stopping Kaspersky):
No change. Starting P3D 4.5 HF3 shows "Couatl Debug Window" ~30 seconds after the P3D splash screen appeared.
Same content as before:

Code: [Select]

Python 2.7.16 Stackless 3.1b3 060516 (default, Mar  9 2019, 21:32:11) [MSC v.1500 64 bit (AMD64)] wxPython 3.0.2.0
couatl v4.8 (build 4800)
log started on Mon Aug 22 20:01:52 2022

connecting to SimConnect...
connected to SimConnect
bglmanx non ready yet, waiting.
connected to bglmanx
View changed to Virtual Cockpit

I checked the add-on.xml:

Code: [Select]

<?xml version="1.0" encoding="utf-8"?>
<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
  <AddOn.Name>FsDreamTeam Addon Manager</AddOn.Name>
  <AddOn.Description>FsDreamTeam Support software</AddOn.Description>
  <AddOn.Component>
    <Category>DLL</Category>
    <Path>C:\Games\FSDT\Addon Manager\bglmanx64.dll</Path>
    <DLLType>PDK</DLLType>
  </AddOn.Component>
  <AddOn.Component>
    <Category>Scripts</Category>
    <Path>C:\Games\FSDT\Addon Manager\Scripts</Path>
  </AddOn.Component>
  <AddOn.Component>
    <Category>Effects</Category>
    <Path>C:\Games\FSDT\Addon Manager\Effects</Path>
  </AddOn.Component>
  <AddOn.Component>
    <Category>Sound</Category>
    <Path>C:\Games\FSDT\Addon Manager\Sound</Path>
  </AddOn.Component>
  <AddOn.Component>
    <Category>SimObjects</Category>
    <Path>C:\Games\FSDT\Addon Manager\Simobjects\Misc</Path>
  </AddOn.Component>
  <AddOn.Component>
    <Category>SimObjects</Category>
    <Path>C:\Games\FSDT\Addon Manager\Simobjects\PBR</Path>
  </AddOn.Component>
  <AddOn.Component>
    <Category>EXE</Category>
    <Path>C:\Games\FSDT\Addon Manager\couatl64\Couatl64_P3D.exe</Path>
  </AddOn.Component>
</SimBase.Document>
Then I checked the signature of the above C:\Games\FSDT\Addon Manager\bglmanx64.dll:
Name: VIRTUALI Sagl
Signing time: ‎Saturday, ‎August ‎13, ‎2022 11:43:25 PM
Details - File version: 5.0.0.4
Date modified: 8/13/2022 11:43 PM
Original filename bglmanx.dll

Checked also couatl64_P3D.exe:
Name: VIRTUALI Sagl
Signing time: ‎Friday, ‎August ‎19, ‎2022 1:31:41 PM
Details - File Version: 4.8.0.4800
Date modified 8/19/2022 1:31 PM
Original filename: Couatl.exe


But...as it's not a critical problem in my case (I simply left the Couatl Debug Window open while flying - on a short flight, I didn't notice any side effects in P3D) and I use GSX very rarely and even don't use P3D every day, you may care about other problems with higher priority first.

[achmedfsx]

The FSDT update saturday evening (couatl64_P3D.exe : signed on ‎Saturday, ‎August ‎27, ‎2022 2:50:01 AM),
has stopped the Couatl Debug Window.

Started P3D today 2-3 times with/without admin rights, no problem.

[achmedfsx]

Too fast - Couatl Debug Window is back.
Maybe somebody knows how to stop the appearance of this Debug Window while P3D shows its logo ?

What's strange: although LORBY shows packages
- bglmanx64.dll (Properties-Details: 5.0.0.4) and
- couatl64\Couatl64_P3D.exe (Properties-Details: 4.8.0.4817)

in line 1 of the debug window it states:
Python 2.7.13 Stackless 3.1b3 060516 (default, May 22 2017, 13:45:26) [MSC v.1900 32 bit (Intel)] wxPython 3.0.2.0
that fits to couatl\couatl.exe (Properties-Details: 3.2.0.4792).

The add-on folder's add-on.xml contains the right entries for 64bit:
...
<AddOn.Component>
    <Category>DLL</Category>
    <Path>C:\Games\FSDT\Addon Manager\bglmanx64.dll</Path>
    <DLLType>PDK</DLLType>
  </AddOn.Component>
...
 <AddOn.Component>
    <Category>EXE</Category>
    <Path>C:\Games\FSDT\Addon Manager\couatl64\Couatl64_P3D.exe</Path>
  </AddOn.Component>
...

In Process Explorer under P3D, I find only couatl.exe but not couatl64.exe.

So why and where does P3D 4.5 start the couatl 32bit version ?
I will try to find it out...