John Dowson

MSFS only provides events/controls for 4 engines, and FSUIPC only has in-built support for up to 4 engines, and the offsets only hold the simvars (A-type variables) for 4 engines. How are you doing this - using offsets? The GENERAL ENG THROTTLE LEVER POSITION simvar is currently held in offset 0x38A8 - engine/index 4 0x3968 - engine/index 3 0x3A28 - engine/index 2 0x3AE8 - engine/index 1 with mixture and prop lever positions held in adjacent offsets (see the offset status document). You can add this simvar with indices 5 & 6 (for engines 5 and 6) to offsets designated as 'free for general use' using the facilities provided - see the section Adding Simulator variables (simvars) to FSUIPC offsets in the Advanced User guide for details. However, the SDK documentation does say (see https://docs.flightsimulator.com/html/Programming_Tools/SimVars/Aircraft_SimVars/Aircraft_Engine_Variables.htm#note😞 so maybe this isn't possible... You can try this, and you will see an error in the log if the simvar with indices 5 and 6 are not available, although I suspect that this is a documentation error. Alternatively, you could define your own preset to update these simvars, and then assign your axis to the preset. For example, to define your own preset to control all 6 engines on one axis, add the following line to your myevents.txt file (create this file in your FSUIPC7 installation folder if it doesn't exist): Six Engine Throttle#$Param 16383 + 32767.0 / (>A:GENERAL ENG THROTTLE LEVER POSITION:1, percent over 100) $Param 16383 + 32767.0 / (>A:GENERAL ENG THROTTLE LEVER POSITION:2, percent over 100) $Param 16383 + 32767.0 / (>A:GENERAL ENG THROTTLE LEVER POSITION:3, percent over 100) $Param 16383 + 32767.0 / (>A:GENERAL ENG THROTTLE LEVER POSITION:4, percent over 100) $Param 16383 + 32767.0 / (>A:GENERAL ENG THROTTLE LEVER POSITION:5, percent over 100) $Param 16383 + 32767.0 / (>A:GENERAL ENG THROTTLE LEVER POSITION:6, percent over 100) (assuming axis value goes from -16383 to +16282) Then, in the axis assignment panel, move your axis lever and check Select for Preset and Send to FS as normal axis, and then select the preset Six Engine Throttle from the drop-down. However, I have just tried this and it doesn't seem to work...it functions correctly if you reduce the code to control one throttle, but not when trying to control two or more... not sure why this is at the moment. I will look into this further and get back to you. John

Hi Bob, So this is the same laptop that you use for WideClient with MSFS as you do for WideClient with P3D? If so, this is very strange as WideClient is the same (obviously), and the WideServer element in FSUIPC5/6 is the same as that in FSUIPC7. I will look into your crash logs and WideClient log, but for now could you change to Log=Yes in the [User] section of your WideClient.ini and show me the log file generated with this after a CTD, as well as the corresponding windows event. The log file will be large and need compressing/zipping before attaching. This should hopefully show the last things being written before the crash. Try a few times to see if this is consistent before posting the log. if this doesn't reveal anything, we you can also try with Log=All, and Log=DebugAll Thanks, John

uSER GUIDE, PAGE 22 (bottom of page 21...) section Explained in the User guide, but just set AutoAssignLetters=Yes in the [JoyNames] section of your FSUIPC6.ini file. John

Of course not - that makes no sense. You can assign a key press or button to an axis control, but you need to provide the axis value which would be fixed. If you wanted to assign a key or button to increment or decrement an axis value by a defined amount, you would normally use an offset that holds the axis value and use the offset inc/dec controls to do this.

What device is this lever/button/switch attached to? Are any buttons/switches/axes on this device recognised? As I have already said (when you asked this question in another post), please attach your FSUIPC7.log and FSUIPC7.ini files. Why? If installing the Efis Control panel software caused this issue, why not try uninstalling that first to see if that solves the issue....

Well, at least you found the correct log file this time, but the log file stops after 57 seconds and was attached when FSUIPC6 was still running. Also no GPS data was sent: I though you were receiving the GPS data, but obviously nothing was sent in the 57 seconds of this short run. Can you please try and generate a log file that shows your issue,, i.e. data at 5hz instead of 10hz and track hanging. I need to see the FSUIPC6.log file from when this occcurs, and please exit FSUIPC before attaching log files. Also, just stick to sending PASHR strings for these tests. No, additional logging would not do this. try removing it - do you get the same issue?

But are the keys that this device is sending recognised by FSUIPC in the key assignment panel, either with or without using the keyboard global hook? As I have said, keyboard devices are NOT recognised as hid devices, but the keys should be recognised. Not sure why you attached that...I have already advised what to try for this to determine what the issue is... John

Please read the text where the license is available: John

Then please raise another topic. This topic is for '"Assignments" doesn't show on FSUIPC7' which is solved. It is not your personal support thread. Please raise separate issues if you have problems, and when you do this please also attach the files I need to see to understand your issue, which is usually the FSUIPC7.log and FSUIPC7.ini files. John

Are you using the JoyLetters facility? If not, you should activate that - this prevents issues when joyids change - see the documentation for details. If you are not using this facility, which i guess is the case if you are having this issue, then please attach your FSUIPC ini and log files and I will take a look. You can try changing them in the ini and FSUIPC will attempt to change them in the registry, but this doesn't always work. If you try this, please take a backup of your ini first. Any issues, please show me/attach your .log and .ini files. John

I can't really help with CTDs - check the Asobo forums for this. I can tell you that it won't be related to FSUIPC as that is running as a separate application. I also experience the occasional CTD for no apparent reason. I tend to get 2 or 3 in the same day or two, and then they disappear for a few weeks, and I have no idea what causes these either. A good place to start then - check the Asobo forums for CTD issues associated with RAM.... Good luck! Cheers, John

Would it be worth testing with one of those other com ports that you know are working? And switch the working com device on that port to com16 and see if that continues to work there...I think that would be a useful test to try... John

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.