mulgrave Posted December 18, 2020 Report Share Posted December 18, 2020 FSUIPC crashed MSFS with error : FSUIPC7.exe 7.0.0.1 5fabb2b2 ntdll.dll 10.0.19041.662 27bfa5f0 c0000005 0000000000045f86 4724 01d6d5651c4aaf8f D:\FSUIPC7\FSUIPC7.exe C:\WINDOWS\SYSTEM32\ntdll.dll bcf7644b-7448-4012-b0fb-5e53d56cb558 any advice ? thanks Note : First time this happens Link to comment Share on other sites More sharing options...
John Dowson Posted December 19, 2020 Report Share Posted December 19, 2020 First, you are not using the latest version of MSFS - can you please update to v.7.0.3. Only the latest version is supported. If it still crashes, can you provide more information - as well as the event log, can you attach you FSUIPC7.log and FSUIPC7.ini files and provide a brief description of what was happening when the crash occurred. Thanks, John Link to comment Share on other sites More sharing options...
mulgrave Posted December 20, 2020 Author Report Share Posted December 20, 2020 Thanks John Where do I get the 7.0.3 version. ? Every time I download it from simmarket, it always version 7.0.2 Link to comment Share on other sites More sharing options...
John Dowson Posted December 20, 2020 Report Share Posted December 20, 2020 58 minutes ago, mulgrave said: Where do I get the 7.0.3 version. ? Sorry - v7.0.2 is the latest official release. There is a v7.0.3 pre-release out (posted somewhere in the forums), but for now just update to 7.0.2. John Link to comment Share on other sites More sharing options...
rvroman Posted December 23, 2020 Report Share Posted December 23, 2020 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 *********** Link to comment Share on other sites More sharing options...
John Dowson Posted December 23, 2020 Report Share Posted December 23, 2020 9 hours ago, rvroman said: This only seems to have started since updating to 7.02. I will try going back to 7.01 and advise. There really are no changes between 7.0.1 and 7.0.2 that could cause this. Your log shows simconnect failing, then FSUIPC7 exiting when it detects that MSFS has closed/crashed. I think the issue is almost certainly with MSFS or the SDK, as you say. Are you using any other SimConnect clients (or Track-IR)? It could be a known issue (since FSX) with the number of simconnect client connections being exceeded - you can activate SimConnect logging to determine this, and if this is the issue you could increase the allowed number of clients (or directly do this to see if things improve). However, if this was the issue, I would have expected to see some TransmitClientEvent errors in your log. You should also raise a crash report with Asobo (via zendesk), and include the crash report from the windows event viewer. John Link to comment Share on other sites More sharing options...
daern Posted December 23, 2020 Report Share Posted December 23, 2020 Another FSUIPC7 user here, who is now receiving CTDs from FS2020 since yesterday's update. In the case of the most recent crash, I hadn't even got the A32NX's engines switched on yet, and had just started loading passengers through SLC. Logs, although they look quite similar to those posted above: 63 System time = 23/12/2020 16:22:55 63 FLT path = "C:\Users\daern\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\" 78 ------------------------------------------------------------------- 94 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) 110 FS path = "D:\Games\Non-Steam\FS2020\" 110 LogOptions=00000000 00000001 6094 Simulator detected 43797 SimConnect_Open succeeded 43797 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3) 43797 MSFS version = 11.0.282174.999 43797 Initialising SimConnect data requests now 54078 User Aircraft ID not supplied -- trying default 58110 D:\Games\Non-Steam\FS2020\Community\a32nx\SimObjects\Airplanes\Asobo_A320_NEO\aircraft.CFG 58297 flights\other\MainMenu.FLT 58828 Aircraft loaded: running normally now ... 59688 System time = 23/12/2020 16:23:54, Simulator time = 15:23:53 (16:23Z) 68031 -------------------- Starting everything now ---------------------- 139828 Sim stopped: average frame rate for last 81 secs = 96.5 fps 139828 Max AI traffic was 0 aircraft 139828 ------------------------------------------------------------------- 142360 C:\Users\daern\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT 324016 Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B 324016 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B 326094 MSFS no longer running - exiting 326094 === Hot key unregistered 326094 === Stop called ... 326094 === Closing external processes we started ... 327094 === About to kill any Lua plug-ins still running ... 328266 === About to kill my timers ... 328266 === Restoring window procs ... 328266 === Unloading libraries ... 328266 === stopping other threads ... 328266 === ... Button scanning ... 328375 === ... Axis scanning ... 328485 === Releasing joystick devices ... 328485 === Freeing macro memory 328485 === Removing any offset overrides 328485 === Clearing any displays left 328485 === Calling SimConnect_Close ... 328703 === SimConnect_Close done! 328703 === AI slots deleted! 328703 === Freeing button memory ... 328703 === Closing my Windows ... 328703 === Freeing FS libraries ... 329719 === Closing devices ... 329719 === Closing the Log ... Bye Bye! ... 329719 System time = 23/12/2020 16:28:24 329719 *** FSUIPC log file being closed Minimum frame rate was 25.8 fps, Maximum was 100.6 fps Average frame rate for running time of 269 secs = 58.6 fps Maximum AI traffic for session was 14 aircraft Traffic deletions 0 aircraft Memory managed: 2 Allocs, 1 Freed ********* FSUIPC Log file closed *********** I'm running out of things to blame here - down to just A32nx and FSUIPC7 installed... Link to comment Share on other sites More sharing options...
John Dowson Posted December 23, 2020 Report Share Posted December 23, 2020 @daern Your issue is the same as that posted by @rvroman , and so my comment above also applies. You could also try the attached version, v7.0.3, that I will be releasing shortly. There aren't that many changes, but it has been rebuilt against the latest SDK (0.9.0.0) which was released with 1.12.13.0. John FSUIPC7.exe Link to comment Share on other sites More sharing options...
daern Posted December 23, 2020 Report Share Posted December 23, 2020 Just now, John Dowson said: @daern Your issue is the same as that posted by @rvroman , and so my comment above also applies. You could also try the attached version, v7.0.3, that I will be releasing shortly. There aren't that many changes, but it has been rebuilt against the latest SDK (0.9.0.0) which was released with 1.12.13.0. John FSUIPC7.exe 591.5 kB · 0 downloads Thanks @John Dowson - spotted that, installed it and am currently mid-way from Leeds to Brussels on a test flight 🙂 Will report back on my findings. Link to comment Share on other sites More sharing options...
daern Posted December 23, 2020 Report Share Posted December 23, 2020 So near, and yet so far! Flew all of the way from Leeds to Brussels, with barely a problem, landed cleanly and was taxiing the last half mile to the gate when the game went belly up and crashed. This time (and for the first time for me), it took out FSUIPC7 as well in short succession. These are the three error reports from the Windows event viewer: 1) 18:52:02 Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5fda32ba Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5fda32ba Exception code: 0xc0000005 Fault offset: 0x000000000043ca7a Faulting process ID: 0x3bc8 Faulting application start time: 0x01d6d94b98f9592f Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Report ID: a2041a77-2001-4ed3-a243-8d94f66831fe Faulting package full name: Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App 2) 18:52:10 Faulting application name: FSUIPC7.exe, version: 7.0.0.3, time stamp: 0x5fe3432a Faulting module name: ntdll.dll, version: 10.0.19041.662, time stamp: 0x27bfa5f0 Exception code: 0xc0000005 Fault offset: 0x0000000000045f86 Faulting process ID: 0x215c Faulting application start time: 0x01d6d94baa09b00a Faulting application path: D:\Games\Non-Steam\FS2020\FSUIPC7\FSUIPC7.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report ID: 6e2fbe8d-0068-413e-bd33-82f86538efcd Faulting package full name: Faulting package-relative application ID: 3) 18:52:14 Faulting application name: FSUIPC7.exe, version: 7.0.0.3, time stamp: 0x5fe3432a Faulting module name: ntdll.dll, version: 10.0.19041.662, time stamp: 0x27bfa5f0 Exception code: 0xc000041d Fault offset: 0x0000000000045f86 Faulting process ID: 0x215c Faulting application start time: 0x01d6d94baa09b00a Faulting application path: D:\Games\Non-Steam\FS2020\FSUIPC7\FSUIPC7.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report ID: 18745916-c8e0-40d6-831d-66f3f3b5c934 Faulting package full name: Faulting package-relative application ID: These are the FSUIPC7 logs: 78 System time = 23/12/2020 16:50:05 78 FLT path = "C:\Users\daern\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\" 94 ------------------------------------------------------------------- 109 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) 125 FS path = "D:\Games\Non-Steam\FS2020\" 141 LogOptions=00000000 00000001 6109 Simulator detected 45656 SimConnect_Open succeeded 45656 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3) 45656 MSFS version = 11.0.282174.999 45656 Initialising SimConnect data requests now 70438 User Aircraft ID not supplied -- trying default 74500 D:\Games\Non-Steam\FS2020\Official\OneStore\asobo-aircraft-tbm930\SimObjects\Airplanes\Asobo_TBM930\aircraft.CFG 74703 flights\other\MainMenu.FLT 75406 Aircraft loaded: running normally now ... 75969 System time = 23/12/2020 16:51:21, Simulator time = 15:51:20 (16:51Z) 83031 -------------------- Starting everything now ---------------------- 162453 D:\Games\Non-Steam\FS2020\Official\OneStore\asobo-aircraft-208b-grand-caravan-ex\SimObjects\Airplanes\Asobo_208B_GRAND_CARAVAN_EX\aircraft.CFG 162453 Sim stopped: average frame rate for last 87 secs = 91.4 fps 162453 Max AI traffic was 1 aircraft 162453 ------------------------------------------------------------------- 225234 D:\Games\Non-Steam\FS2020\Community\a32nx\SimObjects\Airplanes\Asobo_A320_NEO\aircraft.CFG 225250 Sim stopped: average frame rate for last 62 secs = 99.4 fps 225250 Max AI traffic was 0 aircraft 225250 ------------------------------------------------------------------- 228609 C:\Users\daern\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT 237641 #### ERROR: No SimConnect data seen for more than set stall time - will attempt to reconnect... 237641 **** SimConnect Data Stalled! Re-connecting now ... **** 237906 SimConnect_Open succeeded 237906 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3) 237906 MSFS version = 11.0.282174.999 237906 Initialising SimConnect data requests now 237906 User Aircraft ID 1 supplied, now being used 237906 SimObjects\Airplanes\Asobo_A320_NEO\aircraft.CFG 237953 User Aircraft ID 1 supplied, now being used 238672 System time = 23/12/2020 16:54:03, Simulator time = 16:53:53 (16:53Z) 1882281 **** Restarting traffic scanning due to non-reception **** 7321109 MSFS no longer running - exiting 7321109 === Hot key unregistered 7321109 === Stop called ... 7321125 === Closing external processes we started ... 7322141 === About to kill any Lua plug-ins still running ... 7323297 === About to kill my timers ... 7323297 === Restoring window procs ... 7323297 === Unloading libraries ... 7323297 === stopping other threads ... 7323297 === ... Button scanning ... 7323406 === ... Axis scanning ... 7323516 === Releasing joystick devices ... 7323516 === Freeing macro memory 7323516 === Removing any offset overrides 7323516 === Clearing any displays left 7323516 === Calling SimConnect_Close ... 7323734 === SimConnect_Close done! 7323734 === AI slots deleted! 7323734 === Freeing button memory ... 7323734 === Closing my Windows ... 7323734 === Freeing FS libraries ... 7324734 === Closing devices ... 7324734 === Closing the Log ... Bye Bye! ... 7324734 System time = 23/12/2020 18:52:10 7324734 *** FSUIPC log file being closed Minimum frame rate was 17.1 fps, Maximum was 100.5 fps Average frame rate for running time of 7258 secs = 30.7 fps Maximum AI traffic for session was 62 aircraft Traffic deletions 0 aircraft Memory managed: 2 Allocs, 1 Freed ********* FSUIPC Log file closed *********** So, definitely different behaviour, but if I were a betting man, I would say that MSFS is blowing up and taking FSUIPC7 out with it as collateral damage. Feel free to shout if I can provide any other details. Link to comment Share on other sites More sharing options...
rvroman Posted December 23, 2020 Report Share Posted December 23, 2020 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. Link to comment Share on other sites More sharing options...
John Dowson Posted December 24, 2020 Report Share Posted December 24, 2020 @daern I'm surprised about those events as your log shows FSUIPC7 exiting normally and that it was MSFS that crashed. I guess they are non-fatal errors due to the MSFS error. Your problem is almost certainly due to MSFS and you should raise a zendesk bug report. Btw, can you please ALWAYS attach your full log rather than pasting extracts, as there is further information I need to see, such as devices being used and the build version of FSUIPC (and any dlls) that you are using. @rvroman As you have not attached any relevant information (i.e. your logs) I can't really comment, but if it is similar to your previous log (or that of daern's) then it will also be the same issue. Maybe worth checking the MSFS forums for any similar reports - I haven't had much time to check out any issues with the latest release yet.... John Link to comment Share on other sites More sharing options...
rvroman Posted December 24, 2020 Report Share Posted December 24, 2020 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 Link to comment Share on other sites More sharing options...
daern Posted December 24, 2020 Report Share Posted December 24, 2020 3 hours ago, John Dowson said: @daern I'm surprised about those events as your log shows FSUIPC7 exiting normally and that it was MSFS that crashed. I guess they are non-fatal errors due to the MSFS error. Your problem is almost certainly due to MSFS and you should raise a zendesk bug report. Btw, can you please ALWAYS attach your full log rather than pasting extracts, as there is further information I need to see, such as devices being used and the build version of FSUIPC (and any dlls) that you are using. @rvroman As you have not attached any relevant information (i.e. your logs) I can't really comment, but if it is similar to your previous log (or that of daern's) then it will also be the same issue. Maybe worth checking the MSFS forums for any similar reports - I haven't had much time to check out any issues with the latest release yet.... John Thanks John. Because of the lack of info from MSFS itself on the cause of the crash, I'm just doing long flights to try to rule stuff out. If I can crash it without FSUIPC7 running, then this would be useful, but so far I've not managed so it does rather smell like something they've mucked up with the SDK interface. Thanks for the response and I'll keep you updated with what I find. If I can't get a crash without FSUIPC7 running, I'll raise a case on zendesk over the next day or two. Link to comment Share on other sites More sharing options...
daern Posted December 24, 2020 Report Share Posted December 24, 2020 Update: Two more decent length flights completed without FSUIPC7 running and have experienced no further CTDs. Will raise a support ticket with Asobo. Link to comment Share on other sites More sharing options...
John Dowson Posted December 24, 2020 Report Share Posted December 24, 2020 6 minutes ago, daern said: Update: Two more decent length flights completed without FSUIPC7 running and have experienced no further CTDs. Will raise a support ticket with Asobo. Thanks for the update. Maybe worth checking the Asobo forums for issues with the latest release before you report - I still haven't had time to do this (or review the documentation updates for the latest release). Regards - and have a healthy and enjoyable festive period, John Link to comment Share on other sites More sharing options...
daern Posted December 24, 2020 Report Share Posted December 24, 2020 2 minutes ago, John Dowson said: Thanks for the update. Maybe worth checking the Asobo forums for issues with the latest release before you report - I still haven't had time to do this (or review the documentation updates for the latest release). Regards - and have a healthy and enjoyable festive period, John Thanks John. I've been watching the threads and, as yet, I've not seen anyone else report a combination of issues that would point to a specific SDK issue, but there's clearly a whole lot of people getting CTDs since this last release, so something is clearly up, even if there's no obvious pattern that's appeared as yet. Will keep an eye out... I wish you a quiet and peaceful Christmas for you and your family. Link to comment Share on other sites More sharing options...
dc1ps2 Posted December 27, 2020 Report Share Posted December 27, 2020 (edited) I also encountered the same problem, the following provides recorded videos and related files, please help developers to solve my troubles. Thanks a lot, if FSUIPC7 is not turned on, the sim can fly smoothly until reaching the destination. FSUIPC 7.0.3 MFS 2020 1.12.13.0 FSUIPC7.ini FSUIPC7.log Edited December 27, 2020 by dc1ps2 Link to comment Share on other sites More sharing options...
Macrobber Posted December 27, 2020 Report Share Posted December 27, 2020 On 12/23/2020 at 12:26 PM, John Dowson said: @daern Your issue is the same as that posted by @rvroman , and so my comment above also applies. You could also try the attached version, v7.0.3, that I will be releasing shortly. There aren't that many changes, but it has been rebuilt against the latest SDK (0.9.0.0) which was released with 1.12.13.0. John FSUIPC7.exeUnavailable This zip file is now unavailable. Amy chance it can be reposted? On 12/23/2020 at 12:26 PM, John Dowson said: @daern Your issue is the same as that posted by @rvroman , and so my comment above also applies. You could also try the attached version, v7.0.3, that I will be releasing shortly. There aren't that many changes, but it has been rebuilt against the latest SDK (0.9.0.0) which was released with 1.12.13.0. John FSUIPC7.exeUnavailable Link to comment Share on other sites More sharing options...
John Dowson Posted December 29, 2020 Report Share Posted December 29, 2020 On 12/27/2020 at 8:11 PM, Macrobber said: This zip file is now unavailable. Amy chance it can be reposted? v7.0.3 is now the latest official release - you can download it from the usual places (e.g. www.fsuipc.com or in the Download Links section of this forum). And I can only re-iterate what I have already said... If MSFS crashes, it is an issue with MSFS that should be reported to Asobo. You should report any CTD with any crash log reports from the Windows Event viewer. If its an issue in the SDK, SimConnect logging may also help. John Link to comment Share on other sites More sharing options...
Adi Fly Posted December 30, 2020 Report Share Posted December 30, 2020 Same here, but as I see its not an FSUIPC issue (same with Little Navmap with “Fetch AI or multiplayer aircraft” active). I think its about too many of data polling msfs causes ctd. https://forums.flightsimulator.com/t/ctd-using-third-part-tools-with-lot-of-data-polling/344200 Link to comment Share on other sites More sharing options...
flightplanFRA Posted December 31, 2020 Report Share Posted December 31, 2020 (edited) Hi @all, if got the same problem here. Before I installed the last MSFS Update I flew always in this config: Standard A32N FSUIPC7 FS Crew A320 Simsounds This never caused any troubles until I installed the Update of MSFS. Since then, I experienced 3 CTD. Every single one with the crash code: HRESULT: 0xC000014B Until now, there were no CTD when I turned off FSUIPC. The last time I tried FSUIPC & SimSounds but w/o FS Crew ...that worked fine as well, but it was only a short flight of about 1h. Maybe it really has something to do with the amount of data polling... Edited December 31, 2020 by flightplanFRA Link to comment Share on other sites More sharing options...
John Dowson Posted December 31, 2020 Report Share Posted December 31, 2020 2 hours ago, flightplanFRA said: Maybe it really has something to do with the amount of data polling... Yes. Its a problem with the MSFS SDK that you should report to Asobo via zendesk. John Link to comment Share on other sites More sharing options...
thomas747400 Posted January 2, 2021 Report Share Posted January 2, 2021 Hi, I have noticed that MSFS will CTD when I am loading a bush trip (crash happens at approx. 50% loading). This only happens if I use the batch start up file that was placed on my Desktop during the FSUIPC 7 installation. As a work around, I am staring MSFS first, load my flight and then launch FSUIPC 7 which does not result in any CTD. Perhaps give that a try 😉 Happy New Year Thomas Link to comment Share on other sites More sharing options...
John Dowson Posted January 2, 2021 Report Share Posted January 2, 2021 @thomas747400 Could you attach your FSUIPC7.log and FSUIPC7.ini file when this occurs please. It may be that you are still using some older [General] settings that have slower stall times set and so cause too many re-connects when starting-up. I'll also check this here later to see if I can reproduce. You could try deleting the contents of your [General] section (before starting FSUIPC7/MSFS), this will then get rebuilt with the current defaults (but you would have to apply any changes you require after). John Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now