January 23, 20215 yr I'm new to Pilot2ATC and it works great unless I'm using the A320 in MSFS. Every time MSFS shuts down. The reason I believe P2A is the issue is I can run the A320 without a problem if I'm not running P2A. Nothing in particular is happening when it shuts down and it shuts down at completely random times (can be the beginning or towards the end of a flight), but it does shut down every time. No issues with other planes that I've discovered. Is this a known thing or is it just me (being the word not allowed magnet that I am).
January 24, 20215 yr Commercial Member The A320 has had numerous issues. It could be a glitch in the aircraft, but I suspect you are running out of memory or some other resource. Dave
January 24, 20215 yr Author Hmmm... Hadn't thought of that. I'd be surprised if that's the case, but I'll definitely look into it. Thanks for the reply
January 31, 20215 yr I read the below on the FSUIPC forums and it may be relevant. I believe some of the current stability issues with FSUIPC are wrongly causing Pilot2Atc's memory usage to get blamed, but I may be wrong! 'There is currently a known issue that is causing CTDs in MSFS when using SimConnect clients. There are various threads on this issue (both here and on the Asobo forums). Asobo are aware of this and its under investigation. The trigger seems to be related to the amount of data going through simconnect, and FSUIPC is a pretty heavy user.Some people have had success by disabling the reception of AI data in FSUIPC, by adding the following to the [General] section of your FSUIPC7.ini file: ProvideAIdata=No As FSUIPC7 is now a separate application (rather than an embedded dll), it should not cause MSFS to crash, and any MSFS CTDs should be reported to Asobo, with the windows event viewer details attached as well as the crash dump, if available.' https://forum.simflight.com/topic/91502-msfs-crashing-due-to-simconnect-errors/?do=findComment&comment=553767
Archived
This topic is now archived and is closed to further replies.