![]() Please post (or send me) your email address - I'll be happy to send you a DEX to try after I work with this a little bit. I'll see if I have any success with the import. However, some of us have tried to establish new protocols for creating unique identifiers so that when one person's data is imported over another, conflicts aren't created.I'll be happy to take a look in the old DBD and play with it over the next couple of days. Now, if that means that all of the airport fields in the ILScan3.dbd had different names (which doesn't make sense), then yes, all of the airport fields would have to be updated to match.2. The airport keys must be an exact match to the airport keys in Fly!2. I know some people have had success with this.You say that the ILS and Airport keys need to be prefixed with specific characters. Frank later came out with improvements to DexImport which supposedly compensated for the DB variations and allowed old DEXs to be converted for use with Fly!2. The strongest signals received align directly with the length of the antenna. A transceiver is a communication radio that transmits and receives. (I have about 60 updates for navigation and approaches I hope to have out before Christmas).Now, never having attempted to transition old DEXs for new, I simply started from scratch with Fly!2 DB editing. Most radio transmitters generate an unstable oscillating frequency that is stabilized by a mixer. ![]() After Fly!2 came out, I transitioned over and began doing the same thing with Fly!2. Brian,In previous years I put in a lot of time putting in missing NAV and approach components for Fly!1.
0 Comments
Leave a Reply. |