John Dowson

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

Not quite. The general (non-profile specific) calibration settings will be used if there is no profile-specific calibration section. If there is, that will be used. However, what ini parameter is used is based upon the presence of the profile-specific calibration section, not an individual ini parameter. No, this is not correct. An axis slope value set in the general, aircraft non-specific area will apply to profile specific aircraft if there is no corresponding profile calibration section. If the section exists, that section will be used. So, the calibration works in a similar way to the [Axis] sections, not the [Buttons] or [Keys]. The first time you check the profile-specific check-box in the calibration panel, the current general calibration section (+ any changes made in the current session) is used to create the profile-specific calibration section. From then on, only the calibration-specific section ini parameters will be used. Hope this makes sense. John

Yes, of course! Forgot about that - thanks Luke. Please see John

You posted in the Flying W Simulation forum. I have moved your request to the FSUIPC7 / MSFS sub-forum, although your question is not really related to FSUIPC7...you should really contact Pilot2ATC support for issues with that program, or look at the Asobo/MSFS documentation/forums for the location of flight plans.... The location of the flight plan folder depends on what sort of MSFS installation you have, Steam or MS Store. If its a steam installation, the location is: [Your User Folder]\AppData\Roaming\Microsoft Flight Simulator\ and for MS Installs it is: [Your User Folder]\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\ The location is also logged at the beginning of your FSUIPC7.log file (and held in offset 0x1000) - here's mine: John

Ok. But why didn't you just follow the advice in the Installation and Registration document: John

That message is from the other topic, also deleted. So, what was the issue? Did you manually create the key file? If so, please re-run the installer. This will populate the registration details panel where you can validate (by clicking the Register button). Can you try that please to see if it now validates ok. I would like to know what your issue was, ie. why your key could not be validated.

Please keep to this topic for your issue...I have deleted your posts in the other topic I referenced. Do you mean you manually created the key file? If so, what do you mean by 'didn't work'? Have you actually tried to run FSUIPC7 (unregistered)? Does it run? Have you installed the VC++ redistributables?

If you don't have the required VC++ libraries installed, FSUIPC7 won't run, which is why you should try running it, as advised, to see if this is the issue. Anyway, try installing the latest combined VC++ redistributable package, instructions in the README.txt.

Does this mean that you have now successfully registered?

Ok, thanks. Looking at the documentation, both of the EXTERNAL_POWER_AVAILABLE and EXTERNAL_POWER_ON are indexed variables: EXTERNAL POWER AVAILABLE This will be true if the given external power source is available. Use an external power index when referencing. EXTERNAL POWER ON The external power switch position, true if the switch is ON. Use an external power index when referencing. Any idea in what the index refers to? I am currently requesting unindexed, or index 1.

Ok, then you posted in the wrong place - there is a specific sub-forum for FSUIPC7 / MSFS. I will move your post. Did you follow the advice? Can you actually run FSUIPC7? If not, you may need to re-install your VC++ redistributables. I have checked your details and they are validated and working as expected here, so you are either not entering them as specified or something else is going on. If you cannot run FSUIPC7, it will be the VC++ redistributables. If it does run ok, you could try manually creating your FSUIPC7.key file. Instructions can be found in this post (but this really shouldn't be necessary): You only need to buy that if you are going to use WideClient on a 2nd PC (i.e. have FSUIPC clients running on a 2nd PC). Note that you can now run FSUIPC7 on a client PC, so you may not even need it even if you have FSUIPC clients on a 2nd PC. John

Do you know what the difference is between the AUTOPILOT ALTITUDE LOCK VAR:3 and AUTOPILOT ALTITUDE LOCK VAR:1 variables is? Is one the active/set value, and the other the dialed-in value?

It is reported as unavailable when on a runway, but available when at a gate. However, when available and requested, once connected that simvar doesn't change. At least thats what I have found... No time wasted! I will keep those new offsets anyway. John