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

Problem ended up being the latest Realtek audio driver. Uninstalled it and no more CTDs.

OK John. Once again, thanks much for your prompt reply. I'll go back to ASOBO.

Thanks for your response. The screen just froze and did not CTD in MSFS. The FSUIPC error was the only error log I found at that time. I'm still on Windows 10 Pro (64bit). I have seen in many MSFS forums to hold a bit on Windows 11. Would changing the DisableMSFSMonitor variable in FSUIPC.ini help me with Windows 10? I'll try anything at this point.

John, just received an error for FSUIPC that didn't result from a MSFS CTD. Seems to be different error than before. Attaching logs below and Windows log. FSUIPC7.log FSUIPC7.ini systeminfo_21422.docx

OK. Thanks MUCH John for your response. I will focus on MSFS support. Many are having CTD issues. I guess I'm having the same problems as others. Great to know FSUIPC is not the culprit!

Still having CTD issues with all add-ons suspended (in Community Folder). Every time CTD occurs, I get a fatal error for FSUIPC too. I don't know if FSUIPC is causing the problem or if it's MSFS. Latest drivers from NVIDEA (511.65) are loaded, all Windows updates are current, etc. Here's my Specs and error text follows: Processor Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz 3.70 GHz Windows Build Windows 10 Pro (64) 21H2 OSBuild 19044.1503 Installed RAM 32.0 GB (31.9 GB usable) Memory CORSAIR Dominator Platinum System type 64-bit operating system, x64-based processor DISC Samsung 980 Pro 1 TB, Samsung SSD QVO 870 2 TB, Samsung 960 Pro 1 TB, Western Digital 500G Spinning GPU EVGA RTX 3090 FTW3 Hybrid MOBO ASUS ROG Maximus XII Extreme Display ASUS ROG PG35VQ Window Log Error: Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000 Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000015c1d59 Faulting process id: 0x51f0 Faulting application start time: 0x01d81c2fea1c324f Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Report Id: 2b796096-b89d-484b-9516-099b0a667025 Faulting package full name: Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Faulting application name: FSUIPC7.exe, version: 7.2.1.5, time stamp: 0x61efef58 Faulting module name: KERNELBASE.dll, version: 10.0.19041.1503, time stamp: 0xb2acaea9 Exception code: 0xc0000409 Fault offset: 0x000000000008ead3 Faulting process id: 0x54a4 Faulting application start time: 0x01d81c302d870e45 Faulting application path: F:\FSUIPC7\FSUIPC7.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 6e4136e3-69de-41bc-87cb-9d275558fbff Faulting package full name: Faulting package-relative application ID: FSUIPC7.ini FSUIPC7.log

FSUIPC7.logGetting an error after loading latest MSFS update: Processor Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz 3.70 GHz Windows Build Windows 10 Pro (64) 21H2 OSBuild 19044.1503 Installed RAM 32.0 GB (31.9 GB usable) Memory CORSAIR Dominator Platinum System type 64-bit operating system, x64-based processor DISC Samsung 980 Pro 1 TB, Samsung EVO 870 2 TB, Samsung 960 Pro 1 TB, Western Digital 500G Spinning GPU EVGA RTX 3090 FTW3 Hybrid MOBO ASUS ROG Maximus XII Extreme Display ASUS ROG PG35VQ Window Log Error: Faulting application name: FSUIPC7.exe, version: 7.2.1.5, time stamp: 0x61efef58 Faulting module name: KERNELBASE.dll, version: 10.0.19041.1503, time stamp: 0xb2acaea9 Exception code: 0xc0000409 Fault offset: 0x000000000008ead3 Faulting process id: 0x46ac Faulting application start time: 0x01d8196fcf913682 Faulting application path: F:\FSUIPC7\FSUIPC7.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: ed702a52-3cc2-478b-a917-bbbbb973e67c Faulting package full name: Faulting package-relative application ID: FSUIPC7.ini Saturday 2/5 @8:48 PM CST. Is this due to MSFS shutting down prematurely or the cause of MSFS shutting down prematurely?

Got it. Thank you for the quick reply.

John, Is there an easy parameter to change that will allow me to undock MSFS from the FSUIPC.exe? I prefer to start FSUIPC independently from MSFS.

Well, I think I figured it out, although I can't explain it. I had been running the .exe (right click run as Administrator) on the install. For some reason it was creating a phantom .ini and log on my desktop instead of in my FSUIPC7 folder. I tried just clicking on the .exe and everything was placed where it was supposed to. MSFS is connected and everything is working. MUCH appreciate your willingness to hang with me on this. I'm a long-time licensed user of FSUIPC and I look forward to purchasing FSUIPC7! Update - The issue was copying the original .exe from my installation folder to the desktop instead of just putting a shortcut on the desktop. By placing the FSUIPC7.exe file on the desktop, it was placing a new .ini file and log on the desktop when running. Once I changed the desktop icon to a shortcut and left the FSUIPC7.exe in my installation directory, all's well.