Fix Aerosoft VDGS not working in MSFS 2024 by checking airport compatibility, the VDGS driver, SimConnect, Community folder and scenery conflicts.
Aerosoft VDGS usually fails in Microsoft Flight Simulator 2024 because the airport package or VDGS driver is outdated, the companion utility is not running, the scenery is loading from the wrong Community folder, or another airport package is overriding it. Update both components, remove conflicts, restart everything and test at a VDGS-equipped stand.
How do I fix Aerosoft VDGS in MSFS 2024?
The quickest fix is to verify compatibility first, then work through installation, connection and scenery conflicts in that order. Reinstalling the entire simulator is rarely necessary.
- Confirm that the airport supports MSFS 2024. An MSFS 2020 airport may appear visually correct in MSFS 2024 while its VDGS integration does not work. Check that the installed airport build explicitly supports MSFS 2024 and that the chosen gate is listed as VDGS-equipped.
- Update the airport and its VDGS component together. Close Microsoft Flight Simulator and any Aerosoft companion utility before updating. Use Aerosoft One if that is how the product was delivered, or update it through the same installer or in-sim library used for the original purchase. Mixing airport builds from different distribution channels can leave duplicate or mismatched packages.
- Check the active MSFS 2024 package location. A manually installed airport must be in the Community folder used by MSFS 2024, not the folder belonging to MSFS 2020. Our explanation of the correct package structure and active MSFS 2024 Community location covers the common extra-folder mistake. At the airport package root, files such as
manifest.jsonandlayout.jsonshould not be buried inside another identically named folder. - Remove competing airport packages. Keep only one third-party package for the airport's ICAO code while testing. Duplicate terminals, misplaced jetways or overlapping parking positions indicate a scenery conflict; use our guidance on resolving default and third-party airport conflicts rather than automatically deleting every default package. Temporarily disable other ground-service or docking-guidance add-ons as well.
- Start the VDGS companion utility. Some Aerosoft airports depend on a separate Windows driver rather than scenery alone. Do not place that application inside the Community folder. Launch it normally, allow it through security software if it has been blocked, and check for a connected status if the utility provides one.
- Check SimConnect only if the driver stays disconnected. A VDGS model that loads but never receives aircraft position or type data points towards the companion connection. Follow our steps to check and repair SimConnect without reinstalling MSFS.
- Test with a clean add-on set. Move every unrelated package out of Community, leaving only the airport and its documented dependencies, then launch MSFS normally. Safe Mode deliberately disables third-party content, so Aerosoft VDGS cannot be validated there.
- Approach a supported gate. Test by taxiing into a documented VDGS stand. Some systems do not start a normal arrival sequence when the aircraft is spawned already parked on the stop line, and runway or generic ramp starts prove nothing about VDGS operation.
What does the VDGS symptom tell you?
The failure pattern helps identify which component is missing or being overridden.
| Symptom | Most likely cause | First check |
|---|---|---|
| Default airport appears instead | Wrong folder, disabled package or incomplete installation | Confirm the active Community folder and package root |
| Airport loads but VDGS units are absent | Unsupported airport build, unequipped stand or scenery conflict | Verify MSFS 2024 support and test another documented stand |
| VDGS model is visible but blank | Driver is not running, arrival sequence has not activated or the stand is unsupported | Open the companion utility and taxi into an equipped gate |
| Display is on but data is frozen | Driver or SimConnect connection failure | Restart both applications and inspect connection status |
| Buildings, jetways or stands overlap | Two airport packages are active | Remove the duplicate scenery package |
Why is the VDGS display visible but blank?
A visible but blank VDGS usually means the scenery model loaded successfully but its guidance logic did not activate. Confirm that the driver is running, then taxi into a stand specifically equipped by that airport rather than loading directly on the parking position.
Not every gate at an Aerosoft airport has VDGS, and implementations differ between products. Some depend on aircraft proximity, an assigned stand or another activation step described in the airport manual. If the whole airport is missing rather than just the display, use our package-detection checks for Community add-ons before troubleshooting the driver.
Does Aerosoft VDGS work on Xbox or PlayStation?
A VDGS implementation that requires an external Windows driver cannot work that way on Xbox Series X|S, PS5 or PS5 Pro. Consoles cannot run the companion executable, access a Community folder or use a separate SimConnect utility.
A console edition can provide VDGS only when the publisher includes a self-contained, platform-compatible implementation in that specific airport package. Check the feature information for the console version; installing or repairing a PC driver will not enable a PC-only function on a console.
Should I reinstall Aerosoft VDGS?
Reinstall the airport and VDGS component only after a clean-package test still fails. Remove them through the same installer or in-sim library that installed them, restart MSFS, install the matching airport and driver builds, and restart once more before testing.
Do not reinstall Microsoft Flight Simulator itself unless unrelated core features are also broken. If the Aerosoft airport loads correctly but its driver remains disconnected after a verified SimConnect repair, the likely cause is a compatibility problem between that particular airport build, the VDGS component and MSFS 2024 rather than damaged simulator files.