Skip to content

EDIT SOLUTION FOUND WORKING ! Aerosoft VDGS in Microsoft Flight Simulator 2024 | EBBR ENGM NZCH | "NO ITEMS TO DISPLAY" | Not Working | No VDGS

Featured Replies

Hi all. I need some help. It would be much appreciated.

 

I am trying to use Aerosoft VDGS in Microsoft Flight Simulator 2024.

I am using Windows 11 Home

I have installed everything using Aerosoft One only.

I have downloaded the three optional dependencies from Aerosoft One.

All the airports were purchased on the Aerosoft Store. 

I have restarted the computer multiple times.

 

“Left Shift + V” opens the VDGS UI menu. 

This shows "aerosoft-vdgs-driver" window pop up and displays 
"NO ITEMS TO DISPLAY"

It seems there is no airports in RANGE. 

 

This is despite loading up at EBBR, ENGM and NZCH trying all available start locations at the airport. 

The "T1 and T2 safe dock systems" seem to be in the scenery but they are blank and black displaying no information.

I'm unable to get Aerosoft VDGS working in Microsoft Flight Simulator 2024 on 11/02/2025 D/M/Y.
I am using the latest version of Microsoft Flight Simulator STEAM VERSION. 
I've installed everything using "Aerosoft One" latest version available. 
I've uninstalled and reinstalled everything again as it didn't work the first time.
I do not have any virus protection installed so no AVAST or NORTON or BITDEFENDER is installed.

 

I have these airports 
aerosoft-airport-ebbr-brussels
aerosoft-airport-engm-oslo
nzasimulations-airport-nzch-Christchurch
I understand Aerosoft VDGS works with these airports.

 

It seems there is support for Microsoft Flight Simulator 2024
"aerosoft-vdgs-driver
added:    support for MSFS 2024
v.1.9.1.0 (07.10.2024)"

 

I've opened up the file "aerosoft-vdgs-driver-log.ini" with a text editor. In there, set "Verbose=1" and saved the file.

 

See the attached file "aerosoft-vdgs-driver-log" text file.

"----TIME----|----MSG----
18:49:29 | Path to module: 'G:\Community\Community\aerosoft-vdgs-driver\'
----------------------------------------------
----TIME----|----MSG----
18:49:29 | Path to community: 'G:\Community\'
----------------------------------------------
----TIME----|----MSG----
18:49:29 | Path to official: 'G:\Official\'
----------------------------------------------
----TIME----|----SENDER----|----MSG----
18:49:29 | CurrentDialog | 23 airports found
----------------------------------------------
----TIME----|----SENDER----|----MSG----
18:49:29 | CurrentDialog | Determining airports...
----------------------------------------------
----TIME----|----SENDER----|----ERRORMSG----
18:49:29 | CurrentDialog | Airport 'NZCH' COULD NOT be verified, reason: 'PACKAGE_NAME_UNVERIFIED'
----------------------------------------------
----TIME----|----SENDER----|----MSG----
18:49:29 | CurrentDialog | 0 airports are in range
----------------------------------------------
----TIME----|----MSG----
18:49:39 | Opening or closing VDGSDialog (PRESELECT)...
----------------------------------------------
----TIME----|----SENDER----|----MSG----
18:49:39 | PreselectDialog | Creating instance...
----------------------------------------------
----TIME----|----SENDER----|----MSG----
18:49:40 | PreselectDialog | Destruction
----------------------------------------------
----TIME----|----MSG----
19:30:21 | Opening or closing VDGSDialog (CURRENT)...
----------------------------------------------
----TIME----|----SENDER----|----MSG----
19:30:21 | CurrentDialog | Getting airports...
----------------------------------------------
----TIME----|----SENDER----|----MSG----
19:30:21 | CurrentDialog | 23 airports found
----------------------------------------------
----TIME----|----SENDER----|----MSG----
19:30:21 | CurrentDialog | Determining airports...
----------------------------------------------
----TIME----|----SENDER----|----ERRORMSG----
19:30:21 | CurrentDialog | Airport 'ENGM' COULD NOT be verified, reason: 'PACKAGE_NAME_UNVERIFIED'
----------------------------------------------
----TIME----|----SENDER----|----MSG----
19:30:21 | CurrentDialog | 0 airports are in range
----------------------------------------------
----TIME----|----MSG----
19:30:47 | Opening or closing VDGSDialog (PRESELECT)...
----------------------------------------------
----TIME----|----SENDER----|----MSG----
19:30:47 | PreselectDialog | Creating instance...
----------------------------------------------
----TIME----|----MSG----
19:33:08 | Opening or closing VDGSDialog (CURRENT)...
----------------------------------------------
----TIME----|----SENDER----|----MSG----
19:33:08 | CurrentDialog | Getting airports...
----------------------------------------------
----TIME----|----SENDER----|----MSG----
19:33:08 | CurrentDialog | 23 airports found
----------------------------------------------
----TIME----|----SENDER----|----MSG----
19:33:08 | CurrentDialog | Determining airports...
----------------------------------------------
----TIME----|----SENDER----|----ERRORMSG----
19:33:08 | CurrentDialog | Airport 'EBBR' COULD NOT be verified, reason: 'PACKAGE_NAME_UNVERIFIED'
----------------------------------------------
----TIME----|----SENDER----|----MSG----
19:33:08 | CurrentDialog | 0 airports are in range
----------------------------------------------"
 

See the attached file "community folder" showing

that the directories are named the following and have not been changed. 
aerosoft-airport-ebbr-brussels
aerosoft-airport-engm-oslo
nzasimulations-airport-nzch-Christchurch

aerosoft-vdgs-driver
aerosoft-modellib-vdgs
aerosoft-data-exchange

 

The file "aerosoft_ebbr" found under "Community\aerosoft-vdgs-driver\airports" shows

 

" <Airport icao="EBBR" iata="BRU" name="Brussels Airport" latitudeInDeg="50.900278" longitudeInDeg="4.483611" activeInRangeInNM="10" version="1.0" packageName="aerosoft-airport-ebbr-brussels" minimumPackageVersion="0.7.0"> "

 

" <Airport icao="ENGM" iata="OSL" name="Oslo Airport, Gardermoen" latitudeInDeg="60.202778000000002" longitudeInDeg="11.083888999999999" activeInRangeInNM="10" version="1" packageName="aerosoft-airport-engm-oslo" minimumPackageVersion="0.8.0"> "

 

"<Airport icao="NZCH" iata="CHC" name="Christchurch International Airport" latitudeInDeg="-43.4876" longitudeInDeg="172.53739999999999" activeInRangeInNM="30" version="1" packageName="nzasimulations-airport-nzch-christchurch" minimumPackageVersion="0.1.6">
        <Group displayName="Domestic"> "

 

The package name matches the directory name and it is in the same community folder. 

 

The scenery is loading up and working in Microsoft Flight Simulator 2024 with no problems but the VDGS is not working. 
There is nothing displayed on the screens when loading 

 

I have read the user manual found here "Community/aerosoft-vdgs-driver/Manual_Aerosoft_VDGS_Module_web.pdf"

 

I see there is a post 
"https://forum.aerosoft.com/index.php?/topic/179571-no-vdgs-in-msfs-2024-airports/"
but it provides no answers as to how they got it working but it indicates it is possible to do so. 

 

I have read everything I could find on AEROSOFT VDGS from GOOGLE searching for answers before posting here.

 

I do not have Microsoft Flight Simulator 2020 installed. 

 

Is is possible to get any help, advice, comments, ideas on how to get Aerosoft VDGS working at these airports ?

 

aerosoft-airport-ebbr-brussels
aerosoft-airport-engm-oslo
nzasimulations-airport-nzch-Christchurch

 

I would love to purchase all the supported airports for Aerosoft VDGS but I need to get it working first on at least one airport.

 

Thank you.

 

I will report back here immediately and update you if I find any fix or solution and share it with you to help the community. 

 

community folder.jpg

aerosoft-vdgs-driver-log.log

no items.jpg

Solved by TatianaLuna

  • TatianaLuna changed the title to Aerosoft VDGS in Microsoft Flight Simulator 2024 | EBBR ENGM NZCH | "NO ITEMS TO DISPLAY" | Not Working | No VDGS
  • Author
  • Solution

I have found a fix solution. It is working with Microsoft Flight Simulator 2024. 

 

You will notice above

 

"18:49:29 | Path to module: 'G:\Community\Community\aerosoft-vdgs-driver\'
----------------------------------------------
----TIME----|----MSG----
18:49:29 | Path to community: 'G:\Community\'"

 

So what I had to do was copy the airport directory that was in the Community folder at location 

G:\Community\Community\

 

So this folder. 

aerosoft-airport-ebbr-brussels

 

And I have copied it to 

G:\Community\

 

So there is two copies of it one in G:\Community\ and another in G:\Community\Community\

 

Microsoft Flight Simulator 2024 is using the copy in G:\Community\Community\

and

Aerosoft VDGS is using the copy in G:\Community\

 

I now have "EBBR - Brussels Airport: 101 systems showing."

 

I need to test with all airports but at this stage it appears to be working.

 

If I put the airport ONLY in G:\Community\ the scenery will not load in the game as that is not the location of the Community folder that MSFS 2024 shows under 

Settings, Advanced, Developer Mode, Tools, Virtual File System, Packages Folders, Open Community Folder

 

SOLVED.

 

I can confirm that Aerosoft VDGS works with Microsoft Flight Simulator 2024

 

Thank you Aerosoft and team for creating Aerosoft VDGS.

  • Author

Update. I have now confirmed and tested that it is working at all these airports.

 

aerosoft-airport-ebbr-brussels
aerosoft-airport-engm-oslo
nzasimulations-airport-nzch-Christchurch

 

I can confirm that Aerosoft VDGS works with Microsoft Flight Simulator 2024.

  • TatianaLuna changed the title to EDIT SOLUTION FOUND WORKING ! Aerosoft VDGS in Microsoft Flight Simulator 2024 | EBBR ENGM NZCH | "NO ITEMS TO DISPLAY" | Not Working | No VDGS
  • 1 year later...

I had the same problem and this post helped me. Now i've got all stuff working

Thanks a lot!

Create an account or sign in to comment

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use

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.