Hello,
I just updated my version 3.0.12 to 3.1.1.4 and I can no longer save the linda-gui.ini with the following options:
Developer mode ticked
Associate with * .lua ticked
Debug mode Detailed GUI and LUA
When launching Linda the advanced parameters are reset to default values.
Bad update from me?
Thank you in advance for your help.
Regards.
Francis.

Edited March 4, 20206 yr by nervures

Ensure you are running LINDA in admin mode. Follow Fault Diagnosis procedure thread (under LINDA Support) so I can see the logs. 

Hi,

yes Linda runs in admin mode.

When I turn ON Fault Diagnosis Mode it's ok ( Tracer and Editor are active ) but impossible to keep detailed mode active when I re launch Linda already "verbose" .

Francis.

Edited March 4, 20206 yr by nervures

I need to see the logs to what the problem may be. 

Not at home for now. I will send this night.

Hi,

requested files sent to LINDA @ awginfosys.net.

Regards.

Francis. 

 

Edited March 4, 20206 yr by ScotFlieger

Files received thank you. It will be tomorrow before I can examine them fully.

Thank you again for the logs. 

The Linda-gui.ini file has been corrupted with non-LINDA data. The only LINDA blocks should be [Logging], [General] and [Windows]. The [Tracer] block and all those below with SimConnectWindow and LUA display would not be expected. Also there should be no view (Vue) or camera information. Make sure you do not have any additional debug settings ticked in FSUIPC Logging.

The fact that 2 different applications appear to be write to this INI file would account for the access permission errors.

I recommend that you delete the existing linda-gui.ini file and start again. It will be regenerated when LINDA runs.

EDIT: You also have an unknown LUA file running (777COM.LUA). What is this?

Edited March 5, 20206 yr by ScotFlieger
Extra question added.

Hello,

thank you for your reply.

I am at work until 7 p.m. I will follow your comments but what I would like to know is why in version 3.0.12 it worked ?

The 777COM.lua is a script for an automatic backup that I made and which monitors the offset 0x66FF.

Until version 3.0.12 I never had any problems. My linda-gui.ini has always been like this.

I'll keep you informed.

Regards.

Francis.

There could be various reasons. Upgrades to Win10 have tightened security and creating several unexpected errors. I do not know why LINDA 3.0.12 worked for you and 3.1.1 is creating problems. The use of linda-gui.lua has changed to cope with the need to provide all users with a set way to run fault diagnosis mode. All I will say is that I can only support LINDA as issued and we rely on base files remaining as distributed.

If 777COM.lua writes to linda-gui.lua to add the extra lines then I urge you to use your own unique .ini file.

Sorry to jump in here, but I have also found a problem with 3.1.1.  Every time that I load LINDA and want to use theTracer I have to "Select LINDA" and tick Developer, because that setting is not saved.
There is nothing in the linda-gui.ini file that shouldn't be there, judging from what you commented on the OP's file.  I run LINDA in administrator mode, and P3D is installed on its own dedicated SSD.
It's a bit of a nuisance having to do this to run the tracer, but at least I can get it to run.  It's something you may want to look into at some stage though.

Hi @EmileB thank you for the report. LINDA 3.1.1 introduced a Fault Diagnosis Mode for those users you can't read and/or follow debugging guidance. This overrides the Developer and Logging settings. Go to the Maintenance page and Turn Fault Diagnosis Mode ON.

 

 

Edited March 23, 20206 yr by ScotFlieger

21 hours ago, ScotFlieger said:

Hi @EmileB thank you for the report. LINDA 3.1.1 introduced a Fault Diagnosis Mode for those users you can't read and/or follow debugging guidance. This overrides the Developer and Logging settings. Go to the Maintenance page and Turn Fault Diagnosis Mode ON.

Thanks a lot for your quick reply, Andrew, will try it out.

Edited March 24, 20206 yr by EmileB