Products Support > Dallas FSX/P3D

Trial period

<< < (3/3)

virtuali:

--- Quote from: skip d on July 12, 2023, 01:02:05 am ---went to Couatl.ini...opened...
only thing in it was...logfile=etc,etc.
--- End quote ---

You are assuming here you are supposed to see other things in the .INI file, but that's not what the .INI is used for. You use the .INI file to enable logging, that's it.

If you do it correctly, when the program starts, you are supposed to see A NEW FILE, called Couatl.LOG, in the path you specified there. In fact, I suggest not adding a path, which will only increase the chance of mistakes, instead, make the line as simple as this:

logFile=Couatl.LOG

which will create the Couatl.LOG file in the current folder, the same with the .INI you edited.

If you still don't see the Couatl.LOG file, it means the problem is REALLY the antivirus, because if it blocked it, it blocked the log creation as well.

skip d:
I opened "Couatl.ini" and changed the text to "logFile=Couatl.LOG" and saved.
Made sure I had added an "Exception" to my Avast AV.
Started P3Dv5.4 and started sim menu. Clicked on"Add-On" and got the FSDT Mngr.
Clicked on "Register Serial" and received the same message "The Couatl scripting engine hasn't started...etc,etc"
Opened the Couatl.ini file and found only...."logFile=Couatl.LOG"
still stumped...

virtuali:
Then I can only repeat this:

If you still don't see the Couatl.LOG file, it means the problem is REALLY the antivirus, because if it blocked it, it blocked the log creation as well.

skip d:
I recently uninstalled GSX 1&2 ....due to all sorts of complications.
Do I need to have GSX installed in order to get KDFW to work ??
Thanks

Navigation

[0] Message Index

[*] Previous page