Steering Tiller

[Heron 1B]

Hi Pete,

I have FSUIPC version 4.80, just been searching for MaxSteerSpeed=60 in the .ini folder but unable to locate. Has it been withdrawn?

I am aware the subject of tiller steering has been raised here many times but would like to clarify that rudders must be assigned and calibrated in FSUIPC to use MaxSteerSpeed, if you connect to the FS Rudder axis alone then MaxSteerSpeed can no longer be used.

I have Saitek Pro Pedals which by default connect via USB to the FS Axis and include toe brakes. Is it possible to override these FS calibration and assignment and reassign using FSUIPC and still have toe brake facility?

The tiller system I have is from SimParts, Stuttgart, USB connection via small BU0836 board.

Another question off subject reference PMDG 737NGX, whenever I attempt to allocate Button and Switches in FSUIPC and press o.k. FSX closes down, I get a warning "Flight Simulator must close". Does not matter if I select Aircraft Specific or use FS. This does not occur with other aircraft models only the 737NGX. Does using Profiles eliminate this?

Regards,

Derek Froud

[Pete Dowson]

I have FSUIPC version 4.80, just been searching for MaxSteerSpeed=60 in the .ini folder but unable to locate. Has it been withdrawn?

No. Are you looking in the right place? It's part of the [JoystickCalibration] section , which will only be there if you've calibrated something. It's there so it can be different for different aircraft, and it is only operable for direct to calibration axes in any case.

I am aware the subject of tiller steering has been raised here many times but would like to clarify that rudders must be assigned and calibrated in FSUIPC to use MaxSteerSpeed, if you connect to the FS Rudder axis alone then MaxSteerSpeed can no longer be used.

What could it be used for? It's an arbitration mechanism between two axes. Please read the boxed text on this in the User Guide. It explains it all there.

I have Saitek Pro Pedals which by default connect via USB to the FS Axis and include toe brakes. Is it possible to override these FS calibration and assignment and reassign using FSUIPC and still have toe brake facility?

FSUIPC cannot override FS assignments. It's one or the other. If you assign in both they will conflict. FSUIPC supports all possible FS axes and more than can be assigned in FSX in any case.

Another question off subject reference PMDG 737NGX, whenever I attempt to allocate Button and Switches in FSUIPC and press o.k. FSX closes down, I get a warning "Flight Simulator must close".

What!??? That's bad. Please see if this happens with the latest version -- 4.81 or 4.811 (see Download Links subforum). If it still crashes I need more information. It sounds like a corrupted INI file, so I'd like to see that please.

Pete

[Heron 1B]

Pete,

Installed version 4.81 and problem remains, Did a test creating macros and soon as I hit O.K. to close out the Flt Sim stops. Only when in the PMDG737NGX, I do have SP1c and the model runs perfectly.

Here is my .ini file,

[General]

UpdatedByVersion=4810

History=P41QMUX7E5WGJN72TIBWB

MouseWheelMove=No

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

DeleteVehiclesForAES=Yes

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=-4

MinIce=-4

UpperWindGusts=No

SuppressWindTurbulence=No

SuppressWindVariance=No

WindTurbulence=No

TurbulenceRate=0.5,2.5

TurbulenceDivisor=40,40,80,80

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=No

WindSmoothness=2

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=No

ShowPMcontrols=No

SpoilerIncrement=512

MagicBattery=Yes

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=3

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

BrakeReleaseThreshold=75

SaveDataWithFlights=No

ZapSound=firework

ShortAircraftNameOk=Yes

UseProfiles=No

EnableMouseLook=No

AxesWrongRange=No

TCASid=Type

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

Console=No

FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0

SimConnectUsed=10.0.61259.0

[JoyNames]

AutoAssignLetters=No

0=BU0836X Interface

0.GUID={530B85E0-1B60-11E1-8001-444553540000}

1=G-Throttles

1.GUID={C83F4640-C678-11E0-8006-444553540000}

2=Saitek Pro Flight Rudder Pedals

2.GUID={1D234F90-C7E0-11E0-8001-444553540000}

3=BU0836X Interface

3.GUID={1D2B65E0-C7E0-11E0-8011-444553540000}

4=BU0836X Interface

4.GUID={1D2B8CF0-C7E0-11E0-8012-444553540000}

5=Plasma-MM2

5.GUID={1D2B17C0-C7E0-11E0-800F-444553540000}

[buttons]

ButtonRepeat=20,10

3=R1,1,C65602,0

4=U1,1,C65697,0

5=P1,5,C65853,0

6=U1,5,C65786,0

11=P4,12,CM3:1,0

[Auto.PMDG 737]

1=Lua NGX_AUTO

[Auto.Boeing 737]

1=Lua NGX_AUTO

[LuaFiles]

1=NGX_AUTO

2=ipcReady

3=linda

[MacroFiles]

1=iFly737

2=leveld767

3=0_PMDG_ATTN

[LuaFiles]

1=ipcReady

2=linda

3=NGX_AUTO

[AutoSave]

Next=1

Interval=60

Files=10

SaveOnGround=No

AutoSaveEnabled=No

[GPSout]

GPSoutEnabled=No

[GPSout2]

GPSoutEnabled=No

[WideServer]

WideFSenabled=Yes

[sounds]

Path=D:\FSX\Sound\

Device1=Primary Sound Driver

Device2=Speakers (Sound Blaster X-Fi Xtreme Audio)

Device3=Speakers (10- USB audio CODEC)

Device4=Realtek Digital Output(Optical) (Realtek High Definition Audio)

Device5=Digital Audio (S/PDIF) (Sound Blaster X-Fi Xtreme Audio)

Device6=Realtek Digital Output (Realtek High Definition Audio)

[Programs]

RunIf1=D:\FSX\Modules\linda.exe

[Window.LUA display]

Docked=7398, 3310, 3524, 1298

Undocked=535, 252, 230, 140

Derek

[Pete Dowson]

Installed version 4.81 and problem remains, Did a test creating macros and soon as I hit O.K. to close out the Flt Sim stops. Only when in the PMDG737NGX

Do you mean "mouse macro" creation mode? Does it only crash when doing tha? Earlier you said "whenever I attempt to allocate Button and Switches" I understood you tyo mean simply assigning buttons in the buttons tab. Is that not really so? It makes a lot of difference. The mouse macro creation facilty is a lot more complicated and might be influenced by the aircraft loaded. I'd need to check, but I could do with clarification first, please.

Here is my .ini file,

Okay, checking that now ...

... Nothing wrong with the INI file. But I can't check with your "linda" or "NGX_AUTO" files. I see you have the latter loaded automatically when you load the PMDG737. Maybe it is something in that

I used your INI and created a few mouse macros whilst in the PMDG 737NGX SP1c virual cockpit, and had no problems, and they all worked fine, so there's something different in what you are doing. Many others also seem to be using it successfully.

So, I need to know every little detail of what you do to make the crash occur. I also need more details of the actual crash -- the data from the Windows error log in particular, please.

Regards

Pete

[Heron 1B]

Pete,

Confirm the problem exists with buttons and switches also mouse macros creation. But can now narrow it down, tried simply opening and closing FSUIPC whilst in the PMDG737MGX. I went to Addons/Modules/FSUIPC and the usual front page appears, did not go any further just selected O.K. to come out of FSUIPC with the same crash. Screen go white with small window stating " Microsoft Flight Simulator has stopped working" there is option for windows to search for cause and report back but nothing appears unless it is recorded somewhere?

When you say Windows error log, where does that reside exactly, can you advise path?

Strange how the problem exists only with PMDG737NGX.

Derek

[Heron 1B]

Pete,

Narrowed it down, no longer have the crash when coming out of FSUIPC when in PMDG737NGX,

I completely removed and saved the orig Modules folder then created a fresh clean Modules and installed fresh FSUIPC4 ver 4.81 with no other programs in there.

Must be an issue with one of the addon progies that appear in the original Modules folder, here is that list:

FSUIPC4 with all the files.

linda

linda_config

0_PMDG_ATTN.MCRO

ifly737.MCRO

ipcReady.lua

levelD767.MCRO

Linda.exe

linda.lua

linda.log

LVLD.dll_for _simconnect_1.zip

NGX_AUTO.lua

sb3guagebridge.dll

Derek

[Pete Dowson]

I completely removed and saved the orig Modules folder then created a fresh clean Modules and installed fresh FSUIPC4 ver 4.81 with no other programs in there.

Must be an issue with one of the addon progies that appear in the original Modules folder, here is that list:

Well, of those the ones which would presumably be involved are:

linda

linda_config

ipcReady.lua

levelD767.MCRO

Linda.exe

linda.lua

NGX_AUTO.lua

sb3guagebridge.dll

But that isn't the point. FSUIPC should never crash FS, so I need to find out why and fix it.

So, please:

1. Change to version 4.811 (from Download Links subforum), so you are on the same version as me,

2. Reproduce the crash.

3. find the error details in the Windows error log. On this you asked:

When you say Windows error log, where does that reside exactly, can you advise path?

Go to "My computer" or "Computer", right-click, select Manage -- or go to the Start menu and enter "Manage" and press Enter.

Select "Event Viewer" then "Windows Logs" then "Applications". Scroll down the list till you find an Error (red icon with exclamation mark), see if it was for FSX. Find the FSX one, Double-clcik on it, select "Copy" then paste the details in a message here.

Regards

Pete

[Heron 1B]

Log Name: Application

Source: Application Error

Date: 17/03/2012 11:13:09 PM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: Derek-PC

Description:

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: dinput.DLL, version: 6.1.7600.16385, time stamp: 0x4a5bd9c0

Exception code: 0xc0000005

Fault offset: 0x00016569

Faulting process id: 0x5b8

Faulting application start time: 0x01cd04501ad4c206

Faulting application path: D:\FSX\fsx.exe

Faulting module path: C:\Windows\system32\dinput.DLL

Report Id: b4171fd6-7043-11e1-ac1f-5404a63f905c

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Application Error" />

<EventID Qualifiers="0">1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2012-03-17T15:13:09.000000000Z" />

<EventRecordID>35356</EventRecordID>

<Channel>Application</Channel>

<Computer>Derek-PC</Computer>

<Security />

</System>

<EventData>

<Data>fsx.exe</Data>

<Data>10.0.61472.0</Data>

<Data>475e17d3</Data>

<Data>dinput.DLL</Data>

<Data>6.1.7600.16385</Data>

<Data>4a5bd9c0</Data>

<Data>c0000005</Data>

<Data>00016569</Data>

<Data>5b8</Data>

<Data>01cd04501ad4c206</Data>

<Data>D:\FSX\fsx.exe</Data>

<Data>C:\Windows\system32\dinput.DLL</Data>

<Data>b4171fd6-7043-11e1-ac1f-5404a63f905c</Data>

</EventData>

</Event>

Here it is ...............Derek

[Pete Dowson]

Faulting module name: dinput.DLL, version: 6.1.7600.16385, time stamp: 0x4a5bd9c0

Exception code: 0xc0000005

Fault offset: 0x00016569

It's a crash in DirectInput. Some sort of a problem with one of the devices you have attached, or its driver. Maybe something addressed by your LINDA configuration, or your levelD767 macro file? Perhaps you can do a process of elimination, unplugging one device at a time? I see you have 6 of them:

0=BU0836X Interface

1=G-Throttles

2=Saitek Pro Flight Rudder Pedals

3=BU0836X Interface

4=BU0836X Interface

5=Plasma-MM2

If you cannot locate it I'll see if I can add some more diagnostic logging into FSUIPC to narrow it down somewhat.

[LATER]

Meanwhile, I've realised you can probably get a little more datas by adding this to the [General] section of the FSUIPC4.INI file:

Debug=Please

LogExtras=x200000

Then reproduce the error. Show me the log.

Regards

Pete

[Heron 1B]

Here is the log following Debug=Please and LogExtras=x200000..................Derek

Log Name: Application

Source: Application Error

Date: 18/03/2012 9:47:52 PM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: Derek-PC

Description:

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: dinput.DLL, version: 6.1.7600.16385, time stamp: 0x4a5bd9c0

Exception code: 0xc0000005

Fault offset: 0x00016569

Faulting process id: 0xde4

Faulting application start time: 0x01cd050cfbb0c1d1

Faulting application path: D:\FSX\fsx.exe

Faulting module path: C:\Windows\system32\dinput.DLL

Report Id: f475f27c-7100-11e1-8216-5404a63f905c

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Application Error" />

<EventID Qualifiers="0">1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2012-03-18T13:47:52.000000000Z" />

<EventRecordID>35550</EventRecordID>

<Channel>Application</Channel>

<Computer>Derek-PC</Computer>

<Security />

</System>

<EventData>

<Data>fsx.exe</Data>

<Data>10.0.61472.0</Data>

<Data>475e17d3</Data>

<Data>dinput.DLL</Data>

<Data>6.1.7600.16385</Data>

<Data>4a5bd9c0</Data>

<Data>c0000005</Data>

<Data>00016569</Data>

<Data>de4</Data>

<Data>01cd050cfbb0c1d1</Data>

<Data>D:\FSX\fsx.exe</Data>

<Data>C:\Windows\system32\dinput.DLL</Data>

<Data>f475f27c-7100-11e1-8216-5404a63f905c</Data>

</EventData>

</Event>

[Pete Dowson]

Here is the log following Debug=Please and LogExtras=x200000

No, no. The above lines create some extra logging in the FSUIPC log, not the Windows log -- it was the FSUIPC log file I needed to see!

[LATER]

I've now made a special version of FSUIPC which might, hopefully, trap the error and log more useful information. For the time being, without that Log I needed, I've assumed it is occurring durng one of the specific initialisation DirectInput calls. If it does, this version should catch it:

FSUIPC4811a

Please try it and let me know. Remember, it is the FSUIPC4 log I need to see.

Regards

Pete

[Heron 1B]

Pete,

Here is the FSUIPC4.log

********* FSUIPC4, Version 4.811a by Pete Dowson *********

User Name="Derek Froud"

User Addr="dfroud1@internode.on.net"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

Running inside FSX on Windows 7

Module base=61000000

16 System time = 19/03/2012 07:27:42

16 FLT path = "C:\Users\Derek\Documents\Flight Simulator X Files\"

47 Trying to connect to SimConnect Acc/SP2 Oct07 ...

47 FS path = "D:\FSX\"

265 #### Initialising Dlrectinput Axis Scanning ...

265 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_05B5\Calibration\0"

265 Found correct joystick Id 0

265 ... and a "GUID" value

265 ... okay, Acquired device!

265 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_27D3\Calibration\0"

265 Found correct joystick Id 1

265 ... and a "GUID" value

265 ... okay, Acquired device!

265 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0"

265 Found correct joystick Id 2

265 ... and a "GUID" value

281 ... okay, Acquired device!

281 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\0"

281 Found correct joystick Id 3

281 ... and a "GUID" value

281 ... okay, Acquired device!

281 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\0"

281 "Joystick Id" value = 3, not wanted this time

281 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\1"

281 Found correct joystick Id 4

281 ... and a "GUID" value

281 ... okay, Acquired device!

281 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_12DA&PID_0920\Calibration\0"

281 Found correct joystick Id 5

281 ... and a "GUID" value

281 ... okay, Acquired device!

281 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\0"

281 "Joystick Id" value = 3, not wanted this time

281 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\1"

281 "Joystick Id" value = 4, not wanted this time

281 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\2"

281 Found correct joystick Id 6

281 ... and a "GUID" value

281 ... okay, Acquired device!

281 joyGetDevCaps for device 7 returned error 165 [000000A5]

281 joyGetDevCaps for device 8 returned error 165 [000000A5]

281 joyGetDevCaps for device 9 returned error 165 [000000A5]

281 joyGetDevCaps for device 10 returned error 165 [000000A5]

281 joyGetDevCaps for device 11 returned error 165 [000000A5]

281 joyGetDevCaps for device 12 returned error 165 [000000A5]

281 joyGetDevCaps for device 13 returned error 165 [000000A5]

281 joyGetDevCaps for device 14 returned error 165 [000000A5]

281 joyGetDevCaps for device 15 returned error 165 [000000A5]

281 #### Completed Dlrectinput Axis Scanning

468 Run: "D:\FSX\Modules\linda.exe"

562 LogOptions=00000000 02000011

562 Wind smoothing fix is fully installed

562 G3D.DLL fix attempt installed ok

562 SimConnect_Open succeeded: waiting to check version okay

562 Trying to use SimConnect Acc/SP2 Oct07

1981 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N

2730 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

2730 Initialising SimConnect data requests now

2730 FSUIPC Menu entry added

2761 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y

2761 C:\Users\Derek\Documents\Flight Simulator X Files\C172 start up.FLT

2761 D:\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR

61979 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N

62213 System time = 19/03/2012 07:28:45, Simulator time = 07:27:45 (00:27Z)

62401 Aircraft="Cessna Superhawk 172sP VH-RWT"

62993 Starting everything now ...

63009 Using "C:\Program Files (x86)\GoFlight\GFDEV.DLL", version 2.0.0.1

63009 GoFlight GFT8 detected: 1 device

63009 GoFlight GF166 detected: 4 devices

63009 GoFlight GFRP48 detected: 1 device

63009 GoFlight GFMCPPRO detected: 1 device

63009 GoFlight GFEFIS detected: 2 devices

63009 LUA: beginning "D:\FSX\Modules\ipcReady.lua"

63009 LUA: ended "D:\FSX\Modules\ipcReady.lua"

63009 LUA:

63025 LUA: [iNIT]LINDA:: Loading...

63040 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

63103 LUA: LINDA:: Aircraft: Cessna Superhawk 172sP VH-RWT

63103 LUA: LINDA:: Aircraft module detected: FSX Default

63134 LUA: LINDA:: AivlaSoft library loaded...

63134 LUA: LINDA:: FSX standard library loaded...

63149 LUA: LINDA:: IAO library loaded...

63149 LUA: LINDA:: RealityXP library loaded...

63149 LUA: LINDA:: A2A MAP library loaded...

63243 LUA: LINDA:: ---> ERROR:: Could not open MCP Combo port!

63305 LUA: LINDA:: Module: FSX Default Started...

63305 LUA: LINDA:: Ready to go, Captain!

63305 LUA: LINDA::

63368 LUA: LINDA:: LVars watching list cleared...

63446 LUA: LINDA:: Offsets watching list cleared!

64210 Advanced Weather Interface Enabled

82618 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y

82618 Sim stopped: average frame rate for last 21 secs = 29.5 fps

82618 #### Initialising Dlrectinput Axis Scanning ...

82618 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_05B5\Calibration\0"

82618 Found correct joystick Id 0

82618 ... and a "GUID" value

82618 ... okay, Acquired device!

82618 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_27D3\Calibration\0"

82618 Found correct joystick Id 1

82618 ... and a "GUID" value

82618 ... okay, Acquired device!

82618 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0"

82618 Found correct joystick Id 2

82618 ... and a "GUID" value

82618 ... okay, Acquired device!

82618 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\0"

82618 Found correct joystick Id 3

82618 ... and a "GUID" value

82634 ... okay, Acquired device!

82634 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\0"

82634 "Joystick Id" value = 3, not wanted this time

82634 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\1"

82634 Found correct joystick Id 4

82634 ... and a "GUID" value

82634 ... okay, Acquired device!

82634 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_12DA&PID_0920\Calibration\0"

82634 Found correct joystick Id 5

82634 ... and a "GUID" value

82634 ... okay, Acquired device!

82634 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\0"

82634 "Joystick Id" value = 3, not wanted this time

82634 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\1"

82634 "Joystick Id" value = 4, not wanted this time

82634 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\2"

82634 Found correct joystick Id 6

82634 ... and a "GUID" value

82634 ... okay, Acquired device!

82634 joyGetDevCaps for device 7 returned error 165 [000000A5]

82634 joyGetDevCaps for device 8 returned error 165 [000000A5]

82634 joyGetDevCaps for device 9 returned error 165 [000000A5]

82634 joyGetDevCaps for device 10 returned error 165 [000000A5]

82634 joyGetDevCaps for device 11 returned error 165 [000000A5]

82634 joyGetDevCaps for device 12 returned error 165 [000000A5]

82634 joyGetDevCaps for device 13 returned error 165 [000000A5]

82634 joyGetDevCaps for device 14 returned error 165 [000000A5]

82634 joyGetDevCaps for device 15 returned error 165 [000000A5]

82634 #### Completed Dlrectinput Axis Scanning

92852 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

97360 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y

106096 D:\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.AIR

106642 Aircraft="Boeing 737-838NGX Qantas Airways (New Livery) Winglets"

106658 LUA: LINDA:: Aircraft: Boeing 737-838NGX Qantas Airways (N

106658 LUA: LINDA:: Aircraft module detected: PMDG 737NGX

107173 LUA: LINDA:: AivlaSoft library loaded...

107188 LUA: LINDA:: FSX standard library loaded...

107188 LUA: LINDA:: IAO library loaded...

107204 LUA: LINDA:: RealityXP library loaded...

107204 LUA: LINDA:: A2A MAP library loaded...

107313 LUA: LINDA:: ---> ERROR:: Could not open MCP Combo port!

107547 LUA: LINDA:: Loading PMDG 737NGX joysticks config...

107563 LUA: LINDA:: Module: PMDG 737NGX Started...

107563 LUA: LINDA:: Ready to go, Captain!

107563 LUA: LINDA::

108202 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

144769 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y

144769 Sim stopped: average frame rate for last 37 secs = 20.0 fps

[Pete Dowson]

Here is the FSUIPC4.log

Interesting that you got LINDA logging this time, too.

The code I put in to catch the crash isn't being triggered, so the crash is evidently NOT occurring when FSUIPC itself is rescanning and initialising the DirectInput devices. I'll have to pt more traps in. If those don't work, I can only think it is somehow related to what LINDA is doing. That's running in its own thread, separately. I've no idea how or why that would be crashing DINPUT.DLL.

Did you try with each of your 5 devices unplugged, one at a time, to see if it was definitely associated with just one? If so, what was the result? If not, could you try it please?

Please try with this version with more traps in:

FSUIPC4811b

After that I think we need some assistance in narrowing down what exactly LINDA is doing at the time of the crash. Maybe there's more logging that can be enabled, or that they can add for us. I'm afraid i now nothing about LINDA at all. Can you ask the author(s) for help with this? Don't they have their own website?

Pete

[Heron 1B]

Pete,

About to replace the .dll with 4811b,

With 4811a I noted the crash now occurs if I attempt to open FSUIPC.

Will try removing devices one by one today.

Derek

[Heron 1B]

Pete,

Can confirm unable to open FSUIPC without crash with this .dll..........Derek

********* FSUIPC4, Version 4.811b by Pete Dowson *********

User Name="Derek Froud"

User Addr="dfroud1@internode.on.net"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

Running inside FSX on Windows 7

Module base=61000000

32 System time = 19/03/2012 12:55:33

32 FLT path = "C:\Users\Derek\Documents\Flight Simulator X Files\"

63 Trying to connect to SimConnect Acc/SP2 Oct07 ...

63 FS path = "D:\FSX\"

297 #### Initialising Dlrectinput Axis Scanning ...

297 joyGetDevCaps for device 0 returned error 165 [000000A5]

297 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_27D3\Calibration\0"

297 Found correct joystick Id 1

297 ... and a "GUID" value

312 ... okay, Acquired device!

312 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0"

312 Found correct joystick Id 2

312 ... and a "GUID" value

312 ... okay, Acquired device!

312 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\0"

312 Found correct joystick Id 3

312 ... and a "GUID" value

312 ... okay, Acquired device!

312 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\0"

312 "Joystick Id" value = 3, not wanted this time

312 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\1"

312 Found correct joystick Id 4

312 ... and a "GUID" value

312 ... okay, Acquired device!

312 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_12DA&PID_0920\Calibration\0"

312 Found correct joystick Id 5

312 ... and a "GUID" value

312 ... okay, Acquired device!

312 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\0"

312 "Joystick Id" value = 3, not wanted this time

312 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\1"

312 "Joystick Id" value = 4, not wanted this time

312 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\2"

312 Found correct joystick Id 6

312 ... and a "GUID" value

312 ... okay, Acquired device!

312 joyGetDevCaps for device 7 returned error 165 [000000A5]

312 joyGetDevCaps for device 8 returned error 165 [000000A5]

312 joyGetDevCaps for device 9 returned error 165 [000000A5]

312 joyGetDevCaps for device 10 returned error 165 [000000A5]

312 joyGetDevCaps for device 11 returned error 165 [000000A5]

312 joyGetDevCaps for device 12 returned error 165 [000000A5]

312 joyGetDevCaps for device 13 returned error 165 [000000A5]

312 joyGetDevCaps for device 14 returned error 165 [000000A5]

312 joyGetDevCaps for device 15 returned error 165 [000000A5]

312 #### Completed Dlrectinput Axis Scanning

359 Run: "D:\FSX\Modules\linda.exe"

390 LogOptions=00000000 02000011

390 Wind smoothing fix is fully installed

390 G3D.DLL fix attempt installed ok

390 SimConnect_Open succeeded: waiting to check version okay

390 Trying to use SimConnect Acc/SP2 Oct07

1794 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N

2340 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

2340 Initialising SimConnect data requests now

2340 FSUIPC Menu entry added

2372 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y

2372 C:\Users\Derek\Documents\Flight Simulator X Files\C172 start up.FLT

2372 D:\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR

63212 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N

63727 System time = 19/03/2012 12:56:36, Simulator time = 12:55:36 (05:55Z)

63789 Aircraft="Cessna Superhawk 172sP VH-RWT"

64242 Starting everything now ...

64257 Using "C:\Program Files (x86)\GoFlight\GFDEV.DLL", version 2.0.0.1

64257 GoFlight GFT8 detected: 1 device

64257 GoFlight GF166 detected: 4 devices

64257 GoFlight GFRP48 detected: 1 device

64257 GoFlight GFMCPPRO detected: 1 device

64257 GoFlight GFEFIS detected: 2 devices

64257 LUA: beginning "D:\FSX\Modules\ipcReady.lua"

64257 LUA: ended "D:\FSX\Modules\ipcReady.lua"

64257 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

64273 LUA:

64273 LUA: [iNIT]LINDA:: Loading...

64351 LUA: LINDA:: Aircraft: Cessna Superhawk 172sP VH-RWT

64366 LUA: LINDA:: Aircraft module detected: FSX Default

64382 LUA: LINDA:: AivlaSoft library loaded...

64382 LUA: LINDA:: FSX standard library loaded...

64382 LUA: LINDA:: IAO library loaded...

64398 LUA: LINDA:: RealityXP library loaded...

64398 LUA: LINDA:: A2A MAP library loaded...

64491 LUA: LINDA:: ---> ERROR:: Could not open MCP Combo port!

64538 LUA: LINDA:: Module: FSX Default Started...

64538 LUA: LINDA:: Ready to go, Captain!

64538 LUA: LINDA::

64600 LUA: LINDA:: LVars watching list cleared...

64663 LUA: LINDA:: Offsets watching list cleared!

65412 Advanced Weather Interface Enabled

75754 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y

82338 D:\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.AIR

82743 Aircraft="Boeing 737-838NGX Qantas Airways (New Livery) Winglets"

82743 LUA: LINDA:: Aircraft: Boeing 737-838NGX Qantas Airways (N

82759 LUA: LINDA:: Aircraft module detected: PMDG 737NGX

83258 LUA: LINDA:: AivlaSoft library loaded...

83258 LUA: LINDA:: FSX standard library loaded...

83274 LUA: LINDA:: IAO library loaded...

83274 LUA: LINDA:: RealityXP library loaded...

83274 LUA: LINDA:: A2A MAP library loaded...

83367 LUA: LINDA:: ---> ERROR:: Could not open MCP Combo port!

83601 LUA: LINDA:: Loading PMDG 737NGX joysticks config...

83617 LUA: LINDA:: Module: PMDG 737NGX Started...

83617 LUA: LINDA:: Ready to go, Captain!

83617 LUA: LINDA::

84288 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

126283 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y

126283 Sim stopped: average frame rate for last 42 secs = 20.0 fps

126299 ***ERROR C0000005 at 7300A1C3 AxesDeInit ID, Step= [0x00000001, 0x00000002])

126299 *** Access violation trying to write address 5456F646

126299 *** EAX 09530D70 EBX 09530D9C ECX 5456F646 EDX 00000002 EDI 00080590 ESI 31342D30

126299 *** EIP 7300A1C3 EBP 000CDB64 ESP 000CDB5C

126299 #### Initialising Dlrectinput Axis Scanning ...

126314 joyGetDevCaps for device 0 returned error 165 [000000A5]

126314 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_27D3\Calibration\0"

126314 Found correct joystick Id 1

126314 ... and a "GUID" value

126314 ***ERROR C0000005 at 7300A02C AxesInit ID, Step= [0x00000001, 0x00000003])

126314 *** Access violation trying to write address 5456F652

126314 *** EAX 5456F646 EBX 00000000 ECX 005E0E68 EDX 00538004 EDI 00000004 ESI 00000006

126314 *** EIP 7300A02C EBP 000CDF28 ESP 000CDF28

126314 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0"

126314 Found correct joystick Id 2

126314 ... and a "GUID" value

126314 Acquire failed, return = 00000001

126314 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\0"

126314 Found correct joystick Id 3

126314 ... and a "GUID" value

[Heron 1B]

Pete,

I have tested with devices unplugged one at a time, still had crash on attempting to open FSUIPC each time. Then I unplugged just the three BU0836X boards, these have all LINDA buttons and switches for my overhead panel which function perfectly.

The result of unplugging the three BU boards together is I can now open and use FSUIPC as normal.

So it is LINDA it would seem.

Here is the latest log with all three BU boards unplugged,,,,,,,,,,,,,,,,,,,Derek

********* FSUIPC4, Version 4.811b by Pete Dowson *********

User Name="Derek Froud"

User Addr="dfroud1@internode.on.net"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

Running inside FSX on Windows 7

Module base=61000000

812 System time = 19/03/2012 13:38:15

812 FLT path = "C:\Users\Derek\Documents\Flight Simulator X Files\"

843 Trying to connect to SimConnect Acc/SP2 Oct07 ...

843 FS path = "D:\FSX\"

1077 #### Initialising Dlrectinput Axis Scanning ...

1092 joyGetDevCaps for device 0 returned error 165 [000000A5]

1092 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_27D3\Calibration\0"

1092 Found correct joystick Id 1

1092 ... and a "GUID" value

1092 ... okay, Acquired device!

1092 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0"

1092 Found correct joystick Id 2

1092 ... and a "GUID" value

1092 ... okay, Acquired device!

1092 joyGetDevCaps for device 3 returned error 165 [000000A5]

1108 joyGetDevCaps for device 4 returned error 165 [000000A5]

1108 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_12DA&PID_0920\Calibration\0"

1108 Found correct joystick Id 5

1108 ... and a "GUID" value

1108 ... okay, Acquired device!

1124 joyGetDevCaps for device 6 returned error 165 [000000A5]

1124 joyGetDevCaps for device 7 returned error 165 [000000A5]

1124 joyGetDevCaps for device 8 returned error 165 [000000A5]

1124 joyGetDevCaps for device 9 returned error 165 [000000A5]

1124 joyGetDevCaps for device 10 returned error 165 [000000A5]

1124 joyGetDevCaps for device 11 returned error 165 [000000A5]

1124 joyGetDevCaps for device 12 returned error 165 [000000A5]

1124 joyGetDevCaps for device 13 returned error 165 [000000A5]

1124 joyGetDevCaps for device 14 returned error 165 [000000A5]

1124 joyGetDevCaps for device 15 returned error 165 [000000A5]

1124 #### Completed Dlrectinput Axis Scanning

1170 Run: "D:\FSX\Modules\linda.exe"

1202 LogOptions=00000000 02000011

1202 Wind smoothing fix is fully installed

1202 G3D.DLL fix attempt installed ok

1202 SimConnect_Open succeeded: waiting to check version okay

1202 Trying to use SimConnect Acc/SP2 Oct07

2606 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N

3120 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

3120 Initialising SimConnect data requests now

3120 FSUIPC Menu entry added

3167 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y

3167 C:\Users\Derek\Documents\Flight Simulator X Files\C172 start up.FLT

3167 D:\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR

56613 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N

57159 System time = 19/03/2012 13:39:11, Simulator time = 13:38:18 (06:38Z)

57206 Aircraft="Cessna Superhawk 172sP VH-RWT"

57643 Starting everything now ...

57643 Using "C:\Program Files (x86)\GoFlight\GFDEV.DLL", version 2.0.0.1

57643 GoFlight GFT8 detected: 1 device

57643 GoFlight GF166 detected: 4 devices

57643 GoFlight GFMCPPRO detected: 1 device

57658 LUA: beginning "D:\FSX\Modules\ipcReady.lua"

57658 LUA: ended "D:\FSX\Modules\ipcReady.lua"

57658 LUA:

57658 LUA: [iNIT]LINDA:: Loading...

57690 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

57752 LUA: LINDA:: Aircraft: Cessna Superhawk 172sP VH-RWT

57752 LUA: LINDA:: Aircraft module detected: FSX Default

57768 LUA: LINDA:: AivlaSoft library loaded...

57783 LUA: LINDA:: FSX standard library loaded...

57783 LUA: LINDA:: IAO library loaded...

57783 LUA: LINDA:: RealityXP library loaded...

57799 LUA: LINDA:: A2A MAP library loaded...

57877 LUA: LINDA:: ---> ERROR:: Could not open MCP Combo port!

57924 LUA: LINDA:: Module: FSX Default Started...

57924 LUA: LINDA:: Ready to go, Captain!

57939 LUA: LINDA::

57986 LUA: LINDA:: LVars watching list cleared...

58064 LUA: LINDA:: Offsets watching list cleared!

58844 Advanced Weather Interface Enabled

71574 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y

76925 D:\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.AIR

77330 Aircraft="Boeing 737-838NGX Qantas Airways (New Livery) Winglets"

77330 LUA: LINDA:: Aircraft: Boeing 737-838NGX Qantas Airways (N

77330 LUA: LINDA:: Aircraft module detected: PMDG 737NGX

77845 LUA: LINDA:: AivlaSoft library loaded...

77861 LUA: LINDA:: FSX standard library loaded...

77861 LUA: LINDA:: IAO library loaded...

77861 LUA: LINDA:: RealityXP library loaded...

77876 LUA: LINDA:: A2A MAP library loaded...

77923 LUA: LINDA:: ---> ERROR:: Could not open MCP Combo port!

78157 LUA: LINDA:: Loading PMDG 737NGX joysticks config...

78173 LUA: LINDA:: Module: PMDG 737NGX Started...

78173 LUA: LINDA:: Ready to go, Captain!

78173 LUA: LINDA::

79093 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

110106 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y

110106 Sim stopped: average frame rate for last 31 secs = 19.3 fps

110137 #### Initialising Dlrectinput Axis Scanning ...

110153 joyGetDevCaps for device 0 returned error 165 [000000A5]

110153 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_27D3\Calibration\0"

110153 Found correct joystick Id 1

110153 ... and a "GUID" value

110153 ... okay, Acquired device!

110153 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0"

110153 Found correct joystick Id 2

110153 ... and a "GUID" value

110153 ... okay, Acquired device!

110168 joyGetDevCaps for device 3 returned error 165 [000000A5]

110168 joyGetDevCaps for device 4 returned error 165 [000000A5]

110168 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_12DA&PID_0920\Calibration\0"

110168 Found correct joystick Id 5

110168 ... and a "GUID" value

110168 ... okay, Acquired device!

110184 joyGetDevCaps for device 6 returned error 165 [000000A5]

110184 joyGetDevCaps for device 7 returned error 165 [000000A5]

110184 joyGetDevCaps for device 8 returned error 165 [000000A5]

110184 joyGetDevCaps for device 9 returned error 165 [000000A5]

110184 joyGetDevCaps for device 10 returned error 165 [000000A5]

110184 joyGetDevCaps for device 11 returned error 165 [000000A5]

110184 joyGetDevCaps for device 12 returned error 165 [000000A5]

110184 joyGetDevCaps for device 13 returned error 165 [000000A5]

110184 joyGetDevCaps for device 14 returned error 165 [000000A5]

110184 joyGetDevCaps for device 15 returned error 165 [000000A5]

110184 #### Completed Dlrectinput Axis Scanning

122118 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

129668 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y

129700 #### Initialising Dlrectinput Axis Scanning ...

129715 joyGetDevCaps for device 0 returned error 165 [000000A5]

129715 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_27D3\Calibration\0"

129715 Found correct joystick Id 1

129715 ... and a "GUID" value

129715 ... okay, Acquired device!

129715 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0"

129715 Found correct joystick Id 2

129715 ... and a "GUID" value

129715 ... okay, Acquired device!

129731 joyGetDevCaps for device 3 returned error 165 [000000A5]

129731 joyGetDevCaps for device 4 returned error 165 [000000A5]

129731 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_12DA&PID_0920\Calibration\0"

129731 Found correct joystick Id 5

129731 ... and a "GUID" value

129731 ... okay, Acquired device!

129746 joyGetDevCaps for device 6 returned error 165 [000000A5]

129746 joyGetDevCaps for device 7 returned error 165 [000000A5]

129746 joyGetDevCaps for device 8 returned error 165 [000000A5]

129746 joyGetDevCaps for device 9 returned error 165 [000000A5]

129746 joyGetDevCaps for device 10 returned error 165 [000000A5]

129746 joyGetDevCaps for device 11 returned error 165 [000000A5]

129746 joyGetDevCaps for device 12 returned error 165 [000000A5]

129746 joyGetDevCaps for device 13 returned error 165 [000000A5]

129746 joyGetDevCaps for device 14 returned error 165 [000000A5]

129746 joyGetDevCaps for device 15 returned error 165 [000000A5]

129746 #### Completed Dlrectinput Axis Scanning

153209 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

168965 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y

168996 #### Initialising Dlrectinput Axis Scanning ...

169012 joyGetDevCaps for device 0 returned error 165 [000000A5]

169012 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_27D3\Calibration\0"

169012 Found correct joystick Id 1

169012 ... and a "GUID" value

169012 ... okay, Acquired device!

169012 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0"

169012 Found correct joystick Id 2

169012 ... and a "GUID" value

169012 ... okay, Acquired device!

169012 joyGetDevCaps for device 3 returned error 165 [000000A5]

169028 joyGetDevCaps for device 4 returned error 165 [000000A5]

169028 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_12DA&PID_0920\Calibration\0"

169028 Found correct joystick Id 5

169028 ... and a "GUID" value

169028 ... okay, Acquired device!

169028 joyGetDevCaps for device 6 returned error 165 [000000A5]

169028 joyGetDevCaps for device 7 returned error 165 [000000A5]

169028 joyGetDevCaps for device 8 returned error 165 [000000A5]

169028 joyGetDevCaps for device 9 returned error 165 [000000A5]

169028 joyGetDevCaps for device 10 returned error 165 [000000A5]

169028 joyGetDevCaps for device 11 returned error 165 [000000A5]

169028 joyGetDevCaps for device 12 returned error 165 [000000A5]

169028 joyGetDevCaps for device 13 returned error 165 [000000A5]

169028 joyGetDevCaps for device 14 returned error 165 [000000A5]

169028 joyGetDevCaps for device 15 returned error 165 [000000A5]

169028 #### Completed Dlrectinput Axis Scanning

171383 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

173520 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y

[Pete Dowson]

Can confirm unable to open FSUIPC without crash with this .dll.

Ah, but it has trapped at least two crashes, which should help:

126299 ***ERROR C0000005 at 7300A1C3 AxesDeInit ID, Step= [0x00000001, 0x00000002])

126299 *** Access violation trying to write address 5456F646

126299 *** EAX 09530D70 EBX 09530D9C ECX 5456F646 EDX 00000002 EDI 00080590 ESI 31342D30

126299 *** EIP 7300A1C3 EBP 000CDB64 ESP 000CDB5C

126299 #### Initialising Dlrectinput Axis Scanning ...

126314 joyGetDevCaps for device 0 returned error 165 [000000A5]

126314 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_27D3\Calibration\0"

126314 Found correct joystick Id 1

126314 ... and a "GUID" value

126314 ***ERROR C0000005 at 7300A02C AxesInit ID, Step= [0x00000001, 0x00000003])

126314 *** Access violation trying to write address 5456F652

126314 *** EAX 5456F646 EBX 00000000 ECX 005E0E68 EDX 00538004 EDI 00000004 ESI 00000006

126314 *** EIP 7300A02C EBP 000CDF28 ESP 000CDF28

126314 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0"

126314 Found correct joystick Id 2

126314 ... and a "GUID" value

126314 Acquire failed, return = 00000001

I'm not sure I'm logging enough data yet, though. i'll check into this now. Oddly, both of those crashes are on device 1=G-Throttles, not on a Bodnar board.

The result of unplugging the three BU boards together is I can now open and use FSUIPC as normal.

So it is LINDA it would seem.

Yes, but it shouldn't be able to cause FS to crash. I need to find out why. Is there any chance of getting the LINDA authors to help narrow it down. I could do with knowing what it did last, before each crash. The LINDA entries in the Log seem to finish before the crash. Maybe there's extra they can enable.

If LINDA is merely causing some Lua plug-ins to run, could you perhaps wait till the crash occurs, then ZIP up the Lua files from the Modules folder and send them to me at petedowson@btconnect.com ?

Regards

Pete

[Pete Dowson]

If LINDA is merely causing some Lua plug-ins to run, could you perhaps wait till the crash occurs, then ZIP up the Lua files from the Modules folder and send them to me ...

Got them. Thanks.

Wow! That's some complicated syatem the LINDA program creates! I was hoping for something i could maybe try here, but I wouldn't know where to begin, and in any case it may depend upon having the same hardware connected as you.

I have, however, made yet another test version of FSUIPC. Please download this:

FSUIPC4811c

Edit the FSUIPC4.INI file, changing the "LogExtras=" line you already have to:

LogExtras=x200040

Then reproduce the crash once again.

The log file might be quite big -- this traces the execution of the Lua plug-ins. I'm hoping to determine which call causes the problem. If it is a large file, ZIP it as send it as before please.

Have you been in touch with LINDA support at all?

Regards

Pete

[Pete Dowson]

In the email accompanying the log you sent, you said:

Something new with the latest .dll and that .ini update I can now access

FSUIPC without crash, opened Buttons and Switches also tried Axis page

and then O.K. and came out of FSUIPC without the crash.

I've looked at the log which, had the crash occurred, could have been very useful, as it is logging the path through the assorted LINDA lua files AND, more importantly, probably, the NGX_AUTO file -- both of which appear to be running simlutaneously all the time.

However, not only don't you get the original crash, but there is also no sign of the problems shown in the earlier log. i.e. the two trapped and logged crashes. Might odd, because I made no changes in that area.

I tend to suspect that the Lua tracing is slowing down the execution of the Lua files sufficiently to prevent whatever clash was occurring. To check that, could you just revert to the previous value for LogExtras? i.e.

LogExtras=x200000

just to see if it is indeed the timing, or something else has changed. Maybe, if it was, say, a corruption of something in memory, the recompilation with this extra logging has moved things sufficiently to make something else corrupt instead! Very worrying!

Regards

Pete

[Heron 1B]

Email sent with latest LogExtras value..............Sim crash resulted.........Latest FSUIPC.log in email to you

Derek

[Pete Dowson]

Email sent with latest LogExtras value..............Sim crash resulted.........Latest FSUIPC.log in email to you

Yes, so it is definitely some sort of timing-dependent conflict which is occurring. They are extremely difficult to nail -- the very method I used with the Lua tracing to determine which Lua library action is responsible evidently slows things down enough to avoid the conflict. I'm going to have to think about how i can get more information again.

I could of course simply stop (suspend) all HID and Joystick device interaction in Lua whilst FSUIPC options are active. However, this would then prevent some of the flexibility Lua programs have of interacting with menus, virtual buttons, and joystic calibration, which would be a shame.

You said that without anything in the "actions.lua" script the crash no longer occurs. I've looked at that and it seems to be full of LVar reads and PMDG NGX controls sent, -- I don't see anything in there which might interact with devices at all, only FS innards, so really it shouldn't come into it. But maybe the device interaction there is hidden in some of the calls.

I don't understand where the LINDA.EXE GUI comes into the equation. They said "Without GUI your joysticks programmed in LINDA will not work". This implies that the EXE is doing some of the HID or Joystick accessing. I need to understand that part, because that must surely be where this conflit is occurring.

If it's in the FSUIPC Lua libraries, then I really do need to narrow it down to the Lua library function which is being executed at the time of the crash. I had hoped that Lua trace would do this, but it slows things down too much. I'm afraid that if I log all calls into the library functions the same might occur. But I'll take a look.

Maybe a little more explanation about the run-time joystick role of LINDA.EXE would be useful, and perhaps some pointers to where in the mass of complex Lua code I might look to possibile clashes. They mention memory issues, but I really doubt that any problems of actual memory usage are arising -- after all the memory use with the tracing enabed would have been greater, not less.

Regards

Pete

[Pete Dowson]

I'm going to have to think about how i can get more information again.

Instead of doing that, I'm trying something else. I'm assuming that the problem is that two things are calling the DirectInput functions in Windows at the same time, or close, and that the routines being called are simply not re-entrant so get themselves in a mess and crash.

To prevent this I've put interlocks on the three routines in FSUIPC which perform such access. Please download 4.811d and try that for me:

FSUIPC4811d

Regards

Pete

[Heron 1B]

Email sent with new log...............Derek

[Pete Dowson]

Email sent with new log...............Derek

And you said:

Here is the log with the version 4.811d .dll installed.......crash

occurred on selecting FSUIPC in FSX......once again only with the PMDG

NGX not other aircraft.

That is very very disappointing. It is most certainly not a problem with simultaneous calls arriving in DINPUT.DLL from FSUIPC -- the varios parts are now linterlocked. So it is starting to all point to whatever it is that Linda.EXE program is doing. I find it's role in this completely mystifying -- like why is it necessary to have that separate process running in order to use the joysticks?

Another question if I may, when I manage to open FSUIPC (no crash

obviously) and select AXIS Assignments page I have noted the digits to

the right of Delta IN - OUT are racing around not at all steady. i.e.

-16380 in both the In and Out areas flashes past with other unreadable

sets, unable to read them for they pass by so quickly. Like you see on a

slot machine or "one armed bandit". Is that normal?

No, it most certainly is not! That sounds like part of the problem. Does it stil happen without LINDA.EXE running? If so it is faulty hardware -- bad joysticks or connections or maybe drivers. If removing LINDA.EXE from the equation stops that then the question in as above only more so -- what on Earth is that process doing?

Does it happen on all axes? (Use the "ignore" option to work through them).

Regards

Pete

[Artem Crum]

Pete,

- LINDA GUI (linda.exe) - is the only part of the system which is dealing with HID-devices directly.

- Lua scripts in LINDA are only using COM-port interactions.

- actions.lua script is just a collection of Lua functions which are called only when some button is pressed. There is also a little part of it which is executed by timer, but it's not really big to cause any problems.

So, if error is still there without linda.exe running, then this is Lua scripting problem. And the only idea I have, is some kind of memory limitation for Lua scripts in FSUIPC.