N987PL

Done. Thanks

Yes, I know the regular FSUIPC UI shows and minimizes when I start it, but the attached only starting happening when I selected Axis Logs. I unselected that option in the alt f control menu, but am still getting this view instead of the normal FSUIPC logo screen I used to. Hopefully I'm explaining myself correctly.

That was it. Sorry for wasting your time. One other question however. I turned axis logging off on the FSUIPC console, but when I run FSUIPC before starting MSFS now, I still get the logging screen instead of the UI as before. Anything extra I need to do except uncheck axis logging in the console?

I have the DA62X Improvement mod installed. I'll try removing that and see if the ailerons work. Thanks for the reply.

Turned on logging. Not sure why the toe brakes were logging so many entries but I think it picked up the relevant aileron info. Also corrected my throttles to match. FSUIPC7.log FSUIPC7.ini

Noted on where to post in the future. Thanks for the reply. I'll try your suggestions and report back on Monday. Have a great rest of your weekend....

First of all, I can't find another posting about FSUIPC and the DA62 in MSFS, so I'm posting here as a first pass attempt to be in the right place... For the life of me, I can't get the correct bindings for the aileron axis in the DA62. Everything works (not sure why my two throttles are mapped differently, but they work fine) except the aileron axis. I'm happy to direct this elsewhere on the forum if I'm not in the right place, but any information that you can offer to help would be most appreciated. Attached .ini and .log. Thanks in advance FSUIPC7.log FSUIPC7.ini

Everything worked precisely as you instructed. Your help John, is MOST appreciated!

Thanks John. I'll try this.

My Precision Flight Controls Throttle Quadrant works with all other airplanes in MSFS....BUT not the CRJ 500/700/900 or the PMDG 737. I went to page 2 in the EFB for the CRJ as instructed on their forum, but the axis were not "seen" by the EFB utility. In PMDG, throttle 1 axis worked fine, but not throttle 2. There was some issue with the reverse lever on throttle 2 being very eratic in it's movement, and the throttle would not advance. Anyone else have this issue with both airplanes? Again, the Baron and Diamond DA62 work fine (both axis' are mapped in FSUIPC correctly) in MSFS and have worked fine since I installed MSFS 2 years ago, but both the CRJ and PMDG 737 are not working. PFChid64.log PFCcom64.log FSUIPC7.ini FSUIPC7.log

Wow John. I'm a firm believer in FSUIPC and have been for years, but your response here is exactly why I dread posting anything. I will create a new topic.

Apologies if I'm not posting this in the right place. My Precision Flight Controls Throttle Quadrant works with all other airplanes in MSFS....BUT not the CRJ 500/700/900 or the PMDG 737. I went to page 2 in the EFB for the CRJ as instructed on their forum, but the axis were not "seen" by the EFB utility. In PMDG, throttle 1 axis worked fine, but not throttle 2. There was some issue with the reverse lever on throttle 2 being very eratic in it's movement, and the throttle would not advance. Anyone else have this issue with both airplanes? Again, the Baron and Diamond DA62 work fine (both axis' are mapped in FSUIPC correctly) in MSFS and have worked fine since I installed MSFS 2 years ago, but both the CRJ and PMDG 737 are not working.

Didn't fix the issue. I completely deleted the EXE.xml file, uninstalled FSUIPC, and reinstalled. FSUIPC re-created the EXE.xml file and the FSUIPC log attached didn't report any errors in autostarting. And again, prior to the last two FSUIPC updates, FSUIPC started automatically. I guess it could be a coincidence and may not have been a result of any changes with FSUIPC but rather an MSFS update. I can still get FSUIPC working in MSFS by running the FSUIPC.exe, but have to do it manually while MSFS is loading. InstallFSUIPC7.log

Thanks for the reply John. I moved FSUIPC ahead of the other two addons in my EXE.xml file. Will see if this fixes and report back.

John, since this is the closest post I can find regarding my issue, I wondered if you could help me. Before the last two updates, (current logs attached), I didn't have to use the FSUIPC desktop Icon to start FSUIPC. In MSFS load, the FSUIPC logo would display and everything worked when the MSFS load completed and I was on the ramp. The only way FSUIPC works now is for me to use the desktop icon, and that was random a bit last Friday. I can go to Windowed mode while the aircraft is on the ramp in MSFS, click on the FSUIPC executable, and everything loads then, but that is the only way to have FSUIPC control consistently. Did a parameter change in the .ini with the latest releases that I need to address? As you'll see in my attached .ini, AutoStart is set to "Y". Much appreciation for your help in advance.... FSUIPC7.ini FSUIPC7.log