rvroman

I was going to post this to the thread below as that is where there was a good discussion of the CTD issues, but since there have been a few more posts about this since then I thought I would start a new one. This probably will not provide any explanation from a programming perspective, so take it simply as "This is what is working for me", I do not have the knowledge to explain why. The short answer is uninstall FSUIPC (save any documentation you want from your my documents FSUIPC folder somewhere outside of my documents). In the thread linked above John provided a link to just the 7.03 exe file (it does not live within an installer). Download that and save it somewhere (not sure if it makes a difference, but I have it on a slave drive). Then run that exe first before starting MSFS. After it is running start MSFS as you would if you were not going to use FSUIPC (you don't really have a choice as uninstalling it took away the shortcut to start them together) Doing it this way I have been getting 8 hour flights without an issue. Granted I have just set them on AP and gone across the US, but every hour or so when testing I would turn that off and do some hand flying without an issue. All take offs and landings were done manually without issues including taxiing to the gates and ultimately exiting MSFS as normal. Again it may not make sense why it works, and may not work for everyone, but it is working for me. Here is what I experienced prior to doing it this way. In each instance where there is a CTD mentioned the logs showed the same errors everyone else is referencing (aka the long story) FSUIPC 7.01 and MSFS version at that time: No issues FSUIPC 7.02 first released and MSFS version at the time: No issues FSUIPC 7.02 and updated MSFS: CTD (MSFS alone: no issues) Replaced the FSUIPC exe with 7.03 (from link above): CTD (MSFS alone: No issues) Uninstalled FSUIPC and then just ran the standalone 7.03 exe: SUCCESS! No CTD Installed FSUIPC 7.03 the next day when John released the full installation package: CTD Uninstalled FSUIPC and went back to running it with the stand alone 7.03 ext: SUCCESS! No CTD Finally, even when running the standalone 7.03 exe if I start MSFS first and then start FSUIPC: CTD Again I cannot explain it, but hopefully that will not only work for others, but may provide some insight as to why running it as an installed program results in a CTD. Robert

Hi John, Thanks for posting the new version. I just finished the second long distance flight of the day and it worked like a charm. No CTD, no issues at all. Thanks again for a great product and the amazing technical/customer support. Happy Holidays. Robert

Thanks. I will try the new version as well. It probably is MSFS/SDK, but there is likely a FSUIPC element. I did a Boston to Los Angeles flight yesterday in the TBM (well the autopilot did while I did other things) without an issue by starting MSFS only. I then tried the same flight with MSFS and FSUIPC only and it crashed in less than 60 minutes.

Hi John, I am having the same CTD issues. The Windows event logger identifies FS2020 as the cause. But it only happens when I run FSUIPC. When I do a KBOS to KDTW (2.5 hours for me) it runs without an issue when I only use MSFS. When I run both MSFS and FSUIPC on that (or any) flight I get a CTD within 30 minutes to one hour. This only seems to have started since updating to 7.02. I will try going back to 7.01 and advise. I know this is likely out of your control since it is likely a MSFS/SDK issue, but just wanted to pass it along as it may (or may not) be of assistance in future updates to FSUIPC. Robert Here is the end of my last FSUIPC log in case it helps 2370906 SimConnect_Open succeeded 2370906 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3) 2370906 MSFS version = 11.0.282174.999 2370906 Initialising SimConnect data requests now 2386640 User Aircraft ID not supplied -- trying default 2392359 C:\Users\Rober\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\asobo-aircraft-tbm930\SimObjects\Airplanes\Asobo_TBM930\aircraft.CFG 2392546 flights\other\MainMenu.FLT 2394015 Aircraft loaded: running normally now ... 2394078 System time = 22/12/2020 13:01:28, Simulator time = 19:01:26 (20:01Z) 2394093 Aircraft="TBM 930 Asobo" 2452859 -------------------- Starting everything now ---------------------- 2455625 C:\Users\Rober\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT 7979421 Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B 7979421 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B 7980250 MSFS no longer running - exiting 7980250 === Hot key unregistered 7980250 === Stop called ... 7980250 === Closing external processes we started ... 7981250 === About to kill any Lua plug-ins still running ... 7981421 === Closing global Lua thread 7982437 === About to kill my timers ... 7982640 === Restoring window procs ... 7982640 === Unloading libraries ... 7982640 === stopping other threads ... 7982640 === ... Button scanning ... 7982750 === ... Axis scanning ... 7982859 === Releasing joystick devices ... 7982859 === Freeing macro memory 7982859 === Removing any offset overrides 7982859 === Clearing any displays left 7982859 === Calling SimConnect_Close ... 7983078 === SimConnect_Close done! 7983078 === AI slots deleted! 7983078 === Freeing button memory ... 7983078 === Closing my Windows ... 7983093 === Freeing FS libraries ... 7984093 === Closing devices ... 7984093 === Closing the Log ... Bye Bye! ... 7984093 System time = 22/12/2020 14:34:38 7984093 *** FSUIPC log file being closed Minimum frame rate was 14.8 fps, Maximum was 36.0 fps Average frame rate for running time of 5592 secs = 19.6 fps Maximum AI traffic for session was 130 aircraft Traffic deletions 0 aircraft Memory managed: 2 Allocs, 1 Freed ********* FSUIPC Log file closed ***********

Thanks, I will play around with various aircraft and GPS units.

The default aircraft is in reference to aircraft that come with MSFS 2020 and the default GPS. In FSUIPC 4 and FSX I have several of them (listed below) mapped to buttons and switches on my panel and the GPS is displayed on a secondary screen. These then operate the GPS 500 (comes with FSX and used by default FSX aircraft) as well as the GNS 400 and GNS 530 that come in various add on aircraft. Basically pushing the button or using the switch on the panel creates the same response as clicking the mouse on the GPS on the screen. I was hoping to do the same thing in MSFS, but this may just be one of those things they have not created compatibility for yet. GPS Clear Button GPS Cursor Button GPS Directto Button GPS Enter Button GPS Flightplan Button GPS Group Knob Dec GPS Group Knob Inc GPS Menu Button GPS Msg Button GPS Nearest Button GPS OBS Button GPS Page Knob Dec GPS Page Knob Inc GPS Procedure Button GPS Terrain Button GPS Zoomin Button GPS Zoomout Button

MSFS default aircraft. The list of GPS assignments pictured below.

Thanks. I did not think there would be, but when I saw the Go Flight thread I thought it might be worth asking. I wish all 3rd party developers were as committed to MSFS compatibility as the team at FSUIPC.

John, In the thread about GoFlight modules you mentioned that you had developed GFDev64.dll so that those modules could interface with MSFS through FSUIPC. Is there such a dll for Elite hardware? In particular their MEL throttle quadrant. https://flyelite.com/product/mel-throttle-quadrant/ In FSX their software https://support.flyelite.com/downloads/third-party-plug-in/ controls the quadrant and it shows up under modules just as FSUIPC 4 does. In case this is information helps, the quadrant is recognized by Windows as an attached USB device, but not an HID device, it can only work through their interface in FSX and below. Windows does not recognize it as a game controller and FSUIPC 4 does not see it. Thanks

I found my answer to the MFD and PFD buttons not mapping in other threads (thanks). Is it safe to assume the GPS buttons fall prey to the same issue, or is there a different process to map them between ver 4 and ver 7? Thanks.

I will admit I am a rookie user and have not yet looked into offsets, but all I did, using a toggle switch on my panel, was set the toggle taxi lights command as the control sent the switch is activated, and then the same command when it is turned off. If needed just make sure the switch on your VC panel and switch on your external panel have the same orientation when you start (make the VC switch match your panel) and they will stay in sync.