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

Sorry for the hijacking, due to the timing and similar sounding issue, I thought they might be related. I might have my issue sorted which could have been caused by opening FSUIPC7 along with other apps at the same time that use it. If I still have issues, I will start another thread. Thanks John, and best of luck with your issue Aircom!

I quickly came up to the same problem. FSUIPC7.log

I do not use the PFC driver. I will test this new version out and give you a log file later if I run across the same problems. Thanks John!

Hello, I am looking for help to get custom switches working on my Bravo Throttles. Does anyone know if there is a way to "record" pressing switches in the cockpit and getting the Offset and Parameter values for each position? Essentially what is sent to the sim. I have looked through documentation before asking here, and can not find anything(not saying it doesn't exist). My best example right now is the Parking Brake. I want to get the true values of "Parking Brake On/Set" and "Parking Brake Off/Released" So I can have it repeating when pressed. That way when my sim is turned on, the parking brake is always in the correct position my switch on my quadrant is indicating. I also want to do this with other switches and such, so it would be nice if the recording function was possible. I have seen such a function in older versions of FSUIPC, however it does not seem to be here yet. Maybe I have to wait for this feature. If there is a better way to do this, please let me know. I have been looking, and I am sure someone is going to point me somewhere more than likely, thank you in advanced and sorry for the troubles.

I have the same or similar issue. It looks like this will require an update to FSUIPC7.exe. The program essentially locks up and still shows on the task bar. Right clicking the icon on the task bar will no longer work after a while as well when this happens. In order for things to work again, one must go to task manager and find "IPC Interface and More, for MSFS" which is really FSUIPC7.exe and end the task, then you can reopen fsuipc7 get your controls back for a limited time until it hangs again. I hope this is fixed soon as this makes FSUIPC7 nearly unusable for now. And I am sure it likely will.

Changing this figure had no, or minimal effect. When holding F2 do maximum reverse, the N1 goes up to about 90, or 90%. Fully loaded, the aircraft does not move when it stops. When putting the thrust into reverse using the method on this thread, the N1 goes to 110, or 110%. The same scenario(fully loaded) the aircraft accelerates very rapidly up to 200kts, it is then going so fast that it tries to rotate around and doesn't go much or any faster because if this. I can create a video tomorrow if you think it is required.

Shouldn't it have the exact same effect as if I held down F2 until it reached maximum reverse thrust? These act very differently. I checked the Aircraft.cfg, and there was nothing in there that reverenced any sort of maximum reverse thrust, or limit. Below are the closest relevant entries in the .cfg. When I apply full reverse thrust with the Lua, after stopped, If i let it go backwards it quickly speeds up to well over 100kts within 10 seconds. I could record and post a link later or tomorrow possibly. But I have a busy day today. [jet_engine] thrust_scalar=1.0 [contact_points] // IAS values increased point.0=1, 71.738, 0.000, -14.447, 1575.1, 0, 1.955, 70.0, 1.224, 1.724, 0.825, 20.0, 21.0, 0, 400.0, 500.0 //NLG point.1=1, -7.756, -18.209, -14.547, 1574.8, 1, 1.955, 0.00, 3.798, 0.556, 0.847, 20.0, 21.0, 2, 400.0, 500.0 //LWLG point.2=1, -7.756, 18.209, -14.547, 1574.8, 2, 1.955, 0.00, 3.798, 0.556, 0.847, 20.0, 21.0, 3, 400.0, 500.0 //RWLG // point.3=1, -17.851, -6.729, -14.547, 1774.8, 1, 1.955, 13.0, 2.131, 0.990, 0.847, 20.0, 21.0, 1, 400.0, 500.0 //LBLG point.4=1, -17.851, 6.729, -14.547, 1774.8, 2, 1.955, 13.0, 2.131, 0.990, 0.847, 20.0, 21.0, 1, 400.0, 500.0 //RBLG // point.5=2, 72.441, 0.000, -4.721, 800, 0, 0.000, 0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 4, 0.0, 0.0 // Nose Bottom point.6=2, -60.142, -105.473, 7.263, 800, 0, 0.000, 0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 5, 0.0, 0.0 // Left Wingtip point.7=2, -60.142, 105.473, 7.263, 800, 0, 0.000, 0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 6, 0.0, 0.0 // Right Wingtip point.8=2, -63.239, 0.000, -4.402, 800, 0, 0.000, 0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 9, 0.0, 0.0 // Tail Lower point.9=2, -122.948, 0.000, 49.021, 800, 0, 0.000, 0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 9, 0.0, 0.0 // Tail Upper point.10=2, -16.226, -69.52, -7.49, 800, 0, 0.000, 0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 4, 0.0, 0.0 // Engine #1 point.11=2, 12.574, -38.815, -10.115, 800, 0, 0.000, 0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 4, 0.0, 0.0 // Engine #2 point.12=2, 12.574, 38.815, -10.115, 800, 0, 0.000, 0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 4, 0.0, 0.0 // Engine #3 point.13=2, -16.226, 69.52, -7.49, 800, 0, 0.000, 0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 4, 0.0, 0.0 // Engine #4 point.14=2, 75.118, 0.000, 19.223, 800, 0, 0.000, 0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 4, 0.0, 0.0 // Nose Top point.15=2, 12.574, 0.000, -7.404, 800, 0, 0.000, 0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 4, 0.0, 0.0 // Belly point.16=2,-106.833, 0.000, 4.160, 800, 0, 0.000, 0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 9, 0.0, 0.0 // Tailskid point max_number_of_points = 21 static_pitch=0.010 static_cg_height=13.060 gear_system_type=1 [GeneralEngineData] engine_type = 1 Engine.0 = -28.342, -69.565, -2.856 Engine.1 = 0.4, -38.855, -5.155 Engine.2 = 0.4, 38.855, -5.155 Engine.3 = -28.342, 69.565, -2.856 fuel_flow_scalar = 1.1010 min_throttle_limit = -0.31 max_contrail_temperature = -30 [TurbineEngineData] // // Model : CF6-80C2B1F ~58K 4472kg, PW4056 ~ 56.75K 4273kg, RR RB211-524G ~58K 4390kg // fuel_flow_gain = 0.0029 // Gain on fuel flow inlet_area = 61.283 // Ft^2, [d_fan_tip = 106(*93) / 94 / 86.3 in] rated_N2_rpm = 11055.0 // Max RPM HPC [11055 GE, 10450 PW, 10770 RR -- no effect] static_thrust = 58000.0 // Lbs, nominal SLS adjusted by code internally afterburner_available = 0 // Afterburner available? reverser_available = 1 // Thrust reverser available? AfterBurnThrustSpecificFuelConsumption = 0

Works great for me! The only thing I could complain about is the range of reverse thrust is not even and smooth in the sim. The thrust lever moves to full, but it is not very linear and full range on my axis. Maybe I am doing something wrong. But for now it works better than I had before. Edited: Actually, it does something really weird. It does seem to function properly, however when I go into full reverse, it is like my engines have 100 times more thrust and I stop on a dime! Cool, but not realistic lol. Post of you have a fix please!

I will try this. Thank you Thomas. All controls are set up through FSUIPC currently. However, the disable controllers option is not checked. I will do this as well. If I have any more concerns, I will reply again.

I hate to be posting yet another problem : / This is not an FSUIPC problem, however, I was hoping someone could point me in the right direction. It seems that my 2 throttle ID's may have flip flopped on each other and now P3D also thinks it is a new controller, adding default controls again. This is very annoying and I think it is very possible it will happen again. Now all my controls I just put into FSUIPC are on the opposite quadrants... Has anyone had this problem? Any solution? Thanks. FSUIPC5.log FSUIPC5.ini FSUIPC5.JoyScan.csv