Fix Aerosoft VDGS “No items to display” in MSFS by checking supported gates, driver status, package paths and scenery conflicts.
Aerosoft VDGS shows “No items to display” when its airport or stand list is empty. In Microsoft Flight Simulator, that usually means no supported VDGS gate is nearby, the compatible airport package was not detected, or the VDGS driver is not running or connected. It is normally a detection problem, not an aircraft fault.
What does “No items to display” mean in Aerosoft VDGS?
The wording reports an empty result rather than identifying a specific fault. Its meaning depends on where it appears: an empty airport or product view points to missing packages, while an empty in-flight stand list usually means VDGS cannot find an active, supported unit nearby.
A modelled docking display is not proof that the stand supports Aerosoft VDGS. Some boards are static scenery objects, and even compatible airports may provide working guidance at only selected gates. Our VDGS installation and supported-gate walkthrough explains the components that must be present.
How do I fix an empty Aerosoft VDGS list?
Check gate compatibility first, then the driver connection, package location and conflicting scenery in that order.
- Confirm explicit VDGS support. The exact airport release must state that it supports Aerosoft VDGS. An Aerosoft-branded airport does not automatically qualify, and support in one edition or simulator version does not guarantee support in another.
- Test a documented VDGS stand. Load the correct airport and approach a gate specifically listed as supported. Taxi towards it along the centreline rather than testing from a runway, remote stand or an aircraft spawned directly on the stopping point. The active-unit list can remain empty outside the configured detection area.
- Check the VDGS driver on Windows. Make sure the driver is installed, up to date and running. If it reports that Microsoft Flight Simulator is disconnected, restart the driver and simulator, and check that Windows security software has not blocked the driver or its local SimConnect connection.
- Repair the matching packages in Aerosoft ONE. Verify that Aerosoft ONE has detected the correct simulator installation and that both the airport and VDGS components target the same version. Our Aerosoft ONE installation-path checks cover account, simulator-detection and duplicate-install problems.
- Verify the active content folder. MSFS 2020 and MSFS 2024 can use different package locations, and multiple PC installations make the wrong Community folder a common mistake. For a manually installed package,
manifest.jsonandlayout.jsonshould be at the package root rather than buried inside an extra folder. The desktop VDGS driver itself should not simply be moved into Community. - Remove competing airport packages. Disable duplicate scenery for the same ICAO, old versions of the airport and optional packages that replace its stands or jetways. Test with only the required airport and VDGS dependencies active; our method for isolating MSFS scenery conflicts provides a safe testing order.
- Treat MSFS 2024 as a separate installation. An older airport may render correctly in Microsoft Flight Simulator 2024 while its VDGS integration fails to register. If the problem occurs only there, use our MSFS 2024-specific VDGS checks for incompatible packages, missing drivers and incorrect content paths.
How can I tell which VDGS component is failing?
The pattern of the failure usually identifies whether the gate, airport package or driver is responsible.
| Test result | Most likely cause | What to check next |
|---|---|---|
| One gate fails, but another gate at the same airport works | The first stand is not VDGS-enabled | Use the airport’s documented supported-gate list |
| One airport fails, but other compatible airports work | Outdated, incomplete or conflicting airport scenery | Update that airport and disable duplicate scenery |
| Every supported airport fails and the driver is disconnected | Driver or SimConnect connection problem | Restart or repair the driver and check security blocking |
| Every airport fails while the driver reports connected | Wrong simulator path or missing integration package | Check Aerosoft ONE and the active content folder |
| It works in MSFS 2020 but not MSFS 2024 | Version compatibility or separate installation path | Install the package build intended for MSFS 2024 |
Does every Aerosoft airport and gate support VDGS?
No; VDGS compatibility belongs to a particular scenery release and often to particular stands within that airport. Static docking boards, default gates and unsupported third-party scenery will not populate the Aerosoft VDGS list.
The Windows driver and Community-folder fixes do not apply on Xbox Series X|S or the PlayStation 5 version of MSFS 2024. Consoles require a compatible airport and any dependency supplied through the simulator’s content system; a Windows VDGS driver cannot be added manually.
Why does the board stay idle after the list appears?
Once a VDGS item appears, an idle board is a separate positioning or aircraft-profile problem rather than the “No items to display” fault. Confirm that the correct stand is selected, approach on its centreline at low taxi speed and test with a default aircraft; if that works, the add-on aircraft’s geometry or profile needs attention.