Pete Dowson

No, the problem with calibrating joysticks in FSUIPC which are assigned in P3Dv3 is that FSUIPC cannot read those values whilst in the calibration dialogue. Once calibrated they would work, but you can't actually set the calibration values. The business of reading joystick values whilst in a Modal Dialogue needs solving by Lockheed-Martin -- it is a broken SimConnect facility. The joystick scanning is simply the initialisation sequence in FSUIPC where it checks to make sure it has a numerical joystick ID for each joystick attached. If not it tries to assign one. This was purely to get around the many occasions folks have found FSUIPC not seeing a newly connected joystick because, especially in Win8 and Win10, the installers don't seem to be setting that value these days. The only outward sign that the joystick scan has been done is the list of devices found in the Log, near the start. Pete

No, there are no real duplicates, or certainly none which matter. The only lines in [JoyNames] which define what you actually have connected are those with the numbers. You have numbers 0-4, 5 different devices, no duplicates. The letter lines are there as a permanent link between the numbers, assigned in your Registry, and the letters which FSUIPC will be using in your Buttons and Axes assignments. The only letters which link up to the 5 actual devices are F to K. The A-E entries have non-matching GUIDs and so won't be used. I don't know how they got there, but those are the only ones you might delete. If you delete ALL of the letter-assigning lines then none of your assignments will work because FSUIPC won't be able to relate the devices to the letters in the [buttons and [Axes sections. Since you haven't included those sections in your post I've no idea what letters are currently in use. Once you are happy with the letter assignments you could change "AutoAssignLetters" back to "No" so it doesn't make re-assignments if you add new devices, or devices which Windows thinks are new. Then just remember to choose you own letters and edit the [JoyNames] section manually. Pete

Okay, no need for the log. I've duplicated it. The problem is in P3Dv3. it is different to previous versions, and to FSX. It no longer uses the Parameter in the KEY EVENT for those events which normally, via keyboard, are followed by 1-9 (which invoke KEY EVENTS "SELECT n").. I'll have a look at re-programming FSUIPC to cope -- but it covers a lot more than just Exits, so first I shall report it as a bug to L-M. Pete

It's okay, I deleted it. Pete

I think there are LOTS of problems with key events and axes in P3Dv3. I haven't unravelled it all yet, but they've changed so many things I don't know how long it will take to sort it out. It looks like much of the SimConnect system is now incompatible. I'm hoping we can get things worked out, but I suspect it'll need updates from L-M, because I'm not about to rewrite FSUIPC completely! Meanwhile, do try FSUIPC version 4.947c, just uploaded. I seem to be having to make twice daily updates to keep up with what we are discovering about P3Dv3. v:-( Pete

Please download FSUIPC 4.947c, now available. Pete

Please download FSUIPC 4.947c, now available. Pete

Please download FSUIPC 4.947c, now available. Pete

Please download FSUIPC 4.947c, now available. Pete

Please download FSUIPC 4.947c, now available. Pete

Please download FSUIPC 4.947c, now available. Pete

I'll do some more testing with FSUIPC issuing the controls. It might be something to do with SimConnect priority levels. I've a feeling L-M has messed quite a lot of things up in version 3. The changes have been pretty drastic. Can you show me the log, please? Pete

I need the crash data from Windows event viewer too, please. Pete

The HidScanner log isn't relevant here as the log shows it is well past the joystick scanning. But I need to know if the crash details you posted before correspond to the same version of FSUIPC -- i.e. 4.947b? Pete

With FSX (only, not FSX-SE, where it is fixed internally), FSUIPC can trap and prevent ONe (1) out of many possible G3D.DLL crashes. It was one brought about by rather dodgy scenery -- it never happened to me in any case, even without that fix. It doesn't do any other "bug" fixes for FSX, and the G3D patch didn't need a purchase in any case. It was added long ago (Feb 2012) -- see the Version 4.80 entries in the FSUIPC4 History document, which will be in your FSUIPC Documents folder. Anyway, perhaps you should try FSX-SE. It is more reliable and faster, IMHO. Pete

Can you show me the FSUIPC4.LOG for the same thing, please. From the P3D Modules folder. Have you tried 4.947b, posted earlier today? Pete

I need the FSUIPC4 log please, for both instances. There's no reason FSUIPC should crash just because ESP SimConnect is installed -- in fact it always used it before quite happily, and that SimConnect is later than the FSX SP2/Acceleration version which also works fine. When you say your controls aren't recognised, do you mean for assignment in FSUIPC, or just for calibration? If the latter, please see the pinned notice at the top of the Forum. Pete

Well, whatever is wrong there it isn't related to the earlier reports in this thread. I need the crash details from Windows event viewer please as there's nothing helpful in the log as far as it got. "Starting everything now" iswhere it is all set up and ready to go. Pete

Could you try FSUIPC version 4.947b, just released, please, and let me know? I think it must be some timing glitch between FSUIPC and as_btstrp, but with ASN actively "correcting" the loading order I found it hard to reproduce. Thanks, Pete

Could you try FSUIPC 4.947b, just uploaded, please? I've done all I can to avoid a problem with odd devices during the scan. I'm still not totally sure how HidScanner got away with it when FSUIPC didn't! The code is almost identical. Anyway, I've included more precautionary checked. Thanks, Pete

For "toggle aircraft exit" , when used normally, it needs the "Select 1, 2, 3, or 4 control afterwards. With FSX (not tried with P3Dv3) you could put the parameter in the control. But then it's parameter = 1 for main doors, 2 for next, 3 for next, 4 for next, if 4 separate door operations are supported. Certainly the standard door control (shift+E then 1, 2, 3, or 4 on the main keyboard) is working here for me with P3Dv3. The offset 3367 acts upon the bits,, 0, 1,2 or 3 (togglebis 1,2,4,8) in exactly the same way in P3Dv3, it just sends the toggle aircraft exit with the correct subsequent control. Try using the logging in FSUIPC to see what is happening -- event logging. If the controls are being sent, whether from FSUIPC offset changes or by using the keyboard, and the aircraft doors don't respond, then maybe it's the aircraft? Pete

Okay. Perhaps you re=post here with the answer, when you have one? Thanks, Pete

Sorry, i think you need A2A help. I don't have many add-on aircraft and can't possibly diagnose them all. If your controls work with default aircraft that proves FSUIPC is working. The rest is up to A2A. Pete

I really don't know. Depends on what the crashes are. You'd be better off going to the AVSIM FSX forums for help. There's one dedicated to FSX crashes. Pete

Yes, it's a bug in P3Dv3 which has been reported. I don't think you can currently use a trim axis at all in P3Dv3. Check the L-M forum. For FSUIPC, though, if you assigned to the FSUIPC "direct to calibration" trim it should work for calibration, though it may still crash P3Dv3. . I'll check it tomorrow when I get P3Dv3 setup again. Pete