John Dowson

I don't see how this can be.... Loading the default FBW I see the following aircraft name: 134000 Aircraft="Airbus A320neo FlyByWire Xmas" This will load the A320NX profile, NOT the A320 profile. If you think the wrong profile is being loaded, can you show me the Aircraft title, as logged by FSUIPC. When you load an aircraft with a new livery that is not currently assigned to any profile, it is up to the user to select the profile for the new livery (or create a new one) - this is not done automatically. Therefore it must have been the user' choice to assign the 'British Airways OperatorLand468 FBW' to the A320 profile, and not the A320NX profile. For this, then you need: That is a possibility. However, I am concerned if this will be possible with all aircraft due to the encryption sometimes used with deluxe and add-on aircraft. I will have a think about this and maybe look into this. A main issue changing to this would also be that it would invalidate all current profile assignments. I guess I could handle this by determining the FSUIPC version and re-writing the profile sections, but would be a bit of a pain. Let me think about this. No, nothing has changed in this area. Yes - hvar file names must also match in the same way. However, If I do decide to change the way profiles are matched, this would not change the way hvar files are matched. The hvar files are loaded by the WASM which (currently) has no knowledge of the aircraft.cfg file, its location or access to FSUIPC offset information. I could also look into this but would be separate from the profile issue. I also have other changes planned which I think are far more useful to the general community, so I cannot give you any timescales when I will look into this at the moment. John

I have never heard of such behavior and have no idea what could cause this...FSUIPC is not actually doing anything when the UI is opened - it is just waiting for mouse input events from windows. Have you tried re-installing the P3D client? Can't think of anything else at the moment...

But did it detect anything when you press the buttons on the device?

As you have already ran the first one, just run the 2nd one, with your logitech jopystick and rudder pedals disconnected, then reboot and reconnect. then run FSUIPC7 and exit, and show me the 3 files again. Sorry about your issues with MSFS, but I can't help with that. Try the Asobo forums for installation issues.

I haven't tried this but the result depends in which level the MSFS applies the sensitivity curves. From what you say, it looks like the values send from FSUIPC go at a higher level and bypass the MSFS calibration. John

No, sorry, as this is just a message from ATC. There is no 'status' of the aircraft for this. John

Yes. FSUIPC starts its button enumeration from 0, not 1. John

That is usually due to the axis being flagged as a digital (on/off) axis in the registry. See this postL John

It is the delta value - inly value changes greater or equal to this are sent to the FS. Yes. John

I can't see how this can be... please double-check the file extension (as well as location), as it can also have another extension (usually .txt) that is hidden when you look at it in windows explorer. If that isn't the issue, please show me that file. John

That is a macro using an lvar. Well, sorry for the delay as I was also on holiday from the 12th until today/tomorrow. So the throttle is working but the throttle n the UI isn't moving? So, how can you tell that the throttle is working - do you hear it and does the aircraft accelerate? Anyway, I think this is a common issue with the Aerosoft Airbus, although I can't remember the solution... There are various throttle axis controls - try switching to using a different one maybe. Also check the aerosoft forums for this: https://forum.aerosoft.com/index.php?/forum/551-throttle-issues-with-fsuipc/ - you will most probably find something relevant there - please report back id you do.

If you are using the trial license, then this does NOT validate in the installer, as mentioned in the initial post: If you are not using the trial license, you have posted in the wrong topic... And for registration issues, please see the provided documentation. If you have re-installed windows, you most probably need to install the latest VC++ combined redistributable packages. See the README,txt for details (or the MANY other posts on the same issue). John

Unfortunately not, as these are internal controls only and are not exposed via SimConnect. Generally, for such events (non-axis), you can assign to a keypress in MSFS, and then assign your button to that keypress, but you cannot do this with axis controls. If useful, you could try assigning to the non-axis controls: Increase/Decrease Condition Lever Increase/Decrease Condition Lever 1/2/3/4 Condition Lever Low Idle Condition Lever High Idle Condition Lever Cut Off Condition Lever 1/2/3/4 Low Idle Condition Lever 1/2/3/4 High Idle Condition Lever 1/2/3/4 Cut Off Also, check to see if they are actually working for the aircraft that you are using. Last time I looked at these, back in November, I didn't have much success with these. John

Hi Carlos, sorry for the delay - I am back now... Question: did you run the second .reg script I provided (on the 5th January)? There is still a conflict between your Logitech G13 Joystick and your rudder pedals that this should (hopefully) solve. The registry changes are to clean-up your devices and in no way would this cause any changes to MSFS (so re-installing won't help), and they should also not cause MSFS to CTD. Are you still getting these? Are you using empty profiles for your devices in MSFS (recommended if assigning in FSUIPC), or do you have assignments to your devices in MSFS? And did you take a back-up of your registry before making the suggested changes? If so, try restoring that back-up and see if you still get the CTDs with your original registry and we can go form there. Otherwise, try creating new (empty) profiles for your devices in MSFS.

I really can't comment on XPUIPC for X-plane, as this is from another developer. I have replied to your PM on the same subject. John

👍

Unfortunately I am on holiday now, back on support on the 18th. I am not going to review this support request until then. Please review what I have already advised. and also please remember that i do need details on what you have actually done, especially when I am suggesting multiple or different options. And I need to see your files each time you have changed things and require further support. In summary, review what I have already advised, provide the new files and I will get back to you on the 17th or 18th. Sorry for the delay. John

Yes. Also true. However, most {i.e. probably not all} are written with the default values anyway, but there are most probably some that use default values and are not written unless you manually add the value. Probably not very consistent, but a result of 20 years of development with many additional ini parameters added for very specific purposes. Hopefully the documentation should cover all ini parameters and give the default value when relevant. Cheers, John

Please do, and let windows install the default driver - disconnect your devices first and reboot before reconnecting. Show us your files afterwards... After you have done this, Pete's advise may not be relevant, not sure - he can advise {maybe}, but also not an issue if already done. Note I am on holiday now until the 18th - Pete may help you before this if you still have issues, otherwise I may take another look if i get a chance... John

Do you have any saitek/logitek drivers or software installed for the X56, or are you using the default windows drivers?

They look good!

And according to your FSUIPC6.ini: And you also have assignments to the yoke...well, to device 0, which is now your yoke but looked like it was previously your throttle. You should really have set AutoAssignLetters=Yes in your [JoyNames] section before removing and attaching new devices... Is your HOTAS throttle still connected? I think so, but it does not show in your FSUIPC7.ini file, presumably because it has the same id assigned as your Alpha. However, I cannot tell for sure as you have attached a continuation log, not a full log. I really need to see a full log (ie. do NOT start a New Log - never use this feature when generating log files for support, I always need to see the full log). Can you please: - disconnect the alpha (keep your throttle connected, if using that) - change your [JoyNames] section (shown above) to just: - run P3D/FSUIPC6 - just load an aircraft and then exit - show me your FSUIPC6.ini, FSUIPC6.log and FSUIPC6.JoyScan.csv files Then connect your Alpha, start P3D/FSUIPC6 again, load an aircraft and then exit, and show me those 3 (updated) files again. John

Apparently the Reverse Thrust Toggle issue has been fixed in the 6th Jan 2022 update (1.21.18.0), although I have not verified this at the moment. For reference see the following thread: https://forums.flightsimulator.com/t/reverse-thrust-broken/472181 John

Reverse thrust (toggle) has apparently been fixed in the latest update (1.21.18.0) for the aircraft that use that control, although I do not know if this applies to the Kodiak. Did you get it working? See this thread on the Asobo forums: https://forums.flightsimulator.com/t/reverse-thrust-broken/472181 John

Depends on what is causing your issue. Sounds like the axis you are using for the left engine throttle is registered as a digital (on/off) axis. Please see the following thread (originally written for saitek devices but still applies - just make sure you are using the correct VID/PID for your device): If you would like to try FSUIPC7, there is a trial license available in a sticky post at the top of this forum. John