Travis1992

I have not yet tested it, but Asobo has claimed a fix for the issues with FSUIPC and Simconnect. https://forums.flightsimulator.com/t/new-apr-5-2022-sim-update-9-beta-release-notes-1-25-5-0/509205

I would highly not recommend switching between the two versions. There is a somewhat easy way to do this, however many people have reported issues and had to do various things such as reinstall and more to get things fully back to stock standard. I have not kept up on the actual fix to that, it is a mess I am sure you would rather not go into. We will be waiting patently for a fix, as it might be deeper than just the menu thing, but when asobo gives a response, I will try to update this thread if it is not already posted. Thanks John and have a good rest of your weekend.

I was also able to get the sim working with FSUIPC after I loaded into the flight. Thank you for that advice in_04. At least this friendly community advice helps us until a proper fix on either side is made. This post and forum worked as intended... If we come together, and work together, it helps us solve problems. Pointing fingers doesn't help anyone. The ProvideAIdata=No also did not change the crashing issues for me as well. I will be looking forward to seeing a fix on either side and will be checking back from time to time. For now, we can fly with our custom controls and peripherals again.

Hi Alex, It is in your FSUIPC7 installation folder. It is named "FSUIPC7.log"

I suggest anyone experiencing this issue follow that advice and report to Asobo using that thread. AI data has known to cause issues on previous updates. those experiencing this issue could also try with the following added to the [General] section of your FSUIPC7.ini file: ProvideAIdata=No I am running with this and have had no issues. I will also try with this removed when i get a chance. John This post was the most irresponsible post I have seen since I have been using FSUIPC for probably a decade now. I am very disappointed. The reason why it was posted here is for awareness. So somebody can fix it or give guidance to fix it. No once was screaming for your name in these posts John. Any other community members might have had a solution too. As for the advice on the MSFS forum page, it is clear that neither you or the mod on that forum took the time to read that post. The original poster put "solution" when they were simply still trying to find the issue. Sure he got it to work, and that was pointed out that he was not running these programs that were causing the crash. Thank you for still providing a possible fix. I hope to see a little more positive feedback next time there are issues, and people are not nagging and crying for you to come help. We just want to all make the sim a better and easier place to fly.

I can confirm this being an issue as well. When I launch without FSUIPC on, it goes fine until I manually run the FSIUPC7.exe. Crash log: Faulting application name: FlightSimulator.exe, version: 1.25.4.0, time stamp: 0x00000000 Faulting module name: FlightSimulator.exe, version: 1.25.4.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000013f7198 Faulting process id: 0x3434 Faulting application start time: 0x01d8462f7b2573e6 Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.25.4.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.25.4.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Report Id: e1111188-affd-4474-bd71-c7ac6e4d19c4 Faulting package full name: Microsoft.FlightSimulator_1.25.4.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App MSFS Thread of people having same issues: https://forums.flightsimulator.com/t/ctd-on-starting-the-sim/508288

Thanks so much. That worked perfectly! Here is an example if anyone needs it: 0=BX,256,F,67103,0,0,0,*-1 -{ TO SIM: THROTTLE1_AXIS_SET_EX1 }- 1=BR,256,F,67110,0,0,0,*-1 -{ TO SIM: THROTTLE2_AXIS_SET_EX1 }- 2=BU,256,F,67124,0,0,0,*-1 -{ TO SIM: THROTTLE4_AXIS_SET_EX1 }- 3=BV,256,F,67117,0,0,0,*-1 -{ TO SIM: THROTTLE3_AXIS_SET_EX1 }- Do not use the above and copy/paste, it will not work. It is just to show the general set up and addition of the ',*-1' to the entry.

Also, I failed to mention... The controls through FS did not work either. They would not move the levers in the cockpit, but they would move the RPM when I move my throttles, then when no movement, RPM goes to 0(idle). I think direct did this too, but don't quote me on that for sure.

When I use EX1, it works, but the throttles are reversed and as said by DaveG, you can not calibrate them to reverse them(back to normal). I used direct to FSUIPC because of a previous issue we talked about: The only way I can fix(for now) this is by setting up throttles in the simulator, which is quite annoying to switch back and forth.

I am having the same issues. Using "Direct to FSUIPC calibration" for my 4 throttles. Honeycomb Bravo.

Hey John. So when you are open in the Axis window, it no longer shows on the system tray or the task bar if it is put in the background i.e. click on the simulator. In order to get it back, I need to either close it, or use task manager to bring the window to front as previously stated. Can you make the axis and button windows into a window that shows up on the task bar?

If it provides an easy to replicate issue for me again, I will make a video. For now, I suppose all is well. Thank you again for the help! I appreciate the support you guys have consistently provided over the many years.

I did look in the system tray. It was neither place. I constantly use it to initially open in the system tray and understand it shows up on task bar once the window is open, yes. It is in neither once it decides to go to the background(for any reason, me or the program tells it to) while the axis manager window is open. When the axis screen is told to go to the background or such, it all disappears and like previously stated, I have to go hunting in Task Manager or restart the program with the exe.

Thank you John. Setting it to "Send direct to FSUIPC calibration" reduced the lag to very minimal amounts. It was a little buggy setting it up, requiring computer restarts due to FSUIPC losing ability to communicate with the sim, even after sim reboot. But I did get it up and working properly. With the Bravo throttles, you need to reverse the axis because the hardware is set up reversed for some reason by honeycomb, which requires me to use the calibration tab. Also something else to add is that often when trying to set up controls and such, when I minimize the window for things such as axis, or selecting some specific options in there that may cause the window to minimize. It is no longer possible to open the window back up. This results in me either needing to re-run the executable to restart the program, or going into task manager and having to refocus on the window. I do window/task switch key(Native window feature) to switch to the program, and it doesn't. It is not on my task bar in either locations. It is a small but very annoying detail that I have come across over 20 times easily. Other than those things, everything is fantastic. Thank you!

Hi, I have been having issues for a while where the axis processing with FSUIPC 7.0.10 is show lag and spikes both up and down to my current setting when I am adjusting the throttle in the joystick calibration tab. This also translates into the simulator. It does however go to the appropriate position when they are not moved. I don't think this is related specifically to 7.0.10, because it was happening before. When in the Axis assignments tab, the numbers change properly with my inputs. I verified there were no axis' set in the simulator. I am also using the honeycomb bravo. Thanks for the help in advanced. FSUIPC7.log FSUIPC7.JoyScan.csv FSUIPC7.ini