Jump to content

dpwood

Frozen-Inactivity
  • Content Count

    12
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No
  1. Not quite, the error dialog caption reads "LINDA2"
  2. 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.
  3. 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
  4. 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.
  5. 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
  6. 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.
  7. 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?
  8. The error isn't in the console. It's a dialog that appears when the application starts. Here's the full console output though: ********* FSUIPC4, Version 4.937 by Pete Dowson ********* Reading options from "E:\Games\FSX\Modules\FSUIPC4.ini" Running inside FSX on Windows 7 Module base=12660000 User Name="" User Addr="" FSUIPC4 not user registered WIDEFS7 not user registered, or expired System time = 19/11/2014 18:52:27 FLT path = "E:\Media\Docs\Flight Simulator X Files\" Trying to connect to SimConnect Acc/SP2 Oct07 ... FS path = "E:\Games\FSX\" LogOptions=00000000 00000001 SIM1 Frictions access gained Wind smoothing may be by ASN, not FSUIPC, if it is running Will switch smoothing action when ASN starts/stops G3D.DLL fix attempt installed ok SimConnect_Open succeeded: waiting to check version okay Trying to use SimConnect Acc/SP2 Oct07 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) Initialising SimConnect data requests now FSUIPC Menu entry added E:\Games\FSX\FLIGHTS\OTHER\FLTSIM.FLT E:\Games\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR --- NEW LOGGING SESSION ----------- I know FSUIPC isn't registered yet, but I get the error whether or not FSX is running. Reloading the LUA engine produced no further output.
  9. I'm getting the Invalid pointer operation when the application starts, and no joysticks are found. I haven't encountered an access violation yet though. This has always happened, I've not changed anything. I have tried unplugged every peripheral except my Logitech Unifying Receiver which I need in order to have mouse/keyboard control. I've also been through device manager and removed every device that looks like it might be considered an input or tracking device of some sort. No joy. It would be great if we could have a little more diagnostic output. If the error is LINDA is trying to access a device and failing, it would be nice to know which device it's failing with so I can go hunt & destroy. I don't know whether this helps, but I tried Linda2 and got a different error. "Device cannot be opened"
  10. Thanks Scotflieger, I'm not using the Airbus FCU, just Saitek panels which I'm trying to get working on the PMDG 777. I'll revert back to 1.13 and move my queries regarding the invalid pointer to a more appropriate thread.
  11. I was getting "Invalid pointer operation" previously so thought I'd try v2 to see if there had been any improvement. Now I get "Device cannot be opened". I have tried unplugging ALL USB devices except my Unifying Logitech receiver. Can you include something in the message, or logs to at least say what device it's failing to open?
×
×
  • Create New...