John Dowson

Why do you have so many come ports (com1 - com17, minus com2, which is very strange)? You need to determine which com port the device is on - maybe just try changing the COM port in the PFC connection check panel until the radio stack is recognised. And if you disconnect the PFC radio panel, do any of those com ports disappear from the windows device manager? And what makes you think that the device is on com16 or com17, and have you tried both of these? Have you also tried connecting your radio panel to com1? If the device fails to be recognised then I suspect that it is a problem with either your serial PCIe card, the cable or the device itself - or possibly your windows configuration. I cannot reallu help you with any of these issues.

If it is not listed in the offset status document, it has not been added to an offset. There are many simvars, and only a subset of these are added to FSUIPC offsets. If there is a simvar that you want to use in an FSUIPC offset that has nor been added, then you can add this simvar to a spare / 'free for general use' offset using the facilities described in the Advanced User guide - Adding Simulator variables (simvars) to FSUIPC offsets on page 34. That is not added, but should be straightforward to add for both reading and writing/updating.

Cam you please always exit P3d / FSUIPC before attaching logs. And you attached your FSUIPC6.log twice, and still no PFCcom64.log file - please show me /attach that. The PFC driver is trying to use com port 16 - are you sure that is the one that the radio stack is connected to? Did you try with port 17? The log you attached also shows nothing happening for 6 hours, and then a device reconnection: and then another 2 hours later....why are you leaving P3D/FSUIPC running so long just to test the connection? What log options do you have set? Can you please clear them all, and show me the log file generated with no logging options. Then set logging for COM port operations only, and generate a second file and show me that. You can zip/compress it if its too large. But I don't think the logs will reveal much if the device isn't being seen, and I am not sure what else to advise,,,

I have made some performance tests and can confirm that lua scripts in FSUIPC7 run around 8 times slower in FSUIPC7 compared to FSUIPC6. Noy sure why at the moment, I will investigate and let you know if I find anything.

To do this you use the Logic library, e.g bit7 = logic.And(value, 0x80) -- bit 7 = 2^7 = 128 = 0x80 However, looking at offset 64D6, it is an array of 16 bytes/booleans, not bits, so you do not need bitwise logic. Just set your event on byte 7, i.e. 0x64D6 + 7 = 0x64DD, so event.offset(0x64DD, "UB", "NAME") John

I don't think your issue is the same - the OPs issue looked to be a weather issue, although it isn't clear. So, FSX crashes when you open FSUIPC4, but only when the PMDG 737 is loaded? Does it crash as soon as you open FSUIPC4, when you go to the Axes assignment tab, or at what point? Could you please show me your FSUIPC4.ini and FSUIPC4.log files, and also check the windows Event viewer to see if any crash events are reported and if so please show them to me as well. John

Yes, you have to manually add this - the default is to show the splash screen, and there is no UI control to disable/enable this. The splash screen is generally necessary as you do not know if FSUIPC has been started/is running without the splash screen, as it goes to the system tray once started. This confuses new users without the splash screen. IMHO, I do not know why you would want to disable the splash - I only added as a user request - possibly yours... John

Very strange then... Ok, thanks, Is WideClient connected when you get this issue? The logs will tell me, and should also show where this failed - if the key press was sent to WideClient, and if it was received. John

The log you attached ends after 20 seconds and was attached when FSUIPC6 was either still running or had crashed. Please attach a full log file (i.e. only attached once P3D / FSUIPC has exuted), and also your PFCcom64.log file. Yes, I can see that from the log file. Later: ...and I still advise you to update your Explorer view settings so you can see the extensions of the files, as previously advised...in the screenshot above, you have two files shown as 'PFCcom64' - one will be the .ini, the other the .log, but you cannot tell which is which with your current settings.

Button assignments are greyed-out when there has been a condition added to an assignment or when the assignment is overloaded (i.e. multiple assignments to the same button). if this was the case, there would be no Assignments menu option, As Al says, it would be helpful to know what has changed, if anything. Could you please show me/attach your FSUIPC7.ini and FSUI{C7.log files, the latter generated with logging for Buttons & Keys and Events activated. Just load the aircraft, wait a minute or so (until everything loaded and started), and then press your PTT button, and then exit. Also attach your WideServer.log (from the FS PC), and WideClient.log and WideClient.ini files (from the client PC). John

What do you mean by 'set in addons'? I don't have any PFC devices so I cannot really advise much more than what is said in the PFC user guide, Please read that carefully and follow the instructions there. Also check the PFC log file (which i asked you to post if you had any further issues....). Did you re-install FSUIPC6 into a non-windows protected folder, as advised? You do not seem to be responding to my posts...

You have installed FSUIPC under your Windows Documents folder - this can cause issues to windows restrictions on this folder. Please uninstall FSUIPC6 and re-install in a non-windows protected folder (e.g. C:\FSUIPC6 or C:\P3D Add-ons\FSUIPC6. When you install the PFC driver, only install the one you need, i.e. the PFCcom64.dll. You do not need the other dlls. Also, please change your Windows Explorer settings and uncheck the option to hide file extensions of known file types. After you have done this, if you still get issues please attach your FSUIPC6.log and PFCcom64.log files. Please first also see the provided PFC DLL user guide in how to set up the connection correctly.

There is a mismatch between the ini and log you posted: the ini file is from version 6.2.0d: UpdatedByVersion=6200d but the log file from 6.2.0c and from 6th June: ********* FSUIPC6, Version 6.2.0c (5th June 2023) by Pete & John Dowson ******** ... 16 System time = 06/06/2023 10:24:04 I do not understand this or why your log and ini files do not match, and why that log file is so old. Are you sure you are not running FSUIPC6 from another folder? You can check with the Open Folder button in FSUIPC's logging tab.

You need to check/select 'Send to FS as normal axis' (left-hand side) as well as 'Select for Preset' (top-right). John

Try the the following MF presets:

Sorry - its a serial device, so you don't need the hid driver. Are you using the 64-bit drivers? Check that you are using the latest driver - download and re-install from fsuipc.com.

You should be able to use the old ini file, although it may need some manual changes. This is straightforward if using the JoyLetters facility, but can be more complicated if not. Please attach your FSUIPC6.ini and FSUIPC6.log files and I will take a look.

Is your device a serial/com or hid/usb device? You will only need one driver, not both. And you need the 64-bit drivers, not the 32-bit ones. And you should not place the FSUIPC 6.1.9 sll anywhere - you should run the installer to install FSUIPC6, and then install the 64-bit com OR hid PFC driver, The set-up will be exactly the same with P3Dv5 as it was with P3Dv4.

From the README.txt document (included in the zip file you downloaded) - I will update this as documentation is now available (and has been for a while): I have my hat assigned to send the default keys for view control that are assigned in MSFS. See the following article for a description of the view controls and default key assignments: https://flightsimulator.zendesk.com/hc/en-us/articles/360016003159-Camera-Overview John

When you assign to an axis, the axis value is sent to the control/event that it is assigned to. It doesn't really make much sense assigning an axis to a button, unless this is for a specific purpose (e.g. centering the axis). Such controls (up/down/left/right) are best assigned to a hat switch. If you have a spare hat switch, you can use that. Otherwise, it may be possible to overload your view control hat switch to send these controls when another button/switch is pressed, and to control the view when not. This is called a conditional assignment and is described in the Advanced User guide. But what makes you think these are axes controls? Up/Down/left/right are not axes controls, and if they are assigned to keys then they are certainly not axes controls.... If the controls are on a button, they are not axes controls. What controls do you see logged when you press these? You can just assign your buttons to the same controls. This also doesn't make much sense to me. How are you expecting to control two directions (left/right and up/down) on one axis? And this also sounds like you want to assign non-axis controls (up/down/left/right) to an axis, which is the opposite of the title of this post. Normally there are corresponding inc/dec controls for each axis control. If not using the axis controls, you would assign to two buttons, one to increment the axis value and another to decrement. What are the controls logged, if any, when you change the TDC cursor slew in the VC?

Ok. One other thing you can try to aid you in this is to keep the FSUIPC logging console window open, and monitor the events shown around the time your throttle 2 starts to fail. Some people also have issues with PMDG aircraft throttle assignments when calibrated in FSUIPC due to priority issues. I don't think this is your issue, as your problem only seems to be with throttle 2, which is strange. But you could try switching the assignments to Send to FS as normal axis, and making sure that no calibration is applied in FSUIPC. Regards, John

Have you tried without FSHUD running, and without pausing for decent? What other software/utilities/add-ons do you have running? Maybe try without anything running other than FSUIPC, and then add other utilities you may use back one by one. Also, check any throttle calibration utilities in the aircraft itself - does it have throttle calibration in the EFB? If so, check that. FSUIPC does not know or change anything in different flight stages.

You assign an axis to a preset on the left hand side of the assignments panel. not the right hand side, which is used for sending controls when entering and leaving specific axes ranges. You have assigned to send this preset once when the axis value goes to 0. Delete that assignment and assign the axis (left-hand side) not the axis range (right-hand side).

What do you mean by "Throttle 2"? For the 747, you have the following throttle assignment on axes: Looks like these are assigned to the quadrant attached to your yoke, and as you have an exes assigned to both throttle2 and throttle 3. Are you saying that this assignment continues to work for throttle 3 but not for throttle 2? When this occurs, if you go into the axes assignment tab. do you see these assignments when you move the throttle? You also have the following throttle decrement control assigned to buttons: Here you have a repeat throttle 2 decrement assignment on a button on your 2nd throttle quadrant. Also strange as nothing for engines 1 and 4. As you are controlling engines 1 and 4 on one axes, and 2 and 3 on another, I would have thought the decrement controls for 1 and 4 should also be on one button, and for 2 and 3 on another. You have also assigned with 'Direct to FSUIPC calibration' but have not calibrated your throttles. You should always calibrate an axes when assigned in this way. How are you doing this? I see no assignments to reversers. Then it does sound like an issue with your PMDG 747 configuration, I don't understand how this can just affect throttle 2... Try compressing / zipping it.

Just tried again - I clicked Select all then Read, and it seems to be showing data: John