Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About neo2810

  • Rank

Profile Information

  • Gender
  • Location
    United Kingdom
  1. Thanks John, I agree. Looks like it's the offset handoff from MSFS that's the issue.
  2. I am using 0894 to detect engine 1 status for our bespoke tracker (and 92C, 9C4, A5C for the other engines). In the A320 Neo, the engine start is triggered, but when I shutdown after the flight, the offset doesn't change in FSUIPC (Checked using Interrogator)? As a result, our Arrival phase doesn't trigger? It works fine on the props (G36, C172, etc). Edit: Worked on a second test flight. Looks like the issue is with the Sim sending the offset (or not, as the case may be)...!
  3. The question which hasn't yet had a straight answer. I think what people are trying to ask, quite simply is; Pete.... Do you intend to develop a version of FSUIPC for Microsoft Flight Simulator once the SDK is available to you?
  4. I've been using FSUIPC Pro with all my Saitek gear for years without issue. I've suddenly found my rudder is slightly offset to the left on all planes. I've tried resetting the pedals, reloading the Sim, recalibrating the device, reassigning and recalibrating in FSUIPC, all to no avail. The odd thing is, when assigning the device in FSUIPC, the range is completely normal on the Assignment tab, but in Calibration, the in and out are "stuck" on 6063/5731 and even when I move through the pedals range, those inputs change through the range from -16380 > 16380 but with constant interference from the 6063/5731 figures (as if it keeps trying to return to those figures) as if they are overriding the correct inputs. Hope I've explained that clearly. I run LINDA (Multipanel) and SpadNext (all other Saitek drivers) but I've tested with both those shutdown and same issue. Anyone experience anything similar or can shed any light?
  5. I'll see if I can find a correlation, Pete. It's not LINDA, I've only recently started using it and this has been happening for a while. I thought it might be Carenado planes but I have 5, of which only 2 are causing the crash. It must be something which is unique to the B58 and the SR22 but trying to work that out will be tricky...
  6. Hi Pete, For a while now (3 separate versions), I've had an odd issue where FSUIPC will crash the sim when I confirm any control changes on just 2 of my planes. So if I make changes on PMDG planes, or the Dash 8, absolutely no issues, but if I change anything (buttons, axis) on the Carenado Baron 58 or Cirrus SR22 (just those 2 planes) when I hit the FSUIPC OK button the sim crashes. It also crashes vPilot with unhandled exception HRESULT: 0xC000014B. The changes are saved ok, so I've just left it as it is till now. From Event Viewer: Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ArgumentException at System.TimeSpan.Interval(Double, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) Faulting application name: Prepar3D.exe, version:, time stamp: 0x56df48ce Faulting module name: KERNELBASE.dll, version: 10.0.10586.162, time stamp: 0x56cd55ab Exception code: 0xc000041d Fault offset: 0x000bdad8 Faulting process ID: 0x2a30 Faulting application start time: 0x01d19d596e1cb380 Faulting application path: G:\Lockheed Martin\Prepar3D v3\Prepar3D.exe Faulting module path: C:\WINDOWS\SYSTEM32\KERNELBASE.dll Report ID: 6d7f1ac0-e3ca-4071-8e6e-65d4956685e7 Faulting package full name: Faulting package-relative application ID: Here's the FSUIPC log: ********* FSUIPC4, Version 4.949p by Pete Dowson ********* Prepar3D.exe version = Reading options from "G:\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 8.0 Module base=1DBA0000 User Name="***SNIP***" User Addr="***SNIP***" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 0 System time = 23/04/2016 13:13:06 0 FLT path = "C:\Users\awhal\Documents\Prepar3D v3 Files\" 0 ------ Module Version Check ------ 0 acontain.dll: 0 api.dll: 0 controls.dll: 0 fs-traffic.dll: 0 G3D.dll: 0 language.dll: 0 sim1.dll: 0 visualfx.dll: 0 weather.dll: 0 window.dll: 0 ---------------------------------- 0 Trying G:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll 0 Found it: trying to connect 0 FS path = "G:\Lockheed Martin\Prepar3D v3\" 203 ---------------------- Joystick Device Scan ----------------------- 203 Product= BU0836X Interface 203 Manufacturer= Leo Bodnar 203 Vendor=1DD2, Product=1001 (Version 1.36) 203 Serial Number= B36342 203 Product= Saitek Pro Flight Yoke 203 Manufacturer= Saitek 203 Vendor=06A3, Product=0BAC (Version 3.4) 203 Serial Number= Saitek 203 Product= Saitek Pro Flight Quadrant 219 Manufacturer= Saitek 219 Vendor=06A3, Product=0C2D (Version 2.1) 219 Serial Number= Saitek 219 Product= Button Box Interface 219 Manufacturer= Leo Bodnar 219 Vendor=1DD2, Product=1140 (Version 1.4) 219 Serial Number= B50181 219 Product= Logitech Extreme 3D 219 Manufacturer= Logitech 219 Vendor=046D, Product=C215 (Version 2.4) 219 Serial Number= Logitech 235 Product= Pro Flight Cessna Rudder Pedals 235 Manufacturer= Mad Catz 235 Vendor=06A3, Product=0765 (Version 1.9) 235 Serial Number= Example# 235 ------------------------------------------------------------------- 360 Run: "C:\Users\awhal\Desktop\projectFLYTools.exe" 422 Run: "D:\Program Files (x86)\SPAD\Spad.exe" 469 LogOptions=00000000 00000001 469 ------------------------------------------------------------------- 469 ------ Setting the hooks and direct calls into the simulator ------ 469 --- CONTROLS timer memory location obtained ok 469 --- SIM1 Frictions access gained 469 ASN active function link set 469 --- FS Controls Table located ok 469 --- Installed Mouse Macro hooks ok. 469 Wind smoothing may be by ASN, not FSUIPC, if it is running 469 Will switch smoothing action when ASN starts/stops 469 --- All links okay (except older global weather setting method) 469 ------------------------------------------------------------------- 469 SimConnect_Open succeeded: waiting to check version okay 469 Trying to use SimConnect Prepar3D 44610 Running in "Lockheed Martin® Prepar3D® v3", Version: (SimConnect: 44610 Initialising SimConnect data requests now 44610 FSUIPC Menu entry added 44625 C:\Users\awhal\Documents\Prepar3D v3 Files\Default.fxml 44625 G:\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\WoP3_Spitfire\spitIIa.air 79844 G:\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\Carenado SR22_GTSX_Turbo\sr22t.air 122860 System time = 23/04/2016 13:15:09, Simulator time = 08:09:26 (07:09Z) 123031 Aircraft="SR22T Cirrus VH-SLR" 123844 Starting everything now ... 123844 LUA.0: beginning "G:\Lockheed Martin\Prepar3D v3\Modules\ipcReady.lua" 123844 LUA.0: ended "G:\Lockheed Martin\Prepar3D v3\Modules\ipcReady.lua" 123860 LUA.1: 123875 LUA.1: [iNIT]LINDA:: Loading... 123875 Run: "C:\Users\awhal\AppData\Local\vPilot\vPilot.exe" 123891 Run: "C:\Program Files (x86)\EZCA\EZCA.exe" 123938 Ready for ASN WX radar 123938 Run: "D:\Program Files (x86)\HiFi\ASNext_P3D\ASNext.exe" 124031 LUA.1: LINDA:: Aircraft: SR22T Cirrus VH-SLR 124031 LUA.1: LINDA:: Aircraft module detected: FSX Default 124094 LUA.0: LINDA:: AivlaSoft library loaded... 124094 LUA.0: LINDA:: FSX standard library loaded... 124110 LUA.0: LINDA:: IVAO library loaded... 124110 LUA.0: LINDA:: RealityXP library loaded... 124110 LUA.0: LINDA:: Weather library loaded... 124125 LUA.0: LINDA:: A2A MAP library loaded... 124203 LUA.0: LINDA:: Loading a fallback joysticks config... 124203 LUA.0: LINDA:: Loading FSX Default joysticks config... 124219 LUA.0: LINDA:: Module: FSX Default Started... 124235 LUA.0: LINDA:: Ready to go, Captain! 124235 LUA.0: LINDA:: 124344 LUA.0: LINDA:: Offsets watching list cleared! 125172 Advanced Weather Interface Enabled Can you help shed any light?
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.