John Dowson

I have no idea, sorry. We don't support x-plane, thats XPUIPC, from a different developer. John

Is this for all devices, or for a specific device? Most of your button assignments seem to be on the T.16000M only, with a few on your Flight Throttle Quadrant. The first thing to check is that you have power management disabled on your hubs, to prevent them from sleeping. Also check that USB2 devices are connected to USB2 ports, as if not this can sometimes cause such issues, and that if you are using external hubs then they are properly powered. This error is quite strange and indicates that your 2-axis 4-button gamepad was not useable when started, although it was acquired for use. You also have duplicate registry entries for that device (ID 4), but that's only a warning so we'll ignore that for now. These errors are strange (but unrelated your issue). I will look into those. Could you also try with the attached version (v6.0.12c), which will be the next release. It has a minor correction in the controller scanning where it will not acquire a device for use if it is not connected:FSUIPC6.dll Your [JoyNames] section is also confusing, as most of your devices have multiple entries with different GUIDs. Make a safe copy of your FSUIPC6.ini, then replace your [JoyNames] section with the following: You have one general button assignment to device 'F' which has now been removed: 1=PF,3,K122,9 -{Key press: shft+F11}- You can change this to 1=PB,3,K122,9 -{Key press: shft+F11}- or remove completely, as you have the same assignment to your T16000: 2=PA,3,K122,9 -{Key press: shft+F11}- John

@cavaricooper So you have a Honeycomb Alpha? Yes, there are known issues with the Alpha and the heading bug increment due to the continually firing buttons/switches, but people are using FSUIPC to get around this, so if using FSUIPC you should be ok. Or do you still have assignments to the alpha in MSFS? If so, maybe remove those. As I said, there are several posts on this topic already (but probably hard to find) - check the FSUIPC7/MSFS sub-forum. John

Yes, but the SimConnect interface used by FSX isn't that different from the P3Dv4/5 SimConnect, so should still apply. Still, post those files with the logging and I'll take a look. Also try moving the throttle with the mouse to see what that logs. And try with a default aircraft - or is it just an issue with the A318/A321? John

Ok. Then I need to see your FSUIPC4.ini, and also an FSUIPC4.log file, with your aircraft loaded, axis logging enabled, and move your throttle through its full range and back again. Is this just a problem with the A318/A321 add-on? Or is it a general problem with the TCA throttle quadrant? If its a problem with the throttle quadrant or airbus interaction, I think you would be better off asking on the Aerosoft forums, as I don't have that device or the Aerosoft Airbuses. I see there is this long ongoing thread over on the aerosoft forums (which I haven't got time to read, sorry!) which may help, I don't know: https://forum.aerosoft.com/index.php?/topic/156444-tca-support-for-the-aerosoft-busses-and-update-schedule/ John

@jorge moreyra Is your issue solved? If so, what was the problem? If not, can you please respond to my previous message. Thanks, John

@Flygard Could you try the attached version please. I have added GEAR CENTER STEER ANGLE only for the time being, at offset 0x0BF8 as a 4 byte float (F32). Its a 'percent over 100' value, so should give values between +1 and -1, although during a quick test I have seen values between -1.35 and + 1.3 and I'm not sure why. If the values where between +1 and -1, I could convert them to an integer in the -16383 to +16383 range (and reduce to a 2-byte int), but as I get values outside of this range I've just left the raw value for now. FSUIPC6.dll John

@B77X I cannot duplicate your issue. However, I have made some minor updates in the following version (to only ask if you want to import the General axes when creating a New profile), so could you try with this version please and let me know how it goes: FSUIPC6.dll

I have seen this but am extremely busy. I will look into it when I have time. However, note that the very same issue was recently reported and solved, I believed. So, as you are in a rush, please try to find the previous post for this issue and see if that helps.

Also, I would advise you to either change AutoAssignLetters=No to AutoAssignLetters=Yes Or to assign your own JoyLetters. This will prevent issues if your joystick ids change - please see the FSUIPC user guide.

Can you explain what you mean by this please. If you move your throttle, do you see the axis in the axis dialog? I presume so, as you do have a throttle axis assignemnt in your a318af profile. Note also that that profile is only assigned to this one aircraft: 1=Airbus A318 British Airways G-EUNA So will only wotk with an exact (substring) match on that string. You probably want to change that to 1=Airbus A318 or even just 1=A318 And if you want the same profile for the A321, you need to add 2=A321 (but you may want to set that up in a separate profile, I don't know). Also, you are using v4.974. This is out-of-date and no longer supported. Please update to 4.975. John P.S. I see you are also using Linda...if you are using Linda for your assignments, then you will need the Linda support forum. Otherwise you should disable this for the time being.

No, as I have no idea what version of FSUIPC you are using or even what FS you are using. Please try and specify your issue in more detail (so that I can reproduce), and preferably with a default aircraft. Also please attach your .log and .ini files if you post again. John

We cannot help if we do not know what your issue is. Please describe your issue, what you have tried, and attach any appropriate files - we at least need to see you FSUIPC4.ini file. John

@Ardriax I don't understand what you posted, and why are you hijacking a problem that doesn't seem to be related to your issue? Can you at least attach your installation log and you FSUIPC4.log file (if there is one), and explain what you mean by 'wont load the fsuipc even in admin mode'. Do you mean that you cannot see FSUIPC in the add-ons menu? Does FSX (or FSX-SE - I don't even know which sim you are using!) run or does it crash? You also seem to be using an old unsupported version of FSUIPC4. Please update to the latest version 4.975 (or 4.975a) before posting again. John

Ok, sorry, you are using 6.0.12b - I checked your log you PM'ed me. I've been playing around trying to get it to crash or delete/remove an axis section and haven't managed to find any issues so far. Could you try again please and if this happens let me know exactly what you did (i.e. did you import the 'general\ axis or not, did you save when asked or not, etc). Thanks, John

I'm slightly confused - aren't you using the 6.0.12 a/b version posted earlier in this thread? If not, please try that one. There is/was a long-standing bug that resulted in the general axis section being cleared in versions prior to 6.0.11. I corrected this in the 6.0.11 release (or thought I had), but this "correction" resulted in axes being lost in other situations, so I corrected for this in the 6.0.12a (or b) release posted earlier. However, I believe the original problem still exists in this version which I will investigate when I have time, and will release the final fix for this in the official 6.0.12 release. This is getting even more confusing now with @B77X saying that P3D is now crashing but with no crash event. Could you please let me know which version you are using, and if using 6.0.11 then please update to 6.0.12a or b. I have quite a back-log of support requests to get through, so please be patient. John

Not 100% sure what you mean, but the FS version can be read from offset 0x3124, with values: FSX: 1 to 4 for the RTM, SP1, SP2 and Acc versions, respectively FSX-SE: 101 to 109 (etc) for builds 62607 to 62615 (etc) P3Dv1: 10 to 14 for versions 1.0 to 1.4 (but versions before 1.4 not supported). P3Dv2: 20 to 25 for versions 2.0 to 2.5 P3Dv3: 30 to 32 (etc) for versions 3.0 to 3.2 (etc) P3Dv4: 40 to 45 (etc) for versions 4.0 to 4.5 (etc) P3Dv5: 50 for version 5.0 MSFS: 110 John

FSUIPC7 is for MSFS ONLY, as stated on the sales page. For FSX and FSX-SE, you need FSUIPC4. You can download and try each version (as unregistered) from www.fsuipc.com.

Ok, but you wouldn't believe the number of posts I have had where this was not done. Is there an FSUIPC7.key file in your FSUIPC7 installation folder (do NOT post this if its there!)? Can you attach attach your FSUIPC7.log file please so I can see that. Also let me know your order number and I'll check your registration details here. John

They go in your FSUIPC installation folder. Thats up to you. You can assign them to a button/switch/key press, or have them started automatically. For that, see the FSUIPC7 for Advanced Users.pdf (located in your FSUIPC7 documents folder), section Automatic running of Macros and Lua plugins, P35. John

That FAQ entry needs updating. It should go in the same location as your MSFS UserCfg.opt file, and where your FLT files are saved - look for a line like 'FLT path =' or 'FLT UNC path =' in your FSUIPC7.log file. If you have an MS Store install, it should be something like: C:\Users\<username>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\ or C:\Users\<username>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\ John

There is the limit of 999 commands per macro file, and 127 macro files. Thats not what I asked: Do you see them in your FSUIPC6.in file under the [MacroFiles] section? Please attach your FSUIPC6.ini file so I can take a look, as well as a listing of the contents of your installation folder. John

It does! There was a problem prior to 6.0.11 where FSUIPC would remove the general axis section in certain situations. I correct this, or thought I had, but the correction caused axis to be removed in another situation (I hadn't fully tested!), so I changed this in the 6.0.11b version I released earlier in this topic. There does still seem to be an issue which I am looking into to try and reproduce. John

Note that the latest version of the MSFS SDK has new controls for use with 8.33KHz frequency spacing. I have added these to the version in the version posted in the following topic, and have also updated offsets 05C4,05C8, 05CC & 05D0 to use these new controls: John

Note that the key string for this is actually ENGINE_MODE_IGN_SET. i have added these new controls/events, as well as a lot of other new ones, to the following version if you would like to try: FSUIPC7.exe These are the ids of the new events added (the vast majority of the string names match the key id strings with the 'KEY_' part removed): Note the above list also contains controls for 8.33 channel spacing, so I have also update offsets 0x05C4 - 0x05D0 to use these, so hopefully these will now work, although I haven't had a chance to test yet. John