The vdgs ui always shows "no items to display". The VDGS log also shows:

----TIME----|----SENDER----|----ERRORMSG----
22:09:53 | CurrentDialog | Airport 'EDDK' COULD NOT be verified, reason: 'PACKAGE_NAME_UNVERIFIED'

 

I uninstalled and reinstalled all 3 dependencies via AO but still nothing works. Also disabling and enabling the streamed airport did nothing. Any help is appreciated. I also contacted support but never got an answer...

I am having the same problem with Simwings EDDM and Simwings EDDH as well as Aerosoft EDDK and Aerosoft ENVA, all of which I bought from the MSFS Marketplace years ago. I have used them successfully with Aerosoft VDGS in MSFS 2020, and the sceneries themselves seem to work fine in MSFS 2024 as well, but I have found no way to get Aerosoft VDGS to work.

 

From the way I understand the structure of the system, I think there are at least two reasons why it doesn't work:

1. The folder names are different.
   • Aerosoft VDGS finds the right path to my MSFS2024 installation (...\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages), but it expects two subfolders in there: Community and Official. I do have a Community subfolder in the Packages folder, but then there are three other subfolders: Official2020, Official2024, and StreamedPackages. As long as the Aerosoft VDGS driver doesn't look for these subfolder names, it is not going to find anything installed through the MSFS Marketplace. I don't think you can configure the path, so it would be up to Aerosoft to address this.
2. The sceneries are streamed and not installed locally. This in turn has two implications:
   • The package names are different. In my StreamedPackages subfolder, there are packages named "fs20-aerosoft-airport-eddm-munich", "fs20-aerosoft-airport-eddh-hamburg", "fs20-aerosoft-airport-eddk-cologne-bonn", and "fs20-aerosoft-airport-enva-trondheim". These names differ from what is set in the corresponding XML files in the "airports" subfolder of the VDGS driver package folder, although if this were the only problem, it would be simple enough to fix by editing the XML files.
   • The folders under StreamedPackages contain only a few .fsarchive files, and no AFCAD or other files where the VDGS driver could find any devices even if it were to look in the right folder and under the right package name. Now this last problem is probably the interesting one, as I don't know whether it is in Aerosoft's power to fix it. Other than that, the solution would be to wait until MSFS 2024 finally offers an option to install packages locally (I assume the Official2020 and Official2024 subfolders are for this, as they are currently empty). There are some indications that SU 3 will bring about this possibility, so let's keep our fingers crossed...

Of course, another possibility would be for Aerosoft to allow us to transfer our MSFS Marketplace purchases to our Aerosoft accounts - then we could install the sceneries in the community folder via Aerosoft One, and Aerosoft VDGS would work under MSFS 2024 as well. (@Aerosoft: How about this option... please?)

Found a cheap workaround:
 

Find the folder  Community\aerosoft-vgds-driver\airports and select the airports you have bought via the marketplace as an example I do it for EDDK:  aerosoft_eddk.xml. Open it up with any code editor and in the 3rd line you should find: packageName="aerosoft-airport-eddk-cologne-bonn". Copy that name and create a new folder in your Community folder with that package name. If the package name is separated via a comma e.g. packageName="aerosoft-airport-edlp-paderborn,aerosoft-paderborn" then only select one of the names not both.

 

After you've created the folder, create a new file in that folder with the name "manifest.json"

which contains the following:

{

"dependencies": [],

"content_type": "SCENERY",

"title": "",

"manufacturer": "",

"creator": "Aerosoft",

"package_version": "1.1",

"minimum_game_version": "",

"release_notes": {

"neutral": {

"LastUpdate": "",

"OlderHistory": ""

}

}

}

Make sure that the version from the xml matches with the package version in the json.

Thank you very much for providing a workaround - I am now able to use Aerosoft VDGS at all airports!

Thank you so much for posting this solution! Finally got it working. For others who may have same problem, it's also worth noting that, after creating the folder and json as noted above, when Redspirrit above says 'make sure version in xml matches package version in json', it specifically means to ensure that the 'package_version' in the json matches the 'minimumPackageVersion' in the XML. Also, after doing this, when you spawn at the gate you still won't get an active VGDS until you Shift+V and find your gate in the list, then press enter.