John Dowson

👍

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

What do you mean by 'unable to press any button'? Are these physical or virtual buttons? If the former, than what has this got to do with the mouse, and if the latter then you will be using the mouse to click the button. So I don't understand this. The issue with focus is with key assignments. MSFS needs to have the (keyboard input) focus for it to receive key presses. If the focus is elsewhere, you could try adding SetForegroundOnKeySend=Yes to the [General] section of your FSUIPC7.ini if this is the issue. You can aslo try with KeyboardFocus=Yes (not sure what the difference is). Note also that there is a specific FSUIPC-added control called "key focus restore" (number 1125), as listed later in the Added controls list. Please see the Advanced User guide for a details on these parameters. Otherwise, could you please clarify what the issue actually is. John

If Loaded PCFhid64.dll does not show in your log, then the dll is either not in the correct location, or you are using an older version that is not supported by FSUIPC7. I have attached the latest version, just in case: PFChid64.dll However, as I keep saying, if your device is recognosed (you can assign to buttons on this device, so it is recognised), then you do not need it. Again, this implies you don't need the PFC/FSUIPC driver dll. Then this would imply that something else is needed from PFC for the yoke motion, if their own test program doesn't even recognise it.... What console buttons? Is this on the same device, or a different device or the same one? No log or ini files attached. Have you assigned to any macros? Do you have any in your installation folder? I do not understand this without seeing those files... Ok. Macros have nothing to do with devuce/controller recognition, so will not be related to your yoke recognition issue. John

Ok, so you are using custom controls as opposed to the Rotor Brake control. I will check the use of custom controls via offset 0x3110 when I get time - most probably next week, and report back. The Java CDU looks good! Is that available anywhere to download and try?

Then the custom control number and the Rotor Brake parameter will be the same. Are you writing the custom control number or the Rotor Brake control number (together with the parameter) to offset 0x3110/0x3114? As the Rotor Brake control us a standard event, it should work the same in MSFS as in P3D. I haven't tested/checked writing custom controls to 0x3110 - it is possible that this is no longer working (if they are wrongly determined to be presets). I can/will check this, but it will take me a few days before I can get around to this (next week sometime). If you could let me know what controls you are writing to that offset that aren't working (i.e. control number + parameter) that would help. You need to use what works! Some aircraft make use of hvars, others not. PMDG aircraft mainly use custom controls. However, rather than using hvars or lvars directly, it is far easier to use presets. Please see the MobiFlight HubHop resource (https://hubhop.mobiflight.com/presets/) which is a community effort led by MobiFlight that provides presets for many aircraft. You can also check the code used by the preset, which can contain use lvars, hvars & controls/events (as well as other variable types!). John

Those offsets are for sending controls/events and the aircraft loaded does not make any difference to there use - writing to them just sed the control/event to the FS. The events will be sent, but maybe those events are no longer working in the MSFS version. What events are you sending? Maybe you need to use a preset in the MSFS version instead? You can also send presets using offset 0x3110, but it is easier and recommended to use offset 0x7C50 for this, as you can use the fixed preset name in this offset rather than calculating the control number for the preset, which may also change when the preset list is updated (events.txt file). By the way, Pete retired several years ago, although he still helps out occasionally. John

The PFC menu will only be added once you have an aircraft loaded and ready-to-fly, at the time the connection check dialog is displayed. If you check your FSUIPC7.log file, you will also see the following message when it is loaded (i.e. when FSUIPC7 is started, not when the menu entry is added): 1016 Loaded PFCcom64.DLL okay! However, if your device is recognised without this, then you (obviously) don't need it. If the switches on the yoke are recognised, then so should the yoke itself. Do you see anything registered at all in the axis assignment dialog when you move the yoke? Note that if you see another axis, registered, you can click the Ignore button to ignore that for the rest of the time the axis assignment dialog window is open. If you still have issues, please attach your FSUIPC7.ini and FSUIPC7.log files. John

Hi Peter, This implies that you re-installed FSUIPC7 into a different folder than your original installation. All your FSUIPC7 settings are stored in your FSUIPC7.ini file. If you install in a new location, you have to copy that file across to the new installation folder. Note that FSUIPC7 will create a new FSUIPC7.ini file if there is no such file in the installation folder (and this will be empty, i.e. contain no assignments) when you run it for the first time. This file is not touched by the FSUIPC7 installer, either when you install or uninstall. Not sure what you mean by 'functions' - do you mean presets? If they are not available, then this implies that you have either not installed the WASM module or you have not enabled the WASM. Yes, obviously I would have thought... You can try that, but I really don't understand what you have done. Check if you can find your original FSUIPC7.ini file, the one with your settings, Then re-run the installer and install into that folder. Assuming you mean presets when you say functions, these come from the events.txt file (in your FSUIPC7 installation folder), and the WASM module must be installed and active. No "functions" have been removed... You need to find where your original installation folder was, and either re-install into that folder or copy across any files that you use (FSUIPC7.ini, FSUIPC7.key, *.lua, *.mcro, *.dll) to the new installation location. I really don't understand why you are having so many issues. Re-installation of FSUIPC7 is really very easy - you just download the latest version, unzip the file, run the installer (no need to uninstall first - the installer will prompt for this) and just accept the defaults and click Ok in each window until you get to the registration window, which you can skip. It is designed to be easy....or so I thought... Any further issues, please at least show me/attach your InstallFSUIPC7.log file and a FSUIPC7.log file. John

Please find attached. John FSUIPC7.exe

👍😎

You can certainly do that. You need to assign to one of the following (both may work, or one only, depending on the aircraft) with a parameter of 0: ELEVATOR_TRIM_SET AXIS_ELEV_TRIM_SET AILERON_TRIM_SET AILERON_TRIM_SET_EX1 You can also write to the trim offsets using the control Offset Word Set - see page 33 of the Advanced User guide for details on this as well as other offset controls. John

Most, but maybe not all) presets for the 737-700 will be ok for the 737-800. However, I cannot confirm this as I don't have the 737-800, but the simple way to check this is to compare the header files they provide - if they are the same, the rotot brake parameters and custom control numbers will be the same. And if you find that any are not working as advertised, and they are being correctly applied in the FS, then it will be an issue for PMDG support. Good luck with your project! Cheers, John

No problem. The latest license is always available on the first page/comment in this topic. John

Ok, thanks for the update. John

See the following FAQ entry for using the Rotor Brake control for PMDG aircraft in MSFS: Note also that this method is deprecated (it can still be used without issues - all or most of the PMFG presets use the Rotor Brake method). The preferred (and more powerful) method is to use Custom Controls, as you can use actual parameter values with these, as well as the mouse-code operation parameters. See the following FAQ entry on using Custom Controls: The custom control number for FMS left A is calculated from this entry in the PMDG_NG3_SDK.h file (in your Community\pmdg-aircraft-737\Documentation\SDK folder) : #define EVT_CDU_L_A (THIRD_PARTY_EVENT_ID_MIN + 573) and so the custom control number would be 70205. So, if the Rotor Brake control doesn't work, try the custom control instead. If the Rotor Brake control did work, and the preset using this doesn't, there may ne a problem with your installation somewhere. Check you are using the latest version of FSUIPC, which is 7.3.15. John