Pete Dowson

Thanks! Does the App Store ask you if you have one? I've never noticed. Yes, three of various vintages plus a Mini I use on holidays (steam trains). I use two iPads in the cockpit, one mounted each side, for charts and so on. That is, if I ever get a chance to fly! My email is petedowson@btconnect.com. Whichever is easiest. I'm a bit overloaded at present and the quickest and easiest method possible would be good. Do I need instructions on how to force it? I assume the Server is on the website somewhere? Pete

So, I need to pay to download then into my phone anyway, from the App store? Pete

Thanks. I have a complete list of the ones it could happen with, I just don't know why at present. So, I could use one of your apps to generate the error so I can debug it, right? Which app, and what would i need to do to provoke it with 100% certainly, please. If you could instruct me on this it very well might help speed things up. So thanks in advance. Pete

Sorry, what sorts of "Apps"? Do you mean for an iPhone or iPad, or an Apple PC? [LATER] Thanks for the offer. I've looked at your website. What sort of 'problems' would they help me with? Sorry if I'm not seeing what you mean. I assume those apps need an interface program on the FS PC. Talking to FSUIPC or SimConnect? Pete

Odd, because it was for exactly this problem reported in 4.966c and before that the Joystick Scanning was completely revised! Your INI file shows two yokes called AGRONN B737 Yoke V2.1 which are seperately detected and assigned as devices C and D. But you said: I do only see the one set of PFC USB Pedals assigned, though, device F. The other has some odd results I need to look into. I need more detiled logging on the scanning. For this please add these lines to the [General] section of the FSUIPC INI file: Debug=Please LogExtras=x200000 I don't have a test version with further improvements yet for FSUIPC4 (expect 4.968 soon). But you could try this in P3D4, and show me the same files for that, please (with the logging addition above): FSUIPC5101a_TEST.zip Thanks, Pete

I've not been able to reproduce this at all. In fact it looks impossible. There's only one call to the Macro execution function in the whole program, for all types of input, and if that succeeds in executing a macro (i.e. it finds one and identifies it for execution by FSUIPC) then the only calling function exits, doing nothing more for that input. So it remains a puzzle at present. Perhaps you could do some more logging please -- logging in PFCHid and also log Events in FSUIPC. I've re-programmed the fast/slow determination for the decoders. If you'd like to test that please download PFChid149_TEST.zip Pete

Your problem is not related to this thread and a HidScanner log is not needed! Please see your own separate thread. This one is for P3D crashes on loading, at the Splash Screen, which occur only when FSUIPC5 is registered, and, it seems, only for those folks with no joysticks whatsoever. Pete

That might be a good clue. Thanks. I'll be dealing mainly with the LINDA author over this (another programmer) as I think that will speed things up, so if you could follow it in that thread it would be useful. Thanks. Pete

Yes, this is because the TestOptions parameter added does a write test on all of the variables during FSUIPC initialisatin. Don't worry about those now, the info was for me. 179406 *** EVENT: Cntrl= 65814 (0x00010116), Param= 0 (0x00000000) AP_APR_HOLD_OFF 179406 *** EVENT: Cntrl= 65813 (0x00010115), Param= 0 (0x00000000) AP_LOC_HOLD_OFF 179406 *** EVENT: Cntrl= 65811 (0x00010113), Param= 0 (0x00000000) AP_NAV1_HOLD_ON 179406 SimWrite[145]: 0804="AUTOPILOT BACKCOURSE HOLD", DDef=00000007, Ref=3880, Size=4 [flt=0.000000, int=0, 0x00000000] 179406 Exception 20 "DATA_ERROR", Ref 3880, Index param 1 on write SetData for "AUTOPILOT BACKCOURSE HOLD" 179406 SimWrite[132]: 07D0="AUTOPILOT ALTITUDE LOCK", DDef=00000007, Ref=3881, Size=4 [flt=0.000000, int=0, 0x00000000] 179406 Exception 20 "DATA_ERROR", Ref 3881, Index param 1 on write SetData for "AUTOPILOT ALTITUDE LOCK" Something really strange is occurring. It is quite happily sending events for the assorted AP offsets you are writing, and then, suddenly, switches to the SimVar writing -- to non-writeable SimVars (as determined, in fact, by the initialisation test. I now need to find out why this is occurring. Corruption of the tables in memory? Nothing actually writes to those decode tables in my code, at least nothing programmed. I think I'll have to write a Lua plug-in to do something like what you are doing. Writing ot, what, 8 or so AP switches up to 20 times per second? I don't suppose you have a simpe 9not needing LINDA) plug-in which can do that, and which gives the same symptoms on your System, have you? If not, it might speed things up if you could make one, test that it fails, then let me use it do I can debug the issue here. Thanks, Pete

That seems to be the common theme amongst those with this problem. I've tried here on a PC with no joysticks, but it works fine. But that was on a Win7 PC. I'll try on Win10. Looks like the non-Joystick device that DirectInput is giving me (I'm actually asking for "connected joysticks"!!!) causes the crash when I try to read its configuration (number of buttons, axes, and current values). This is part of my "validity" checking on devices before adding them to the scans for assignments. Using Win10 I suppose? I bet it's another bug in Win10 which I need to work-around! I've had several already.. :-( Pete

I've been testing writes to those offsets here. Each one does generate the correct event ("AP_MASTER" etc etc). I'm at a bit of a loss still understanding why it might then be trying to write the SimVars directly. It makes no sense. Could you repeat a test on one or two of those offsets but first edit the FSUIPC5.INI, adding these lines to the [General] section: Debug=Please TestOptions=x10 LogEvents=Yes and show me the resulting log, please. Pete

Sorry, you need to ask iFlyToFSuipc support. I know nothing about thatprogram, sorry: I've never heard of it. Pete

In all cases so far the Joystick Scan seems to show a device which is not of the Joystick type. It shouldn't even be told of those -- if there's no joysticks, it should simply be empty, no scan. So, do YOU have any joystick type devices connected at all? Please add these lines to the [General] section of the FSUIPC5.INI file: Debug=Please LogExtras=x200000 This will log the detail of the scan process and its immediate aftermath. Show m the resulting log after the crash, please. Pete

Seems to affect a few users and has already been reported. Is it occurring during a session, or when P3D4 is still on the Splash Sctreen? I need to see the FSUIPC5.INI and the FSUIPC5.LOG, both from the Modules folder, please. Pete

Well, naturally, because no attempts would be made to write the variables if the offsets were not written. You have a couple of errors there: the documented ones are AP 07BC, HDG 07C8, NAV 07C4, SPD 07DC, ALT 07D0, VS 07EC, APR 0800 and REV (BC) 0804. I'm a bit puzzled at present because the code inthis area is the same from FSUIPC3 and FSUIPC4, and those values aren't writeable directly withSimVars in either P3D3 or P3D4. There shouldn't be any DATA ERROR for commands which should not be given -- FSUIPC has to use the Events (Controls) for them, and always has. I'll get back to you. Pete

No, it is something to do with the classification of which SimVars are writeable. I'm looking at it today. Im currently not sure whether it is an error in my conversion to 64-bit, or a problem in P3d4. There are several other non-LINDA reports now of similar problems from other programs using the offsets for switches. Pete

Which version of FSUIPC4? I think your FSUIPC4 must be out of date -- the currently supported version is 4.967 which has similar problems (to be solved in 4.968, imminent). Please try 5.101a from this link: FSUIPC5101a_TEST.zip Pete

You posted an almost identical report in a different thread! Please do not post in multiple places, and anyway not in a thread not remotely connected with your subject. Pete

What do these iPads do? What software are they using to talk to FSUIPC? Is there something you install on the P3D PC, an EXE? The interface for application programs hasn't changed. There's no "64-bit" interface, though if it is a DLL it would have had to be converted to 64-bit to run inside P3D4. The log shows some access to offsets driving variables in P3D which have already been reported as having problems. I'm already investigating those (see the thread about Linda). But there are none regarding axes, only other switches. Pete

I only support sims based on Microsoft Flight Simulator, of which I've been a dedicated user and for which I've been a developer of software since the breginnings, the days of SubLogic (Bruce Artwick). However, I'm currently dubious even about dealing with DTG's FSW, which is probably a close derivative of FSX, let alone something not even related to FS. I never touched X-Plane either. Sorry. I am 74 this year and do not plan on starting major new projects. Pete

What is the "non USB Cirrus 2"? Does it work with PFCFSX.DLL in FSX/P3D3? If so then it should be fine with the nearly-ready PFCcom64.dll. Pete

Okay, thank you. I'll tske a look. Pete

It's something odd with SimConnect. The easiest solution for me to to mark those values as non-writable. This will automatically make it revert to the Event / control method. Pete

Can you show me these files, then, please, all from your P3D Modules folder: FSUIPC5.INI FSUIPC5.LOG FSUIPC5.JoyScan.csv Thanks, But you aren't even close to being 'up to date'. And if no one uses new versions and let's me know of problems, then nothing will ever progress and there wouldn't have been an FSUIPC5 at all. Mind you, I could have retired and done some flying myself then! ;-) So maybe that's best. I'll never change anything, I'll ignore all user requests, and go fly. BTW you can always keep a copy of your last "fully working one" (for you) so you can restore after reporting the problems so that they get fixed. It was because so many folks stayed with 4.966c and never tested 4.966m or updated to 4.967 that the newer problems (for some systems, not many in fact) never came till too late for the FSUIPC5.1 release last week. When problems only occur in certain configurations there's no way they'll come to light unless enough people are involved. And that' more than a hadful of Beta testers. Pete

Please don't keep sending my my own program (the DLL). It is just a waste, and I already have a copy of my own program, believe it or not! The LOG shows similar to grapeNo1's, ending with 140 ---------------------- Joystick Device Scan ----------------------- 203 Product= <not readable at this time: maybe device disconnected?> 203 Vendor=0CF2, Product=9010 (Version 1.1) 219 ------------------------------------------------------------------- Can you please run HidScanner too, as I asked him, and show me its log? It might prove useful to see if there are similarities. Pete