November 2, 20205 yr When the FSAerodata database is enabled in V5 I have seen a consistent CTD when using any aircraft that uses a default P3D GPS unit. The problem occurs when entering a direct to key entry on the first letter of the desired navigation fix or airport code. The sim will freeze and then close. When the FSaerodata database is disabled the error no longer occurs. This seems to be unique to version V5 including V5.1 as the problem does not exist in V4.5. Posted to the Fsaeodata support forum but did not receive a response. Interested if anyone else has observed this in V5. Gary Stewart
November 4, 20205 yr Author Received a reply from FsAerodata they confirmed the CTD on their end also. He stated a fix has been implemented for the next air data cycle 2012. When the database is enabled in V5 the first waypoint in a default GPS is 002HP which has been disabled by the cycle update and that causes the error to occur. Gary Stewart
March 9, 20215 yr Yes, I have updated P3D v5 for fsAerodata, and I have observed this same phenomenon. I do not think that they have fixed the issue and 2012 came out just a few weeks ago.
March 10, 20215 yr The problem seems to be solved. The issue was linked to fsAerodata Deactivating the fsAerodata database and then reactivating it took care of the problem. See here: https://www.fsaerodata.com/forum/viewtopic.php?f=4&t=563&p=2166#p2166
Archived
This topic is now archived and is closed to further replies.