Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Workaround for TWY mnt / importing custom airport? (V3)

Featured Replies

Hi Dave,

I read somewhere in another bug report that the data maintenance part of V3 is not yet implemented so I'm not filing this as a bug, more of a question (for XP12). I mostly fly out of an airport that is severely botched in the default scenery and in the Gateway, so I made my own changes through WED, but I cannot get them to work in V3. I can import them just fine in V2.

Is there a way to update V3 with V2 data until Data Mnt is up and running? Bonus question: Any ETA on a working Data Mnt? 😄 Thanks!

  • Commercial Member

You can convert the P2ABaseData.mdf file to the P2ABaseData.db file and get all the changes to all your airports brought over from V2.  Use the Data Conversion tab of the DataMnt tool for that, with the V2 .mdf file as the source and the V3 .db file as the target.

Also, the Import function for taxiways and Gates does work in the DataMnt tool.  What doesn't work, or just barely works, is the manual editing of taxiways and gates.

As for timing, it's high on the priority list after the bugs quiet down.  There is enough there now to allow you to do what you need.

 

  • Author
5 hours ago, Dave-Pilot2ATC said:

You can convert the P2ABaseData.mdf file to the P2ABaseData.db file and get all the changes to all your airports brought over from V2. 

 

I think this needs to be filed as a bug, because I did the conversion and V3 doesn't update the taxiways, even though the edits I did in WED work great in V2, so there's no issue with them. So I did the conversion, and V3 still uses the default scenery TWYs.

Quote

Also, the Import function for taxiways and Gates does work in the DataMnt tool. 

This also does not work for me. I imported in V2 from the custom scenery and it worked. I did the same in V3 and no go.

Quote

 What doesn't work, or just barely works, is the manual editing of taxiways and gates.

Well, in my case this is what did the trick. I redid most of the edits from WED in manual mode in V3 and they worked. They were saved and used by ATC. It's kinda wonky but if you keep at it after a few tries it's fine.

I don't know how to replicate the issue, because my editing leaves no trace in the logs... So, basically my issue is that neither importing nor converting updates the taxiways from custom scenery.

  • Author

Thank you! Here's a link to the airport file. It's LROP - Otopeni.

LROP

One way to make sure the scenery loads correctly is to check the name of the taxiway that is parallel to runway 08L/26R. It should be Q, not O.

To clarify, import worked in V3 as far as importing from the default scenery. The TWYs that come with Pilot2ATC database for LROP are simple aproximations and I was able to use the data from XP. Only that even the default data is a mess, so I needed custom data. That's the conversion/importing that doesn't work in V3 but worked in V2.

  • Author

You just needed to agree to the cookies and privacy policy, no need to sign up. Here's a link to dropbox too:
 

Dropbox LROP

  • 3 months later...

As I'm currently testing V3, just allow me a question regarding my modifications of taxiway and gates:

I understand I can convert P2A V2 Data\P2ABaseData.mdf into P2A V3 P2ADynamicData.db.
But what will happen at the next Navigraph AIRAC Update ?
Will V3 DB with my changes overwritten ?

At the moment, it is not a problem as V2 will be updated by Navigraph, so I can update V3 from V2,
but in the long run, after buying a V3 license, I may remove V2 from disk.

Or are the "local modifications" not stored in the same DB/tables/... as the Navigraph updates,
so after a one-time conversion of P2A V2 mdf into V3 db, my local modifications aren't touched by Navigraph updates into P2A V3 ?

  • Commercial Member

The taxiway data is not supplied by Navigraph and is stored in a separate database file:  P2ABaseData.db in V3 and P2ABaseData.mdf in V2.

To convert your V2 changes to be able to use in V3, you can use the manual Data Conversion in the Data Updater tab of the Data Manager utility on the Utilities tab of Settings.

Set the V2 P2ABaseData.mdf file as the Source file and the P2ABaseData.db in V3 as the Target  file.  Then press the Convert button.

Dave

OK, now I see, I have to change the database names in the Utilities -> Data Mnt.

So my first conversion with P2ADynamicData (.mdf -> .db) loads the V2 Navigraph data from V2 into V3
and now I converted P2ABaseData (.mdf -> .db), that took over my local taxiway/gate modifications from V2 to V3.

Thanks for your info !

Edited by QuaxTheSnoopie
spelling correction

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.