Sign in to follow this  
Don Quixote

P3D 2.5: LINDA starts, but doesn't work

Recommended Posts

Hi everyone,

I've been using LINDA for a couple of months now, and first of all, a big THANK YOU! to those that have created this wonderful addon. It makes setting up controls so much easier, I wouldn't know what to do without it anymore. :lol:

Anyway, I recently did a complete re- install of my system, including P3D 2.5. Since then I'm experiencing a problem with LINDA (using 2.6.3 "v2"). Whenever P3D starts, the LINDA module (linda.exe) is started as well, as it should be. In the sim the LUA display saying "Linda is ready..." appears as usual. However, none of the key commands assigned through LINDA work, no matter what I do.

When opening the LINDA interface, it is impossible to activate FSX sync or to reload the LUA engine (buttons are greyed out).

The only workaround is to close the LINDA interface and re- start it (without closing P3D). In most cases it now works fine, although occasionally it needed another LINDA restart until it worked.

 

My P3D verison is 2.5.12946.0. OS is Win 7 Home premium 64bit. All the simconnect versions that came with P3D are installed.

 

 

I don't know if it's any help but here are the contents of linda2.log (not sure if there's any other log file around):

 

Init LINDA 2.6.8 ...
Can start...
Creating forms...
LINDA Ver 2.6.8 (147) GUI starting...
Fonts added
Sys Config loaded
VRI config loaded
HID Devices loaded
HID Definitions loaded
HID config loaded
Selector initialized
News read
Main Timer started
--> Main form: done!
--> Viewer form: done!
--> Input form: done!
--> FSX controls form: done!
--> Console form: done!
--> Macros form: done!
--> Module form: done!
--> Editor form: done!
HID OnArrival 4F677C0=044F/0402
HID OnArrival 4F67940=044F/0404
HID OnArrival 4F67AC0=046D/C226
HID OnArrival 4F67A00=046D/C226
HID OnArrival 4F67B80=046D/C226
HID OnArrival 4F67DC0=046D/C227
HID OnArrival 4F67F40=046D/C227
HID OnArrival 4F680C0=046D/C52B
HID OnArrival 4F67C40=046D/C52B
HID OnArrival 4F68180=046D/C52B
HID OnArrival 4F68240=046D/C52B
HID OnArrival 4F68300=046D/C52B
HID OnArrival 4F683C0=046D/C52B
HID OnArrival 4F68480=046D/C52B
HID OnArrival 4F68540=046D/C52B
HID OnArrival 4F46E40=06A3/0763
HID OnDeviceChange
HID IsJoystick test = 4F677C0=044F/0402 = Joystick
HID IsJoystick test = 4F67940=044F/0404 = Joystick
HID IsJoystick test = 4F67AC0=046D/C226 = Keyboard
HID IsJoystick test = 4F67A00=046D/C226 = 1
HID IsJoystick test = 4F67B80=046D/C226 = 1
HID IsJoystick test = 4F67DC0=046D/C227 = Keypad
HID IsJoystick test = 4F67F40=046D/C227 = 0
HID IsJoystick test = 4F680C0=046D/C52B = Keyboard
HID IsJoystick test = 4F67C40=046D/C52B = Mouse
HID IsJoystick test = 4F68180=046D/C52B = 1
HID IsJoystick test = 4F68240=046D/C52B = System Control
HID IsJoystick test = 4F68300=046D/C52B = 88
HID IsJoystick test = 4F683C0=046D/C52B = 1
HID IsJoystick test = 4F68480=046D/C52B = 2
HID IsJoystick test = 4F68540=046D/C52B = 4
HID IsJoystick test = 4F46E40=06A3/0763 = Joystick
HID OnDeviceChange

 

 

 

Any ideas what could cause this problem? Help would be greatly appreciated...

Cheers,

Steve

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I only used Linda once since I switched to P3D 2.5, but I also had the problem that it started but didn't work properly (no LVars in the tracer). I was able to fix this by starting the FSX to P3D migration tool and enable virtual FSX.

 

Peter

Share this post


Link to post
Share on other sites

Thanks for your reply Peter,

I actually have the Migration Tool as well, but since LINDA worked perfectly fine in 2.4 without virtual FSX enabled I'm not sure if it really is required...

Share this post


Link to post
Share on other sites

Hi everyone,

 

I've been using LINDA for a couple of months now, and first of all, a big THANK YOU! to those that have created this wonderful addon. It makes setting up controls so much easier, I wouldn't know what to do without it anymore. :lol:

 

Anyway, I recently did a complete re- install of my system, including P3D 2.5. Since then I'm experiencing a problem with LINDA (using 2.6.3 "v2"). Whenever P3D starts, the LINDA module (linda.exe) is started as well, as it should be. In the sim the LUA display saying "Linda is ready..." appears as usual. However, none of the key commands assigned through LINDA work, no matter what I do.

 

When opening the LINDA interface, it is impossible to activate FSX sync or to reload the LUA engine (buttons are greyed out).

 

The only workaround is to close the LINDA interface and re- start it (without closing P3D). In most cases it now works fine, although occasionally it needed another LINDA restart until it worked.

 

My P3D verison is 2.5.12946.0. OS is Win 7 Home premium 64bit. All the simconnect versions that came with P3D are installed.

Hi Don Quixote

 

Thank you for your detailed post and sorry to hear you are experiencing problems.  I am using LINDA successfully with P3D 2.5 mainly with the Aerosoft Airbus A318/A319/A320/A321 and A2A C172 and C182.

 

First of all, the Migration Tool does not affect the way LINDA is installed (manually) or how it worked with P3D 2.5.  What you don't say is which aircraft you are using. Unless you have the correct aircraft selected in the top dropdown and FSX Sync are orange, none of your key assignment will work. There is an issue if there are more than one sim aircraft or LINDA module with the same name - this has hit users (including me) of the A2A C172 and Aerosoft Airbus. You need to make sure there are no duplicate folder names in /p3d/modules/aircrafts/linda and /linda-cfg.

 

You say you have done a complete reinstall, so I assume you have had LINDA working in the past. An obvious question. You have reinstalled the LINDA aircraft modules for those you wish to fly?  

 

There is an small anomaly in your linda2.log file where is says version 2.6.8 (147).  I think this was a typo on my part as the build number (147) is correct.  What I need to see is a cut-and-paste of the LINDA console output (email to linda@awginfosys.net).

 

Report back on your progress and I will tried to get you sorted.

Share this post


Link to post
Share on other sites

 

 


What you don't say is which aircraft you are using. [...] There is an issue if there are more than one sim aircraft or LINDA module with the same name - this has hit users (including me) of the A2A C172 and Aerosoft Airbus. You need to make sure there are no duplicate folder names in /p3d/modules/aircrafts/linda and /linda-cfg.

You say you have done a complete reinstall, so I assume you have had LINDA working in the past. An obvious question. You have reinstalled the LINDA aircraft modules for those you wish to fly?

 

Thanks for your reply! I'm using several modules/aircraft (Flight1 DC9, A2A Cherokee, Majestic Q400, and others) but the problem is the same with all of them.

When I installed Linda I simply copied all the modules and configs from my old install into the new one. Maybe that wasn't such a good idea? I've now removed all the modules and config files (except for the default one) and now LINDA seems to be working just fine. I guess that means that the problem is with one of the modules. I'll try and add them one by one to see which one causes the issue. I'll let you know if I can find the faulty one.

 

Cheers!

Steve

Share this post


Link to post
Share on other sites

Update:

I was wrong about the modules - after restarting Windows, I had the same problem once again (LINDA starts, but FSX sync button is greyed out, as is "reload LUA engine"). This was with just the default modules installed.

 

What I noticed instead was that the timing seems to be critical: Normally LINDA starts along with P3D.exe. Apparently, LINDA doesn't recognise that P3D is running in this case. However, if LINDA is started after free flight menu has loaded - which takes about a minute or so - it connects to P3D and works fine.

Since that's straightforward enough, I fixedit by applying some Windows duct tape... Meaning, made a simple batch file that starts P3D, waits 60 seconds, then starts LINDA. Not exactly an elegant solution but it works. :lol:

 

Thanks again,

Steve

Share this post


Link to post
Share on other sites

Click the start  with FS button. It will add an entry to FSUIPC.ini which will start it. 

Share this post


Link to post
Share on other sites

That's not the problem - I did have the "start with FS" option enabled, which worked perfectly in P3D 2.4, but not unfortunately in 2.5. As mentioned, it seems that if LINDA starts simultaneously with P3D (which is the case if the "start with FS" box is ticked) it doesn't connect to the sim. If, however, LINDA is started *after* P3D, it connects and works fine. That's what I'm doing with a simple batch file. Doing it manually works too of course.

Share this post


Link to post
Share on other sites

Hi Steve

 

As David has correctly pointed out, you need to go to the LINDA Settings page and make sure that the Start with Sim box is checked.  Also check the other options are as you previously have them.

Share this post


Link to post
Share on other sites

Also ther can not be any errors in the aircraft LUA scrips (\Prepar3d v2\modules\linda\aircraft\your aircraft\actions.lua). make sure to open the file in the LUA Editor. Just learned this my self.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this