Invalid pointer operation

[dpwood 0]

Thanks for the reply. I don't think anything in the console is related to the Invalid Pointer issue. If I open LINDA without FSX running I get the error, and no joysticks are found. The console at this point is empty, The console only starts filling up when I start FSX, by which time it's already too late.

 

I have reinstalled and registered FSUIPC4, switched to the C172, the MCP device is disabled, and I still get the Invalid Pointer Operation on startup. The console looks cleaner though:

 

LUA.0:
LUA.0: [iNIT] Loading...
LUA.0:  Aircraft: Cessna Skyhawk 172SP Paint1
LUA.0:  Aircraft module detected: FSX Default
LUA.1:  AivlaSoft library loaded...
LUA.1:  FSX standard library loaded...
LUA.1:  IVAO library loaded...
LUA.1:  RealityXP library loaded...
LUA.1:  Weather library loaded...
LUA.1:  A2A MAP library loaded...
LUA.1:  Module: FSX Default Started...
LUA.1:  Ready to go, Captain!
LUA.1:
LUA.1:  Offsets watching list cleared!
LUA.1:  LVars watching list cleared...
LUA.1:  FSUIPC logging bit cleared: 2
LUA.1:  FSUIPC logging bit cleared: 10
LUA.1:  FSUIPC logging bit cleared: 6

 

 

Could the issue be related to finding HID devices?

[ScotFlieger 280]

Hi dpwood

 

That is all working fine in the trace. Where and how is this invalid pointer being reported?  It is most probable that it is the HID devices that is causing the problem. How many and what type do you have?

[dpwood 0]

Lots. I have 32 HID devices registered. Most of them with pretty generic names. Which is why I was hoping for more diagnostic output around the loading of HID devices so I could identify which device, preferably by some GUID, was at fault.

 

I have disconnected all peripherals except my Logitech Unifying Receiver. I have gone through the list and removed everything that will be removed, whilst leaving me with keyboard and mouse control. This has left me a little frustrated (I didn't always manage to keep mouse and keyboard control) but I now have a mere 31 HID devices! The device I deleted was a generic sounding Microsoft Control Device, I forget the exact name, but the good news is LINDA Loads and sees Joysticks!!

 

The error occurs immediately upon starting the application, and presents as an error dialog box. This seems like a good candidate for further diagnostic output and a little more robustness around whatever pointer operation is failing. I'd be happy to contribute to the code if it was open. Thanks very much for your help.

[ScotFlieger 280]

Hi dpwood

 

Thank you for update. Can you confirm that you had your set up working before with LINDA?

 

This looks like it is related to the core LINDA GUI application. I was likely granted access to the LINDA source to add the VRInsight Airbus FCU panel to the GUI. I have not looked at or touched the HID code as it is complicated. There has been no recent work on this area although users, like you, are adding more and more HID devices to their systems and using LINDA to manage them.  Work is currently on the beta testing of fixes for VRInsight Combo users (where LINDA started) to address compatibility issues and to standardise the versions available. It does address one HID issue which required the GUI joystick page to be open for repeat and on release functions to work.

 

I don't have the time at present to look at the HID code and without being able to reproduce the fault there is little chance of finding the cause with so little to go on.

 

Andrew

[dpwood 0]

I had never had LINDA working. This was an out-of-box issue from the first time I launched the application.

 

LINDA2 does seem to have made a big improvement in that it now says "Device cannot be opened". If only it said which device, or skipped it and logged it as unopenable.

 

I understand there's little that can be done with an issue you can't replicate. At least this thread serves as a good indicator of what the "Invalid Pointer Operation" is most likely caused by. Thanks again, Andrew, for all your help.

 

Dave

[dpwood 0]

I have an update on this. The offending device reinstalls itself on reboot, so I can now tell you it was called "Microsoft Input Configuration Device". LINDA errors unless I disable or remove this device. Disabling it fortunately seems to persist across a reboot.

[ScotFlieger 280]

Hi dpwood

 

Do you have a touch screen connected to your system?

[dpwood 0]

No, no touch screen devices.

[ScotFlieger 280]

Thanks Dave. Can you reproduce the Invalid Pointer error for me and post/send me a screen shot?

 

Andrew

[dpwood 0]

Sure, I can re-enable the device and get the error, though I fear it's less than informative. I get this immediately upon starting the application:

 

 

I can dismiss the error, but the joystick list doesn't populate. The console is also empty.

 

Regards,

Dave

[ScotFlieger 280]

Thanks Dave. I am digging into the code this weekend.  First thing I see is that you should install version 2.5. It is the current version but may not answer you problem.

 

The console won't populate until you have FSX running and then LINDA will link to your current aircraft (shown in top dropdown).

 

Andrew

[dpwood 0]

I've installed 2.5 and the error message now reads "Device cannot be opened", but otherwise the same. Disabling the device continues to fix the issue.

[ScotFlieger 280]

Hi Dave

 

Right I think I am getting closer thanks to the screen shoot. The Invalid pointer operation is an untrapped error with the code caught by the runtime system (hence the LINDA in the dialog top line).  With 2.5 does the "Device cannot be opened" error display LINDA 2.5 in the dialog top line?

[dpwood 0]

Not quite, the error dialog caption reads "LINDA2"