Updating from v2.8.7 and restoring the HID lua leads to:

 

 

and the joystick settings are not loaded.

 

If I delete the hid.lua and start afresh then upon the next restart the joystick settings are not loaded although contained in the LUA.

 

FSUIPC 4.959m in use.

 

Restoring v2.8.7 and all works as expected.

Hi Stephen

 

First off the current version of LINDA is 2.8.8. But to answer your question.

 

The LINDA system file \modules\linda-cfg\system\config-hid.lua contains details of all previous joysticks you have used on your system. The 044F indicates a Thrustmaster joystick. Deleting the file will cause the error report as your PDMG 737NGX was previously used with these devices. Restoring the file resolved the problem.

 

If you have disposed of the Thrustmaster joysticks, you can edit the reported file to remove the 044F04040 and 044F04020 entries.

The TM joystick and throttle remain connected, just not recognized by v288 upon loading. As mentioned even if I start a fresh joystick configuration the TM settings are not recognized on subsequent loading.

 

If I revert to v287 then there is no issue at all.

Please email me the following files to [email protected] after running both LINDA 2.8.7 and 2.8.8.

 

\modules\fsuipc4.log

\modules\linda-cfg\aircrafts\{the affect aircraft}\config-hid.lua

\modules\linda-cfg\system\system\config-hid.lua

Email not deliverable to that address Scot.

 

EDIT: sent links via PM

Thanks for the info. It may be your ISP that is blocking but the email tests OK for me.

 

Both config-hid.lua setups for 2.8.7 and 2.8.8 should work correctly. What I forgot to ask you was to select Verbose mode before sending me the FSUIPC4.log files. Could I ask you to repeat the tests again with Verbose logging set? Sorry.

I cannot see a 'Verbose' log setting in FSUIPC or LINDA, only simconnect ?

Select LINDA setup and tick Developer Mode, the select Verbose from drop down list at bottom. Alternatively open up LINDA console. It is repeated there.

Links re-sent via PM with verbose enabled

Hi Stephen

 

Your 2.8.8 log contains an error that we have just spotted with the init.lua failing to open an EVENT for the MCP (line 173) - see error line in Red.

 

This error will stop LINDA working. It is not something we have seen before and may be related to the latest versions of FSUIPC4. The workaround is to click on Reload LAU Engine which appears to clear it.

 

We are investigating the cause and will provide a permanent solution in due course. Thank you for your help supplying the log details.

The above errors reported with init.lua line 173 has been fixed by FSUIPC4 4.960 and other issues by LINDA 2.8.9 (446).

 

I have yet to find a permanent fix for the device not recognised error report.