volkerjacob

Hello Urs, as former EFB v1 user, I already purchased the new version. I must say great work, EFB v2 is a great step forward. Thank You for Your hard work!

using Navigraph - here You can see the part from their charts: i can`t see a yellow warning dot at Data Provider

https://vatspy.vatcar.org/ -> this is the new website for VATSpy maintenance .....

Hello, for KDFW, the VKTRY 2 ARR is only available for RW's 16/17 via PHAUP. The ARR via POPPA for RW's 35/36 is not in the Dropdown list.... here a real flight example... https://flightaware.com/live/flight/AAL2688/history/20180301/1415Z/KSLC/KDFW

Hello Urs, VatSpy support will be continued. Ther is a new GitHub page that will be maintained with Updates. https://github.com/VATCAR/VAT-Spy-Client-Data-Update-Project

Hello Urs, maybe You try to ask the guy's from http://www.vattastic.com/ , if they are able to provide You the needed sector/position information?

Hello - there is a more up to date file here: https://www.dropbox.com/s/5n9miji1l9je1ch/Update_August_2017.zip?dl=0 but unfortunately, it's in the newer VATSPY format since SerfInfo not used anymore. But with the release of the new AccuMap client, it's possible that there will be no updates for VATSPY anymore ...

Hello Urs, since i updated to this build, i got the following error if i try to start DataProvider (first run after Update was fine!)

Hello David - thanks for explanation - will check that "/scenery" issue .....

and this works for all new xml registered scenery too? Weird - at my desk all xml registered scenery is missing and using only default layout .........

OK - a forum post by virtuali give me a hint to a quick and dirt solution for all FSDT users (GSX or similar new installer at P3D V3/4). At Data Provider Setting use C:\ProgramData\Virtuali\Couatl\prepar3dv3(4) as Scenery.cfg folder - FSDT read all available scenery configs and write this into his own file! Works for me with P3D V3 .

Never seen this before with UK2000, because there is no installer that can do that at the moment, but looks similar to my FSDT entries . There is no own FSDT scenery.cfg at me.

Done....

The problem here is that most developers will use the new scenery rule for P3D V3 AddOns too. If You install a update or new scenery into P3D V3, the scenery is also not registered at scenery.cfg.

Hello, with the release of Prepar3D V4 many scenery developers use the new Prepar3D scenery rule to register scenery's into P3D - even for older scenery with updated installer at P3D V3. The scenery's are now registered at C:\ProgramData\Lockheed Martin\Prepar3D v3 -> add-ons.cfg and scenery_add-ons.xml . This happen to all my FSDT and Flightbeam scenery today, after install of updated GSX. Dataprovider is not able to locate the scenery's anymore.