Pete Dowson

They are just macros, like any other, and will appear in all the assignments drop downs in the form "filename:macroname". They do appear in all three lists -- Axes, Buttons and Keys. Please check again, you must be missing them. Hint: you can move quickly to about the right place in the dropdown by starting off the drop down then typing the first few chanracters in the name -- in this case the name you gave for the macro file. Otherwise, please show me your FSUIPC6.INI file? Pete

That is correct. you can used WideFS with P3D4 by registering it with your existing key. WideFS7 is still the same product, effectively, so needs no re-purchase. FSUIPC4 is for FSX and P3D1-3. You will need to upgrade to FSUIPC6 for P3D4, and purchase that if you need to use its user features. Pete

Okay. Normally, on both props and jets, stopping the engine is by cutting the fuel off, which in FS (since FS98 I believe), and in P3D, is done by Mixture Lean, same as Shift+Ctrl+F1 with default keyboard assignments. Pete

So those values don't apply. They are set by the PFC driver which is specific to the PFC hardware unit with the motorized trim wheel. Pete

Do you mean to make a a MOUSE wheel operate the elevator trim? If so, FSUIPC provides such an option -- see the "Miscellanous" tab in the FSUIPC options. Version 4.70b is very much out of date. Please update to the latest version of FSUIPC4. We cannot support old versions. So you are trying to do what, exactly? I don't remember exactly what that offset represents, but it is just an indicator that the motorized trim wheel is operating. Do you have a PFC unit with motorized trim wheel? 3371 is to do with motor action, as it says. I'm not sire you moving the wheel is relevant. What exactly are you trying to do? If you can explain then perhaps i can help. but first download the current version of FSUIPC4 (see FSUIPC.COM) and install that. Pete

Good! Happy flying! Pete

That would make no different that I know, unless your client FSUIPC applications are being run as administrator. Nothing useful. Why supply the FSUIPC logs? You haven't supplied the WideClient logs for comparison! Those are the most important! It's the clients not getting the response they need -- it is the clients that are being blocked Pete

So, how did you make the P3D4 connection work? And if not P3D5, why not? Pete

So what is setting it? Since the virtual button offsets are supposed to be INPUTS to the software (ProSim in this case), ProSim should NOT be programmed to write to them! It is the job of your cpFlight switches to do that! I think you might be getting yourself confused between switch inputs and ProSim settings. Either way, as I said, it isn't an FSUIPC matter. FSUIPC is merely a repository for the data you are storing in and reading from these offsets. FSUIPC isn't doing anything with them if you are not programming the virtual buttons so signalled. Pete

0x1 means the switch is ON. It would be 0x0 if it was OFF. If it got set to 0x1 then I assume that was your cpflight software doing it. If it doesn't change when you operate the switch then to me that suggests a broken switch or a loose connection. Don't cpFlight provide any way to verify that your hardware is all working okay? Either way, it really isn't an FSUIPC support matter, but cpflight as I suggested before. Pete

You can check yourself. In the FSUIPC Logging tab, Monitor (8right-hand side), add offset 3340 and 3344, both as type U32, and check Hex (so we can see the bits set or clear). Set for the normal log below, so the values are logged. (You can display on screen also). Use your switches and see if you get the offsets changing. You can also set or clear the bits by assigning a button or keystroke to Offset Byte Setbits, Offset Byte Clearbits, or Offset Byte Togglebits, giving the offset as x3340 and the bits as parameter (1 for 3340.0, 2, 4, 8, 16 ... 128 for 3340.7) Pete

Nothing I know of. You need to enable Button logging and Event logging (not axes) in FSUIPC's logging tab, then reproduce the problem. ZIP up the log and attach ithere. Also please do the same with your FSUIPC5.INI file. Both files will be found in the Modules folder within your P3D4 installation. You say Why do you think FSUIPC "deactivating and reactivating" (whatever that means) would cause all buttons to be signalled? If you have a USB device which keeps disconnecting and reconnecting, on its own, then FSUIPC will re-scan the devices to make sure it knows about any possible additional device which can have assignments. But this process, whilst possibly causing a slight stutter, would not generate any button or switch changes. Let's see the log and settings. Pete

Okay. Version 4.5.14 is okay too, no problems. here I assigned Ctrl+Shit+7 to "TOGGLE AIRCRAFT EXIT" with parameter 2. Here's the whole sequence including key presses and releases: 774545 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2 774545 .. Key not programmed -- passed on to FS 774748 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=3 774748 .. Key not programmed -- passed on to FS 775232 KEYDOWN: VK=55, Waiting=0, Repeat=N, Shifts=3 775232 FS Control Sent: Ctrl=66389, Param=2 TOGGLE_AIRCRAFT_EXIT 775232 .. This key is programmed in FSUIPC6 'Keys' options 775232 *** EVENT: Cntrl= 66389 (0x00010355), Param= 2 (0x00000002) TOGGLE_AIRCRAFT_EXIT 775310 KEYUP: VK=55, Waiting=0, Shifts=3 775731 KEYUP: VK=16, Waiting=0, Shifts=2 775746 KEYUP: VK=17, Waiting=0, Shifts=0 In the B738 the cargo doors open or close using this assignment, so it works as intended. As you can see, there is no Error reported as there was in your test. Now there may possibly be a bug in P3D version 4.5.13 which isn't in 4.5.12 or 4.5.14, but that seems highly unlikely to me. Therefore I suspect you have a corrupt P3D installation. Maybe you have some weather files which are corrupt -- that can have strange and unpreductable consequences, usually a CTD but not always. Se this thred: You could also try P3D 4.5.14 of course. I also re-checked the other method I suggested to you (and which I assume you didn't even try), using Offset 3367. This offset operates the doors directly, using SimConnect, without using any controls or events. I used key press Ctrl+Shift+8 for this. Here's the sequence: 781160 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2 781160 .. Key not programmed -- passed on to FS 781596 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=3 781596 .. Key not programmed -- passed on to FS 781908 KEYDOWN: VK=56, Waiting=0, Repeat=N, Shifts=3 781908 IPC Offsets Control: Ctrl=x0D00, Length=1, Offset=3367, Param=x2 781940 .. This key is programmed in FSUIPC6 'Keys' options 782018 KEYUP: VK=56, Waiting=0, Shifts=3 783125 KEYUP: VK=16, Waiting=0, Shifts=2 783234 KEYUP: VK=17, Waiting=0, Shifts=0 That also operated the cargo doors. Another advantage of using this direct method is that instead of using "Offset Byte Togglebits", as here, you could use "Offset Byte Setbits" to open or "Offset Byte Clearbits" to close doors. AND you can do this with multiple doors at the same time. With this offset method, set offset x3367, with these parameters: 1 = door 1 2 = door 2 4 = door 3 8 = door 4 Just add them for more than one at a time. I think that's really all I can do for you. Pete

Well there's nothing complicated in the INI. It's very simple and straightforward. But in the Logs you have shown the GEAR TOGGLE has always been instigated by a button press -- button 5 on joystick 1 (your yoke). There are no un-requested operation of the GEAR. The odd thing in the log is the other actions which seem to accompany some instances of that occurring, as in the last case: 556453 *** EVENT: Cntrl= 65793 (0x00010101), Param= 1 (0x00000001) YAW_DAMPER_TOGGLE 562859 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 563719 *** EVENT: Cntrl= 65798 (0x00010106), Param= 0 (0x00000000) AP_PANEL_HEADING_HOLD 564875 *** EVENT: Cntrl= 65799 (0x00010107), Param= 0 (0x00000000) AP_PANEL_ALTITUDE_HOLD 585484 *** EVENT: Cntrl= 65729 (0x000100c1), Param= 0 (0x00000000) AP_NAV1_HOLD 590594 *** EVENT: Cntrl= 66375 (0x00010347), Param= 0 (0x00000000) TOGGLE_GPS_DRIVES_NAV1 Now none of those actions are commanded by anything in FSUIPC. It looks like either the aircraft you are using does all that (maybe as a service to you, like an "easy" mode where it tries to help), or you have some sort of co-pilot program also running which decides to do all that for you. I'd check through whatever add-on (or add-in) programs you have running. AND try a different aircraft. I'm afraid I can't really see any more I can do to help. It just isn't being caused by FSUIPC. Pete

Okay. I have one like that on my aft overhead, but I've programmed that to operate a keypress in Pilot2ATC (the ATC program I use) to switch between two different sound outputs -- one to my headsets and the other to my overhead speakers. All this is on a separate PC from both ProSim and P3D. So I really don't know how it relates to what you are programming. It definitely sounds like a question for cpFlight. Have they programmed the pedestal, or did you? Pete

My intercom switch? Sorry where? Pete

If it is possible, then yes, one will be produced. But it is first entirely dependent on FSUIPC, and we cannot give any hard commitments on that yet either. Currently there simply is not sufficient information for us to commit to anything nor provide any sort of timescale. We have good intentions and want to support MSFS in all the ways we support P3D, but whatever transpires It will certainly be a lot of work. There is little in common with the previous simulators we have supported.. Pete

You could try looking at these Logs yourself. I can point out where "GEAR TOGGLE" is used. I just search on GEAR. you can do the same. I'll do this just this once more, then I think yo should check for yourself. Here's the first instance. I include a lot because you can see from this that ONE button press (Joy 1 button 5) instigates the GEAR TOGGLE, but there's then a whole lot of other stuff that is most certainly NOT instigated by actions in FSUIPC: 518375 Button changed: bRef=0, Joy=1, Btn=5, Pressed 518375 [Buttons] 3=P1,5,C65570,0 518375 FS Control Sent: Ctrl=65570, Param=0 518375 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE 518516 Button changed: bRef=0, Joy=1, Btn=5, Released 556453 *** EVENT: Cntrl= 65793 (0x00010101), Param= 1 (0x00000001) YAW_DAMPER_TOGGLE 560203 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW 560250 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW 560281 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW 562859 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 563719 *** EVENT: Cntrl= 65798 (0x00010106), Param= 0 (0x00000000) AP_PANEL_HEADING_HOLD 564875 *** EVENT: Cntrl= 65799 (0x00010107), Param= 0 (0x00000000) AP_PANEL_ALTITUDE_HOLD 585484 *** EVENT: Cntrl= 65729 (0x000100c1), Param= 0 (0x00000000) AP_NAV1_HOLD 590594 *** EVENT: Cntrl= 66375 (0x00010347), Param= 0 (0x00000000) TOGGLE_GPS_DRIVES_NAV1 627562 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW 627594 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW 627625 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW 627672 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW 627703 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW 627734 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW 631500 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 631531 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 631609 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 631641 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 632125 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 632156 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 632187 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 632234 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 632750 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 632750 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 632812 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 633578 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 633656 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 634375 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 634453 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 641391 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW 641422 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW 641453 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW 641500 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW The second seems better. there aree other actions around it seemingly mostly to do with other button and key presses. 1697078 Button changed: bRef=0, Joy=1, Btn=5, Pressed 1697078 [Buttons] 3=P1,5,C65570,0 1697078 FS Control Sent: Ctrl=65570, Param=0 1697078 Button changed: bRef=0, Joy=1, Btn=24, Released .... 1697078 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE And that was it. I assume the first is the instance which concerns you. You have some add-on which is doing these things you don't like. Whether it's to do with the aircraft, or you have some other add-ons, or perhaps some plug-ins, i don't know. but I think you need to carry out a process of elimiination of those, because it isn't FSUIPC. Attach you FSUIPC.INI file and I'll check that you've not got any rogue assignments. Pete

Looking at the log 1279047 FS Control Sent: Ctrl=66389, Param=2 TOGGLE_AIRCRAFT_EXIT 1279047 .. This key is programmed in FSUIPC5 'Keys' options 1279047 Exception 1 "ERROR", Ref 3387, Index param 2 on TransmitClientEvent, object=1, id=66389 (TOGGLE_AIRCRAFT_EXIT), data=2 You seem to have a different error. There's no way you should get a Simconnect error like that with the parameter 2. I saw you were using P3D 4.5.13. I'm still on 4.5.12. The control with a parameter of 2 most certainly always worked with all the versions of FSX and P3D i used it with. I can try to test with 4.5.13 but it may not be for a day or two. BTW I checked back, and the FSUIPC6.INI file you uploaded earlier had no TimeForSelect=4 parameter in it at all. Do you know how that went missing? Could you try adding it please? I goes into the [General] section. [LATER] I can't get 4.5.13 now. It's been superseded by 4.5.14. I'll test with that. Pete

What numbers. Do you mean FSUIPC Offsets? The list is in the Offsets List document installed with the rest of your FSUIPC documentation. If you didn't understand about offset 3340 how come you are programming ProSim for it? So whatever you programmed to set that bit is obviously wrong. How did you program it? Or is this something cpFlight did for you? If so I think you need to go back to them. Pete

Sorry, you'll need to ask VirtualCol support about that. FSUIPC can do no more than what you ask it to do -- send Throttle Decr and Throttle Cut in this case. This is the same as pressing F2 for decrease and F1 for cut, using default keyboard assignments. (except those operate all engines not specific ones). Maybe the programmers of that aircraft have used throttle cut to also cut fuel? That's normally done for jets by Mixture Lean (keyboard Shift+Ctrl+F1). You can of course check what happens with default assignments to eliminate FSUIPC. But check also that you haven't got double assignments -- maybe you've not disable controllers in P3D? Pete

All of the virtual buttons are treated the same in FSUIPC, just assigned different joystick numbers from 64. Did you check the buttons assignment tab in FSUIPC Options to make sure your button showed up as joystick 64, button 0? Pete

There are THREE instances of the same two buttons being pressed, one of which operates "GEAR TOGGLE": #1 186797 Button changed: bRef=0, Joy=1, Btn=9, Pressed 186797 [Buttons] 1=R1,9,Cx32000BC0,x3FFF0100 186797 Repeating flag set: bRef=0, Joy=1, Btn=9 (RepeatDelayCtr=1) 186797 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0BC0, Param=x3FFF0100 186938 Button changed: bRef=0, Joy=1, Btn=9, Released 191188 Button changed: bRef=0, Joy=1, Btn=5, Pressed 191188 [Buttons] 3=P1,5,C65570,0 191188 FS Control Sent: Ctrl=65570, Param=0 191188 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE 191453 Button changed: bRef=0, Joy=1, Btn=5, Released #2 337109 Button changed: bRef=0, Joy=1, Btn=9, Pressed 337109 [Buttons] 1=R1,9,Cx32000BC0,x3FFF0100 337109 Repeating flag set: bRef=0, Joy=1, Btn=9 (RepeatDelayCtr=1) 337109 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0BC0, Param=x3FFF0100 337141 Button changed: bRef=0, Joy=1, Btn=9, Released 353234 Button changed: bRef=0, Joy=1, Btn=5, Pressed 353234 [Buttons] 3=P1,5,C65570,0 353234 FS Control Sent: Ctrl=65570, Param=0 353234 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE 353328 Button changed: bRef=0, Joy=1, Btn=5, Released #3 497797 Button changed: bRef=0, Joy=1, Btn=9, Pressed 497797 [Buttons] 1=R1,9,Cx32000BC0,x3FFF0100 497797 Repeating flag set: bRef=0, Joy=1, Btn=9 (RepeatDelayCtr=1) 497797 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0BC0, Param=x3FFF0100 497969 Button held, flags=X05, repeat set: bRef=0, Joy=1, Btn=9, (RepeatOk sets 2) 498250 [Buttons] 1=R1,9,Cx32000BC0,x3FFF0100 498250 Repeating flag set: bRef=0, Joy=1, Btn=9 (RepeatDelayCtr=11) 498250 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0BC0, Param=x3FFF0100 498250 Button changed: bRef=0, Joy=1, Btn=9, Released 558125 Button changed: bRef=0, Joy=1, Btn=5, Pressed 558125 [Buttons] 3=P1,5,C65570,0 558125 FS Control Sent: Ctrl=65570, Param=0 558125 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE 558266 Button changed: bRef=0, Joy=1, Btn=5, Released This one: 1=R1,9,Cx32000BC0,x3FFF0100 is "Offset SWord Increment", with 0BC0 which is the Elevator Trim control. (Why are you assigning a button for this instead of using the normal Fs control for trim? Is it that you want a bigger or smaller effect?). That wouldn't be so odd if it wasn't that it is always associated with this button being used: 3=P1,5,C65570,0 which is your Gear operation. Could your device (joy = 1) be playing up and sending button presses by itself? Can happen when they get faulty. Or maybe the Gear assignmnet button fires incidentally when you usae the trim button -- but didn't you say it happens hands off? Don't know about your brakes. There's no brake use in the log at all after the start where you toggle Parking brake and "Antiskid brakes" which is somethnig i don't know.. You do have these at the end: 1377656 *** EVENT: Cntrl= 66313 (0x00010309), Param= 0 (0x00000000) TOGGLE_ENGINE1_FAILURE 1377656 *** EVENT: Cntrl= 66314 (0x0001030a), Param= 0 (0x00000000) TOGGLE_ENGINE2_FAILURE but no FSUIPC assigned button or key press did that. Pete

You could tell if it was from AIS by logging it's commands sent to FSUIPC. It's probably using offset 2900 to control and delete aircraft (if indeed it is deleting). You'd need to Monitor that offset. Please refer to the Offsets list document installed for you with FSUIPC. Just search for 2900. It'll be on page 32 or thereabouts. You'll see it is 3 DWORD (32-bit) values, so monitor 2900 as S32 2904 as S32 2908 as S32 That will log slews, movements, and deletions if AISeparation is doing them all through FSUIPC. You'd need to search for 2904=65535, the deletion code, to see what it is deleting. Pease don't ask me to analyse your logs. I really do think you are spending all this time on that program needlessly. Why don't you try AIflow? Pete

Well evidently something is sending FSX some command, though how landing gear and views are related is a bit mysterious. Two things to try: firstyou say: That really isn't good enough. If you are using FSUIPC for assignments you need to DISABLE controllers, each one (I seem to remember in FSX you had to select controllers separately). It then doesn't matter if there are any assignments, and it prevents FSX from automatically making assignments on a reload, or after a Windows update, or whenever it things there's a new or changed device connected. Second, if after you do that you still get that strange thing happening, use FSUIPC's event logging (not the axes). Best to then stop the session and close FSX immediately the events occur, then the log entries near the end will show what commands were responsible. unfortunately, though, there's no way to trace back). You could also enable button and key logging. That will make the log a lot bigger i expect, so hope that the strange events occur early in the session. With that logging you might see what is triggering it. maybe an unstable button or USB connection. Pete