Hi Matthias

 

The crashing problem is a new one that a number of users are experiencing.

 

Are you starting LINDA before FSX or is it set to start with the sim?  Did you do a completely clean installation as per instructions?

 

My first advice is to delete one file: \fsx\modules\linda-cfg\system\config-hid.lua.  The start LINDA, open console and then start FSX.  EMAIL me any linda2.log and console log to [email protected]. Please do not post on thread to save space.

 

The 5 sec delay is a small one due to the new code needed to allow Dynamic HID to work.

Thank you very much for the quick answer!!

 

LINDA is startet via FSUIPC.ini., so i will test to start LINDA manually before FSX is startet. And yes, i copied the Content of the extracted Folder MODULES to the FSX/Modules folder and accepted overwriting any existing files. So i should be a clean reinstall, i guess 

 

Will report back!

Ok,

 

did a quick test. I deleted the config-hid.lua as instructed, stared LINDA as Administrator and opened the console. Again FSX crashes as soon as the LUA Display appears. I send you the .log file via mail, but to my surprise, the console window does not Show any entry, it's just empty.

 

Matthias

Hi there,

 

Have just tested 2.6.2 and found that FSX doesn't crash if I load Linda and open the console window first.

 

FSX DOES crash as soon as I attempt to reload the Lua engine.

 

Weirdly the test assignment I made did not appear to function, which is why I tried reloading the Lua engine.

 

Back to 2.5.7 for now. This is probably driving you nuts. ;-)

Mh,

 

where can i find the 2.5.7 Version? I saw an entry with a patch file, and the info that you can find Version 2.5.7 at the bottom of the top post in the DOWNLOAD Sub Forum, but here it's midnight in a few moments and i guess my eyes are too tired to find :(

 

Matthias

 

Ok, sorry, guys, found the download link to 2.5.7. I guess i should go to bed now

Edited March 13, 201511 yr by ankh21

Hi Dbader

 

Thank you for that very useful report. I will test that combination tomorrow (too close to bedtime now).  What function assignment did you make?

Hi ankh21

 

You can find 2.5.7 here at the bottom of the post for 2.6.2. The patch is further down the thread.

Thank you very much!

 

As posted via EDIT i found it and went back to 2.5.7...and everything seems to be ok now, so my heart beat is back to normal  

 

Thanks for your Support and your help!

 

Matthias

 

 

Hi Dbader
 
Thank you for that very useful report. I will test that combination tomorrow (too close to bedtime now).  What function assignment did you make?

 
Heading bug fast decrease in the PMDG 737
Didn't have enough time to test other functions I'm afraid.

Thank you for your report and sorry to hear that you are having problems. The linda2.log file shows nothing amiss.

 

 

Scot I tried again wit 2.6.2 with same P3D closing result.

Fresh install using same procedure as in my post #23 above.

 

Init LINDA 2.6.2 ...

Can start...

Creating forms...

LINDA Ver 2.6.2 (140) 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 4C489F0=044F/0402

HID OnArrival 4C48B70=044F/0404

HID OnArrival 4C48C30=046D/0A1F

HID OnArrival 4C48CF0=046D/0A1F

HID OnArrival 4C48F30=046D/C52B

HID OnArrival 4C48DB0=046D/C52B

HID OnArrival 4C48FF0=046D/C52B

HID OnArrival 4C490B0=046D/C52B

HID OnArrival 4C49170=046D/C52B

HID OnArrival 4C49230=046D/C52B

HID OnArrival 4C492F0=046D/C52B

HID OnArrival 4C493B0=046D/C52B

HID OnArrival 4C495F0=046D/C537

HID OnArrival 4C49470=046D/C537

HID OnArrival 4C496B0=046D/C537

HID OnArrival 4C49770=046D/C537

HID OnArrival 4C49830=046D/C537

HID OnArrival 4C127E0=046D/C537

HID OnArrival 4C128A0=046D/C537

HID OnArrival 4C12A20=04D8/06E7

HID OnArrival 4C12BA0=06A3/0764

HID OnArrival 4C12D20=09F3/0040

HID OnArrival 4C12EA0=09F3/0200

HID OnDeviceChange

HID IsJoystick test = 4C489F0=044F/0402 = Joystick

HID IsJoystick test = 4C48B70=044F/0404 = Joystick

HID IsJoystick test = 4C48C30=046D/0A1F = 1

HID IsJoystick test = 4C48CF0=046D/0A1F = 1

HID IsJoystick test = 4C48F30=046D/C52B = Keyboard

HID IsJoystick test = 4C48DB0=046D/C52B = Mouse

HID IsJoystick test = 4C48FF0=046D/C52B = 1

HID IsJoystick test = 4C490B0=046D/C52B = System Control

HID IsJoystick test = 4C49170=046D/C52B = 88

HID IsJoystick test = 4C49230=046D/C52B = 1

HID IsJoystick test = 4C492F0=046D/C52B = 2

HID IsJoystick test = 4C493B0=046D/C52B = 4

HID IsJoystick test = 4C495F0=046D/C537 = Mouse

HID IsJoystick test = 4C49470=046D/C537 = Keyboard

HID IsJoystick test = 4C496B0=046D/C537 = 1

HID IsJoystick test = 4C49770=046D/C537 = System Control

HID IsJoystick test = 4C49830=046D/C537 = 1

HID IsJoystick test = 4C127E0=046D/C537 = 2

HID IsJoystick test = 4C128A0=046D/C537 = 80

HID IsJoystick test = 4C12A20=04D8/06E7 = Joystick

HID IsJoystick test = 4C12BA0=06A3/0764 = Joystick

HID IsJoystick test = 4C12D20=09F3/0040 = Flight

HID IsJoystick test = 4C12EA0=09F3/0200 = Joystick

 

 

Scot I tried again wit 2.6.2 with same P3D closing result.

 

Hi gboz

 

Thank you for the latest report.  I am using P3D 2.5 with 2.6.2 now and do not see any crashing.

 

Can you do a couple things for me?  Can you zip your complete \p3d\modules\ folder and email it to me at [email protected]?  Also I would ask you to try disconnecting all but one joystick from your system and test again.  This time email me the linda2.log.  Finally can you identify the PID numbers of your GoFlight LGT & TQ6 panels (VID=09F3 and PIDs either 0040 or 0200).

 

I wish to get to the bottom of this CTD problem because not all users are experiencing the issue.

 

 

Finally can you identify the PID numbers of your GoFlight LGT & TQ6 panels (VID=09F3 and PIDs either 0040 or 0200).

 

Scot where do I find these?

 

gb.

gboz,

 

Look in Device Manager,

Right click on the device -> properties ->( advanced ->) Details Tab -> Property -> Hardware Ids

gboz,

 

Look in Device Manager,

Right click on the device -> properties ->( advanced ->) Details Tab -> Property -> Hardware Ids

 

Thanks Scot.

Will get back with the other stuff.

 

This is for the USB device rather than the HID. Is that right?

 

Joystick - HOTAS Warthog

USB\VID_044F&PID_0402&REV_0100

USB\VID_044F&PID_0402

 

 

Throttle - HOTAS Warthog

USB\VID_044F&PID_0404&REV_0100

USB\VID_044F&PID_0404

 

 

GF-TQ6 Throttle System

USB\VID_09F3&PID_0200&REV_0100

USB\VID_09F3&PID_0200

 

 

Saitek Pro Flight Combat Rudder Pedals

USB\VID_06A3&PID_0764&REV_0201

USB\VID_06A3&PID_0764

 

 

GoFlight GF-LGT control module

USB\VID_09F3&PID_0040&REV_0102

USB\VID_09F3&PID_0040

 

 

Model 1010 FSX-FSUIPC

USB\VID_04D8&PID_06E7&REV_0001

USB\VID_04D8&PID_06E7

 

gb.

Update on LINDA Crashing To Desktop (CTD) during FSX/P3D start up.

 

The reported problem is that just after the scenery loading completes and the LINDA Ready To Go message displays, FSX stops working with the fault module ntdll.dll.

 

Thanks to those users who have generously sent me their \Modules folder, I have been able to reproduce the fault.  This is the first step in any software investigation. In 2 cases I have been able to pin down the problem to differences in the FSUIPC4.ini file.  When I insert my own copy of the file into their modules I do not get the crash, when I reinsert their copies I do. I am currently analysing why this could be case and will report back.

 

In the meantime, those experiencing this issue have reported that reverting back to 2.5.7 solves their problems.

Great news, Scot.  Find that little bugger and stomp on it!

As reported, I have pinned down the problem to some interaction between FSUIPC4.ini and 2.6.2. If I reinstall 2.5.7 there is no problem with any of the FSUIPC4.ini files I have been sent. However, 2.6.2 only works with my own FSUIPC4.ini and none of the others including a newly build one created by FSUIPC4. A line by line comparison between mine and other .ini files shows no differences that I can detect. The search goes on.