July 14, 201213 yr I get frequently this message, even after removing LINDA from the modules directory (i.e. Linda.exe and ipcready.lua). Any idea? best regards, Peter
July 14, 201213 yr Commercial Member This message could appear ONLY if linda.exe is running and you save new assignments. Artem Crum, EASA PPL•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••LINDA → Lua Integrated Non-complex Device Assigning•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
July 14, 201213 yr Author Wow, thanks for the quick reply. However, Linda is definitely not running, and I have even removed the ipcready.lua to prevent the linda-startup script for being executed. I cannot find any reference in the FSUIPC.log either and searched already a lot of files for the string. So far only found in LINDA's "events.lua" This is my setup: FSX-ACC FSUIPC (licensed) SPAD-Driver --> mostly mapped to FSUIPC virtual buttons HIDMacros.exe --> the same FSINN AES (only free parts) PS: Maybe you saw my post in the Dev-board on how to get the Saitek-Panels adressed in LUA/FSUIPC?
July 17, 201213 yr Author Ok, the thing is solved. Obviously, among many other things, FSUIPC saves also messages that were created by add-ons (like LINDA) in binary files named <FlightName>.ipcbin. Me setup of FSUIPC was configured always to load the ipcbin-File associated to the current flight file. As the ipcbin-file of the default flight contained the LINDA-message, it was occasionally reproduced under not so clear conditions (I think it was when FSUIPC considered to re-initialize itself). Once I deleted the ipcbin-File the ghost has gone.
Create an account or sign in to comment