MSFS switch bindings through FSUIPC7 not working

[pilgrimpilot]

Two things: 1) I haven't set any specific profiles because right now I use the same profile for every aircraft I fly. When I went to copy the log I found that all my bindings had to be reset. Must I set a profile for the bindings to stick? 2) I created new empty profiles inside MSFS except for the mouse and the keyboard, for which I kept the default profiles. The bindings for the axes set through FSUIPC7 are working fine, as are the default keyboard and mouse bindings set through MSFS, but the button and switch bindings that I have set in FSUIPC7 are not working, even though they show up in the log. I note that RepeatDelayCtr is set to 1. I don't know if that has anything to do with it, or how to change that setting if it does.

FSUIPC7 found MSFS and was connected, according to the Title Bar. The log includes Buttons and Keys, Axes, and Events. I had to delete some items from the log to keep it under 20 kb's for upload. I believe that what I have left will contain the pertinent information.

On a separate note, I find that the controls in MSFS are entirely too sensitive and jumpy, and the sim is impossible to fly by hand. This is true of every aircraft I have flown (GA only). I have good FR and no CTDs. I don't have these problems in XP 11 or FSX.

I welcome help and advice from anyone who can help with the control sensitivity issue and/or the switch issue in FSUIPC7 and of course John or Pete.

Thank you in advance. Merry Christmas!

GA-Z170XP-SLI-CF, i7 7700K@4.2GB, GeForce 1080TXi and M.2 SSD, 32 GBs DRAM at 2100MHz, Saitek Pro Flight Yoke/Throttle Quadrant, Cessna Trim Wheel, second Saitek Throttle Quadrant, MFG Rudder Pedals, Windows 10 Home 64-bit 21H2 19044.1415

FSUIPC7.ini FSUIPC7.log

[John Dowson]

On 12/25/2021 at 3:54 PM, pilgrimpilot said:

When I went to copy the log I found that all my bindings had to be reset.

Sorry, no idea what this means. What has your log got to do with your bingings/assignments? Why do you think your 'bindings had to be reset'?

On 12/25/2021 at 3:54 PM, pilgrimpilot said:

Must I set a profile for the bindings to stick?

No. General assignments for buttons and keys apply to all aircraft, and are added-yo or replaced by profile specific bindings. If there is a profile specific axes section for the loaded aircraft, that will be used exclusively. If no such section is present, the general axis assignments are used.

On 12/25/2021 at 3:54 PM, pilgrimpilot said:

I had to delete some items from the log to keep it under 20 kb's for upload. I believe that what I have left will contain the pertinent information.

Please don't do this. If the log file is too large to upload, just zip it.

On 12/25/2021 at 3:54 PM, pilgrimpilot said:

but the button and switch bindings that I have set in FSUIPC7 are not working, even though they show up in the log.

Which ones are not working?  Looking at your assignments, I see tyhat you have assigned to the PAN controls. These are known not to be working via SimConnect. To control views via FSUIPC, you need to assign your buttons/POV to the default key combinations used to control the cameras in MSFS. The same may apply to eyepoint controls.

On 12/25/2021 at 3:54 PM, pilgrimpilot said:

I welcome help and advice from anyone who can help with the control sensitivity issue and/or the switch issue in FSUIPC7

Sensitivity issues can usually be handled by appropriate calibration and the use of slopes, but this usually depends upon the axis and the aircraft. You could try switching from using 'Send to FS as normal axis' and use 'Send direct to FSUIPC Calibration' and then also calibrate in FSUIPC.

Cheers,

John

[pilgrimpilot]

Thank you for your reply. By 'bindings had to be reset' I meant that after I had set all the controls, when I looked at the log, none of them were there, so I had to do the bindings again. That is why I asked whether there had to be a profile set to have them stick. I must have done something wrong, because I see them in the log now. I use the buttons on the yoke exclusively for eyepoint views and panning, except for one toggle, which I use for elevator trim, so if simconnect doesn't see those, that explains why they are not working. I will set via MSFS. Thank for reminding me about zip. I didn't think about that when I was trying to upload. The controls that are too sensitive are the ailerons and the elevator. I have installed the Leo Bodnar board for those axes only. I use diview to calibrate them and then use the Windows control panel utility but I have to do that before every flight because the controls don't hold center. I will try sending them 'direct to FSUIPC Calibration' as you suggest and perhaps play with the slopes. I will repost with the results. Again, I don't have these issues with XP11 or FSX.

[John Dowson]

6 minutes ago, pilgrimpilot said:

By 'bindings had to be reset' I meant that after I had set all the controls, when I looked at the log, none of them were there, so I had to do the bindings again.

But your bindings/assignments have nothing to do with your log - why do you expect to see them there? You can see the affect of your assignments on the log when you operate them, if you have the appropriate logging flags set.

 

[pilgrimpilot]

Thank you for your reply. By 'bindings had to be reset' I meant that after I had set all the controls, when I looked at the log, none of them were there, so I had to do the bindings again. That is why I asked whether there had to be a profile set to have them stick. I must have done something wrong, because I see them in the log now. I use the buttons on the yoke exclusively for eyepoint views and panning, except for one toggle, which I use for elevator trim, so if simconnect doesn't see those, that explains why they are not working. I will set via MSFS. Thank for reminding me about zip. I didn't think about that when I was trying to upload. The controls that are too sensitive are the ailerons and the elevator. I have installed the Leo Bodnar board for those axes only. I use diview to calibrate them and then use the Windows control panel utility but I have to do that before every flight because the controls don't hold center. I will try sending them 'direct to FSUIPC Calibration' as you suggest and perhaps play with the slopes. I will repost with the results. Again, I don't have these issues with XP11 or FSX.

[John Dowson]

2 hours ago, pilgrimpilot said:

By 'bindings had to be reset' I meant that after I had set all the controls, when I looked at the log, none of them were there, so I had to do the bindings again.

You keep saying this and I keep giving the same response: you will not see your bindings when you look at your log.

2 hours ago, pilgrimpilot said:

I must have done something wrong, because I see them in the log now.

But you do not see your bindings in the log, as I keep on saying. Your bindings (i.e. assignments) are stored in your FSUIPC7.ini file.
You can see the affect of the bindings in the log, if and when you have the appropriate logging options set. Please understand the difference between your FSUIPC7.ini file, which holds all of your settings, and the FSUIPC7.log file, which is a log of the current/latest session.

3 hours ago, pilgrimpilot said:

I use the buttons on the yoke exclusively for eyepoint views and panning, except for one toggle, which I use for elevator trim, so if simconnect doesn't see those, that explains why they are not working. I will set via MSFS.

You can assign view controls in MSFS if you prefer. Alternatively, you can assign your POV to the keyboard assignments to control the view.

3 hours ago, pilgrimpilot said:

I will try sending them 'direct to FSUIPC Calibration' as you suggest and perhaps play with the slopes. I will repost with the results.

Ok. If you have any issues, activate appropriate logging (which for axes assignments would be Axes control logging) and show me both your FSUIPC7.ini and FSUIPC7.log files, the latter showing you moving your assigned axis through its full range.

John