in_04

Fix works perfect thanks for fast help

Just started the flight. Before FSUIPC7 is running, stop running as soon as i start the flight. Will install WASM

@John Dowson thanks for your great work. I guessed I make everything like you described and FSUIPC starts but crashed after several seconds. I added all logs and ini files FSUIPC7.zip

I had same problem than bobsk8, will check the new exe and hope problem is fixed. Was annoying to lose the Joystick in flight 🙂

@Pete Dowson any idea why I didn't get zero on the axis as output? Esp. the elevator axis is way off and make flying a helicopter difficult. Uploaded my FSUIPC.ini Gues log isn't really helpful FSUIPC7.ini FSUIPC7.log

Sorry for bother you, Close FSUIPC and restart it and it worked again 🙂

The new FSUIPC version 7.4.14 doesn't show me my Button assignments anymore. The profile is loaded and work, but nothing changes in the dialog. Need support. I changed nothing just updated too the 7.4.14 version. 20240507_FSUIPC7.zip

Hi @Pete DowsonI guess you already looking in the new SU11 release for changes. I currently miss the possibility to assign the rotor related TRIM keys for Longitude trimming. I also guess there are more missing, but these ones would help me a lot for Heli flying. Only lateral is currently in 7.3.14 present.

Ok my current workaround is: Set: AutoConnectToSim=No In the FSUIPC7 INI file, start as usual with EXE.xml, bat and so on. After your in cockpit ready to fly, open FSUIPC and connect it to MSFS. If you want to leave the cockpit, open FSUIPC again and disconnect from MSFS. This works for me without any CTD 🙂

Got FSUIPC7 to work at flight, after I started it a Sim shows the ready to fly button. No error occurred until the moment I stopped the flight and want to go back to main menu. MSFS2020 crashed. Here is the FSUIPC7 log: 390 ### Note: AI Traffic related facilities and data are inhibited! 390 LogOptions=00000000 00000001 3265 Simulator detected 8296 SimConnect_Open succeeded 8296 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3) 8296 MSFS version = 11.0.282174.999 8343 Initialising SimConnect data requests now 8343 Offset file 'C:\FSUIPC7\myOffsets.txt' not found (info only) 8343 Maximum number of custom events available is 2048 (defined by ini parameter MaxNumberOfCustomEvents) 8375 C:\Users\Games\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT 8375 SimObjects\Airplanes\bell 47\aircraft.CFG 8375 User Aircraft ID 1 supplied, now being used 8437 Aircraft loaded: running normally now ... 9000 System time = 02/04/2022 17:48:36, Simulator time = 08:48:41 (15:48Z) 9000 Maximum number of custom events available is 2048 (defined by ini parameter MaxNumberOfCustomEvents) 9015 Aircraft="FlyInside B47G" 16000 -------------------- Starting everything now ---------------------- 506203 Sim stopped: average frame rate for last 498 secs = 25.4 fps 506203 ------------------------------------------------------------------- 506203 User aircraft crashed! 520890 E:\Program Files (x86)\SSD1\FS2020\Community\flyinside-bell47\SimObjects\Airplanes\bell 47\aircraft.CFG 529343 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B 533390 MSFS no longer running - exiting 533390 === Hot key unregistered For me it seems the MSFS202 crash has something todo with the time FSUIPC7 start polling the SimConnect_CallDispatch. @John Dowson is there any other hint for getting it to work? Maybe some longer startup delays? The crash is a combination of FSUIPC7 and MSFS2020, only the use of both programs gives the crash, so both sides should take a look if they can find a solution. MSFS2020 runs flawless without FSUIPC7, it runs if I start FSUIPC7 late, but crashes if it I go back to the main menu. So what is difference with SimConnect when not actual in flight? FSUIPC7.log

Got the same crash too with the 1.25.4.0 SU9 Beta on startup Here is the FSUIPC log file Currently only workaround is to disable FSUIPC7 at all. Seems to be a problem with SimConnect_CallDispatch 342875 Aircraft loaded: running normally now ... 344797 Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B 344797 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B 348281 MSFS no longer running - exiting MSFS2020 starts without FSUIPC7 flawless. FSUIPC7.log

Hi Pete, believe it or not, but I also get the signature problem "from time to time". Means of ten starts of FSX there are two or three where FSUIPC wouldn't get the signature. I have no explanation and checked the ram many times without a problem. I run Vista 64 Bit, German with downloaded English language pack. Currently I live with this, but I hope for a FSUIPC version without the signature. If the signature is only for verify that it is virus free, it is not necessary for me. Just my 2 cents

Hi, could confirm the problem, at least with Direct X10 preview and the new released SR71 from AlphaSim. I got the Super Fog just after take off, must used clear all weather to continue the flight.

Hi Warrant, Have you tried this: solved problem by manual editing the FSX.cfg file. Changed F:\Games\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll.aheuqaiibizrqueuunbrroowcneolzrhbllzwnel=-1 too F:\Games\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll.aheuqaiibizrqueuunbrroowcneolzrhbllzwnel=2 and now it works.

I use SP1 because I was a tester and I have a MSDN subscribtion. But last but not least, dont know if you change something with version 4.26 or not. But now its working. Thanks for the help, and close the thread if possible.