Pete Dowson

Yes. Use your existing WideFS7 registration details. Pete

I see from the log that it was okay for 194 seconds -- over 3 minutes. Maybe I aborted the previous test I was doing too early. I notice from your log that there are lots and lots of axis movements before it started going wrong. Rudder and Elevator. Does it need this happening to make it go wrong? Okay, will try that first on Win7. Pete

If you mean assignments to buttons and switches in FSUIPC, then, no. GoFlight support in FSUIPC5, which is a 64-bit DLL to match the 64-bit P3D4, needs a 64-bit version of GFDEV.DLL from Goflight, which is not yet available. Pete

I can't test on that, never had it. Pete

Odd that I cannot make it happen here, with both your apps nor with the plug-in from Scotfleiger. Pete

So you were using an older version earlier, before the fix, mainly in 5.101a? I judt tried to induce the offset writing problem with oyur plug-in. I'm afraid it STILL won't go wring here. I initially started with ipcWrites and Even logging enabled. I have this at the start: 342001 LUA.1: FSUIPC5_test - started... 342064 WRITElua 0C4E, 2 bytes: 54 01 T. 342126 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 340 (0x00000154) VOR1_SET 342142 LUA.1: FSUIPC5_Test :: CRS = 340 342157 WRITElua 07CC, 2 bytes: 00 00 .. 342157 LUA.1: FSUIPC5_Test :: HDG = 0 342189 WRITElua 07D4, 4 bytes: 00 00 00 00 .... 342189 LUA.1: FSUIPC5_Test :: ALT = 0 342220 WRITElua 07E2, 2 bytes: 00 00 .. 342220 LUA.1: FSUIPC5_Test :: SPD = 0 342220 *** EVENT: Cntrl= 66037 (0x000101f5), Param= 0 (0x00000000) AP_SPD_VAR_SET 342220 WRITElua 07F2, 2 bytes: 00 00 .. 342220 LUA.1: FSUIPC5_Test :: VS = 0 342251 WRITElua 0C4E, 2 bytes: 55 01 U. 342251 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 341 (0x00000155) VOR1_SET 342267 WRITElua 07CC, 2 bytes: B6 00 .. 342267 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 1 (0x00000001) HEADING_BUG_SET 342267 WRITElua 07D4, 4 bytes: 70 3D 0F 00 p=.. 342267 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 49 (0x00000031) AP_ALT_VAR_SET_ENGLISH 342298 WRITElua 07E2, 2 bytes: 01 00 .. 342298 *** EVENT: Cntrl= 66037 (0x000101f5), Param= 1 (0x00000001) AP_SPD_VAR_SET and then in case it was affecting the timing, I turned off those logging options, here, nearly 3 minutes later (172 seconds): 494633 LUA.1: FSUIPC5_test -- AP buttons 0 494633 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 494633 *** EVENT: Cntrl= 66107 (0x0001023b), Param= 0 (0x00000000) AP_PANEL_HEADING_OFF 494633 *** EVENT: Cntrl= 65819 (0x0001011b), Param= 0 (0x00000000) AP_NAV1_HOLD_OFF 494633 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF 494633 *** EVENT: Cntrl= 66104 (0x00010238), Param= 0 (0x00000000) AP_PANEL_ALTITUDE_OFF 494633 *** EVENT: Cntrl= 66116 (0x00010244), Param= 0 (0x00000000) AP_PANEL_VS_OFF 494633 *** EVENT: Cntrl= 65814 (0x00010116), Param= 0 (0x00000000) AP_APR_HOLD_OFF 494633 *** EVENT: Cntrl= 65813 (0x00010115), Param= 0 (0x00000000) AP_LOC_HOLD_OFF 494633 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 0 (0x00000000) AP_BC_HOLD_OFF 494648 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 150 (0x00000096) VOR1_SET 494648 LUA.1: FSUIPC5_Test :: CRS = 150 494648 LUA.1: FSUIPC5_Test :: HDG = 170 494648 LUA.1: FSUIPC5_Test :: ALT = 3050 494648 *** EVENT: Cntrl= 66037 (0x000101f5), Param= 28 (0x0000001c) AP_SPD_VAR_SET 494648 LUA.1: FSUIPC5_Test :: SPD = 28 494648 LUA.1: FSUIPC5_Test :: VS = -50 494664 LUA.1: FSUIPC5_test -- AP buttons 1 494664 LUA.1: FSUIPC5_test -- AP buttons 0 494680 LUA.1: FSUIPC5_Test :: CRS = 151 494680 LUA.1: FSUIPC5_Test :: HDG = 171 494680 LUA.1: FSUIPC5_Test :: ALT = 3100 494680 LUA.1: FSUIPC5_Test :: SPD = 29 494680 LUA.1: FSUIPC5_Test :: VS = -40 494695 LUA.1: FSUIPC5_test -- AP buttons 1 494695 LUA.1: FSUIPC5_test -- AP buttons 0 I let this carry on till here: 592757 LUA.1: FSUIPC5_test -- AP buttons 1 592867 LUA.1: FSUIPC5_test -- AP buttons 0 593085 LUA.1: FSUIPC5_Test :: CRS = 164 593116 LUA.1: FSUIPC5_Test :: HDG = 184 593147 LUA.1: FSUIPC5_Test :: ALT = 9300 593147 LUA.1: FSUIPC5_Test :: SPD = 151 593179 LUA.1: FSUIPC5_Test :: VS = 900 593272 LUA.1: FSUIPC5_test -- AP buttons 1 593397 LUA.1: FSUIPC5_test -- AP buttons 0 593600 LUA.1: FSUIPC5_Test :: CRS = 165 593631 LUA.1: FSUIPC5_Test :: HDG = 185 593678 LUA.1: FSUIPC5_Test :: ALT = 9400 593709 LUA.1: FSUIPC5_Test :: SPD = 152 593740 LUA.1: FSUIPC5_Test :: VS = -900 So, it was running fine, no errors, for a full 251 seconds with no problems. Over 4 minutes. Do I need to run it for longer? I think something else it doing on here. I'm testing on Win7 as all my debugging tools are here, but I'll now conduct a similar test on Win10. Pete

With which versdion of FSUIPC5? ALL of the feedback on the recent updates confirm it is fixed. If something is still wrong with 5.101d or 5.101e I most certainly need a log and other details from you, most urgently as I've crossed that problem off -- it also affected 4.967 which uses the same code, and I was about to release 4.968 as a fix for FSX/P3D3!. Make sure you have FSUIPC5101e_TEST.zip installed, and then add these lines to the [General] section of the FSUIPC5.INI file: Debug=Please LogExtras=x200000 and please show me the Log file after plus your FSIPC5.INI and the FSUIPC.JoyScan.csv file. I'm afraid this is more important than the offset writing problems at present. Pete

Just copy the files over -- FSUIPC4.INI needs to be renamed FSUIPC5.INI, that's all. Copy also other files you need, like MCRO and LUA files, and the whole PROFILES sub-folder if it exists. Pete

Looks like you are using the .NET DLL. I'm afraid I know nothing about that -- please post in the .DLL Net subforum -- one of the SubForums above this forum. I'm sure Paul Henty, the author, will be able to help. Pete

Yes. If you are using a different name, though, you will need to do it by editing the KEY file. Why is that? That will stop me using P3D4 then. Surely they don't need to do any changes? Pete

Assigned "direct" or via FS axis controls? Does the problem still occur if you remove the Axis assignments (temporarily) from the INI file? Pete

Okay, thank you. BTW are all these: 297562 Exception 20 "DATA_ERROR", Ref 3157, Index param 1 on write SetData for "AUTOPILOT THROTTLE ARM" 297562 Exception 20 "DATA_ERROR", Ref 3158, Index param 1 on write SetData for "AUTOPILOT THROTTLE ARM" 297562 Exception 20 "DATA_ERROR", Ref 3159, Index param 1 on write SetData for "AUTOPILOT THROTTLE ARM" 297562 Exception 20 "DATA_ERROR", Ref 3160, Index param 1 on write SetData for "AUTOPILOT THROTTLE ARM" 297609 Exception 20 "DATA_ERROR", Ref 3162, Index param 1 on write SetData for "AUTOPILOT THROTTLE ARM" 297609 Exception 20 "DATA_ERROR", Ref 3163, Index param 1 on write SetData for "AUTOPILOT THROTTLE ARM" 297625 Exception 20 "DATA_ERROR", Ref 3165, Index param 1 on write SetData for "AUTOPILOT THROTTLE ARM" (etc etc) a result of ONE offset write, or is this being repeated in LINDA -- for instance, if it sees the state has not changed correctly? Do you have axes assigned and calibrated? Direct to FSUIPC or using FS controls? Pete

Ah, shame. Maybe I need to install and run LINDA, then. Could you email me whatever I need, with instructions on how to repro the problem in the very simplest way? petedowson@btconnect.com. As you'll see from the previous message in this thread, I have tried tp repro it using pcssundahl's methods, without success so far. This problem is the only thing holding back the full release of FSUIPC 5.102, with joystick scanning fixed (including the crash with no real joysticks), PFCcom and PFChid support, and Active Sky WxRadar facilities working correctly. Until I can reproduce your problems here I can see no way to fix them, or otherwise inform L-M of a Simconnect problem, if that is what it is. Currently I can see no place where I can realistically add enough logging to allow me to diagnose it on your systems, though I'm still looking at that possibility. Pete

I've tried all this here, and then made loads of changes through the FSS MCP/EFIS and the FSS 737 OVHD, but I cannot provoke any problems. Everything carries on working fine. In your calibrations, if the "filter" option essential to generate the problem? Are you assigning axes "direct to FSUIPC" or via the normal FS Axis controls, "Axis xxxxx Set"? Maybe you posted your INI here somewhere -- I'll take a look. Meanwhile, just in case it is magically "cured" by no specific action on my part, please try this version, which is exactly the same as the so-far unreleased build I'm using: FSUIPC5101e_TEST.zip Please also enable ipcWrite logging, and Event logging (both events and axis events), so I can see if I can spot a relationship between inputs and the start of the problem. No need to provide the whole log, as it will be very large I expect, just the 50 or so lines before and after the first error. Oh, and please show me the INI file too so I can compare settings. Thanks Pete

Good. Thanks. Pete

Ah, from a program. Sorry, I missed that. In that case surely you arefamiliar with the Offset Status document in your FSUIPC Documents folder? Please look up offset 0D70 there and see if you understand it. Sorry, it is i English. Let me know what you don'tt understand. Well, in the sense that I've got too much to do this week and not enough time, yes. But if you look through the Forum you see I still answer every question, and promptly too. I only said I nearly missed your query because yo posted it in the wrong place. Pete

You nearly didn't, because yu posted this in the FAQ sub-forum, a reference for answers NOT a support forum! I've moved it now. PLEASe use the Support Forum for support, not random subforums. You have something very seriously wrong in your system then. Absolutely nothing takes that long, even if there are hundreds of L:Vars defined in your add-on. Try other L:Vars to see if it is a general problem in that aircraft, and trry different L:Vars in other aircraft to see if it is your system or only a faulty add-on. Who said that? 0D70 is used for executing macros from a program or Lua plug-in. It is no different from assigning a button or a keypress except it requires another program. Offset use is described in the Offsets list in your FSUIPC Documents folder. But as I said, you need to make a program to use it. Pete

FSX displays Frame Rate with Shift+Z so just program that. I don't know. Is there one in FSX-SE? If it is only a menu item, then no, I don't think there will be a way. But also look through the list of FSX controls supplied in your FSUIPC Documents subfolder, in the Modules folder. Pete

Which version of FSUIPC5 are you using? Have you tried the update from Download Links subforum yet? Pete

I think that the only reason axis calibration brings the problem on is that there will then be many many more requests being made to SimConnect. I suspect it's some sort of SimConnect overloading, but how it then returns errors relating to write requests for SimVars for which FSUIPC doesn't issue them I don't know. Anyway, I wil try to reproduce it here today. Pete

I'm not sure if it in Win10 adding it, or it got installed by some other driver, but I think the cause is that odd device "BEEF" "FEED". Even the VID and PID look phoney. Anyway, now please try FSUIPC5101d_TEST.zip still with these lines added to the[General] section of the FSUIPC5.INI file: Debug=Please LogExtras=x200000 and please show me the Log file after, no matter what the result. This version attempts to weed out odd looking devices rather than ask them for more particulars. Pete

Good. So ... fixed? Looks lke it. Seems that device FSUIPC was picking up didn't respond well to queries made of it to see if it was suitable for button/axis assignment. Pete

Thanks. Your registry / DirectInput result are the same as at least one other with this problem: a "Flight Mode Switch": 282 ---------------------- Joystick Device Scan ----------------------- 282 Checking: \\?\hid#ene0110#6&39a4dcf9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 282 Usage=12, UsagePage=1, =Flight Mode Switch 282 Error 1 [00000001] returned on HidD_GetProductString: (\\?\hid#ene0110#6&39a4dcf9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}) 282 Product= <not readable at this time: maybe device disconnected?> 282 Vendor=0CF2, Product=9010 (Version 1.1) 282 ------------------------------------------------------------------- 282 ****** Registry scanning: VID=0CF2, PID=9010 ****** 282 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0CF2&PID_9010\Calibration\0" 282 ... and a "GUID" value 282 GUID= {07C10890-913A-11E5-8003-444553540000} 282 NB: not valid for this device according to GetConfig! He says he doesn't have one either! Another very odd thing is that it gets into the INI: [JoyNames]AutoAssignLetters=No1=1.GUID={07C4D920-913A-11E5-8006-444553540000} albeit with no name (which was unreadable), yet the log doesn't get that far -- might that section have been created by an earlier session. I see from the Calibrations that you must have had a device operating at some stage. Anyway, now please try FSUIPC5101d_TEST.zip still with these lines added to the[General] section of the FSUIPC5.INI file: Debug=Please LogExtras=x200000 and please show me the Log file after, no matter what the result. Pete

Thanks. Waiting to hear from the others now ... Pete

Unless you set those numbers, they are determined by what's in the Registry, not by me. If you change them, FSUIPC "fixes" the registry accordingly. The letters are either chosen by you, or assigned automatically (by "AutoAssignLetters=Yes") in order A - Z (missing O and I), as the Joysticks are seen. The numbers are not relevant to that. Version 5.102 will be replacing 5.101 and it's ilk soon. maybe tomorrow. Pete