John Dowson

That makes sense, and that will trigger the event LANDING_LIGHTS_TOGGLE - this event should work in most default aircraft (but maybe not all), and some add-ons but certainly not all of them. It certainly works in the C172, as does writing 0x3F7 to 0x0D0C, which results in: taxi lights off, beacon, landing, nav and strobe lights on (as well as others, which the C172 doesn't actually have) . 0x3F7 = 001111110111 so that is as expected (bit 3 is 0 so Taxi off). John

Yes, thanks - that explains it. I can maybe check what offsets are being used (from the PFC log) and can see if they are working for the aircraft being used if @jimbooo could attach an FSUIPC7.log file, together with a PFChid.log file, both generated with the logging changes that you have already suggested. John

It shouldn't make a difference if assigning in FSUIPC with 'Send direct to FSUIPC calibration', but will if assigned in MSFS or in FSUIPC with 'Send to FS as normal axis' (depending on the axis controlled you have assigned to). However, as I said, your ini file shows no assignments. Try assigning your axis in FSUIPC7 as well,. John

Yes there are: 76141: Macros not found: "C:\FSUIPC7\PFC.mcro" The OP attached a file named PFC.MCRO.txt - he needs to remove the .txt extension - but is it really an issue if this empty macro file cannot be ran? What offsets are being used, and for what- (where is this info? The PFChid64.log shows some macro's being called in PFC.mcro (which is empty!): 76235: Full macroname for decoded switch = "PFC:LandingLight", mask = X00000000 ... 76375: Full macroname for decoded switch = "PFC:Obs1", mask = X00000000 ... 76391: Full macroname for decoded switch = "PFC:CRSencode", mask = X00000000 etc I am not sure what those are and why they don't have an error if the PFC.mcro can't be found...maybe Pete could explain? That is a good idea - and please attach your FSUIPC7.log file as well. John

As well as having no axes assignments in FSUIPC7, you also have the checkbox for Exclude THROTTLEn_SET checked (page 3 of calibration screen) - uncheck that and try again. John

The log file you attached shows that FSUIPC7 was still running when you attached it, and only contains 13 seconds worth of log information. Can you please leave FSUIPC7 running a little longer (a minute or so), and make sure that you have exited FSUIPC7 before attaching the log file. You also have an ipcInit.lua that is ran on startup - what is in this? Maybe try disabling that (i.e. rename it to ipcInit.lua.off) to see if that is causing your issue. John

No. Yes - the X just closes the window and is the same as File ->Close. You can also press Alt followed by F followed by x to exit FSUIPC7 - the keyboard shortcut. Why don't you just have MSFS auto-start FSUIPC7? Yes - use the keyboard shortcut. If FSUIPC is iconised, you can also press Alt+F (together) first to show the main window. John

Your registration details will be available in your SimMarket account. Note that f you have a license for FSUIPC4 (which is compatible with FSX and FSX-SE), this will not be valid for FSUIPC7 (which is compatible with MSFS2020). John

👍

Not really...to confirm: In the axis assignment tab, you can see the joystick and axis letters detected there, and the In / Out numbers changing. You then assign to Throttle1 with Send direct to FSUIPC Calibration, and on page 3 of the calibration tab, you cannot see the In / Out numbers changing there? If that is the case, I do not understand as the axis input values are coming from the same place... Can you try this with just running FSUIPC7 without MSFS and see if you get the same behavior? Are you assigning using profiles for both the assignments and/or calibration? Can you attach your FSUIPC7.ini file as well please.

What version of FSUIPC7 are you using? Calibration of axes not assigned in FSUIPC7 (or assign with 'Send to FS as normal axis') was removed in 7.3.9 due to issues introduced in SU10, but was re-enabled in 7.3.13. The latest version is 7.3.15. If that is not your issue, can you please explain what you mean by 'cannot be calibrated within FSUIPC.7', and please let me know how that is assigned, and attach your FSUIPC7.ini file. John

This is not correct...they are working, I was using the wrong parameters. I tested using the following two simple lua scripts for prev/next page on the left CDU: Prev page: ipc.writeUD(0x3114, 0x20000000) ipc.writeUD(0x3110, 70191) Next page: ipc.writeUD(0x3114, 0x20000000) ipc.writeUD(0x3110, 70192) where #define MOUSE_FLAG_LEFTSINGLE 0x20000000 So I am not sure what your issue is... You could try setting a custom log value in FSUIPC7 of x800 to check the events are being transmitted. You should see lines such as the following logged: 6625734 ExSendEvent(70191, 536870912, 0) 6625734 ... evnum mask=0, preval=0 6625734 ... not intercepted or in options 6625734 Transmitting "????" 70191 [0x1122F], Param 536870912, Priority 1 (Axes flag = 0) 6626313 ExSendEvent(70192, 536870912, 0) 6626313 ... evnum mask=0, preval=0 6626313 ... not intercepted or in options 6626313 Transmitting "????" 70192 [0x11230], Param 536870912, Priority 1 (Axes flag = 0) John

Sorry - forget this, they are working...I was using the wrong parameters.... John

Still no issue here when using the A310 Enhanced add-on....

👍

FSUIPC7 shouldn't do anything unless you tell it to... If you don't have your throttle assigned, it may still be calibrated, which would interfere. Try removing the calibration. If you are using profiles (which you should be doing...), make sure that your calibration is profile specific for the DC-3. Then remove any throttle calibration for the DC-3 profile using the Reset button - do this for Throttle as well as Throttle1/2/3/4. If you still get issues, please show me/attach your FSUIPC7.ini file. John

@Alpin-Flier Are the PMDG custom controls still working ok for you? They seem to be broken again here and I am not sure why, although the Rotor Brake method is still working. If it is working for you, could you let me know what version of the PMFG 737 and what version of FSUIPC7 you are currently using please - I am trying to determine if this is an issue with FSUIPC7, PMDG or MSFS.... Thanks, John

I have just checked the use of Custom Control numbers with the PMDG 737 in MSFS and they no longer seem to be working. No idea why, or if this is an issue with PMDG, FSUIPC7 or MSFS. Nothing has change in FSUIPC7 in this area for a while so I suspect PMDG or MSFS... I will look into this further, but I am also surprised that there have not been a lot more support requests om this if the PMDG custom controls are no longer working... I have checked the Rotor Brake method of control and this is still working with MSFS/FSUIPC7. You could switch to using these for MSFS instead, e,g, for #define EVT_CDU_L_PREV_PAGE (THIRD_PARTY_EVENT_ID_MIN + 559) #define EVT_CDU_L_NEXT_PAGE (THIRD_PARTY_EVENT_ID_MIN + 560) you would use control number 66587 (Rotor Brake) with a parameter of 55901 for PREV_PAGE and 56001 for NEXT_PAGE. For details on calculating the parameter for the Rotor Brake control, see John

You posted in the Announcements sub-forum where it explicitly states NOT for support requests. I have moved your post to the FSUIPC7 support sub=forum, where it belongs. Please tale care to post in the correct place for support. When editing the FSUIPC7.ini, you should do this either with FSUIPC7 not running, ir if it is running then open the button assignments window before editing, and once you have saved your changes, click the Reload all buttons button. If you don't do this, the original settings will be re-written. John

Ok - I will try with this installed to see if that makes a difference...

Can you please show me your InstallFSUIPC7.log file. If the installer determines that you have a steam installation of MSFS, it is because it has found the following file: AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt Try removing or renaming that file, then uninstall FSUIPC7 either by running the uninstaller (located in the FSUIPC7 installation folder) or from the windows app management panel, then install again. If you still get issues, please attach your installation log. John

I don't think it means anything - just additional/Extra controls. Both the standard and the _EX1 controls work for some aircraft, but for others only one may work.

Create a text file, rename it to PFC.MCRO, open it in an editor an add the line: [Macros]

Yes - and I showed you, e.g. There you have throttle assigned to Z axis on device C, as well as on X, Y axis (for separate engines) on device D. Please re-read my original reply, and, as I said, once you have fixed that, and have checked/cleared your MSFS assignments, if you still get issues I need to see your .ini and .log files, with appropriate logging activated. John

You have your throttle assigned to two controllers: This is always a bad idea. Remove one of those assignments . Also in some profiles: Also check the throttle isn't also assigned in MSFS. Any further issues, attach your FSUIPC7.log file, generated with logging for Axes Controls activated, together with your updated FSUIPC7.ini file. John