X-Plane troubleshooting

The XPGuard menu is missing

Check that the folder is Resources/plugins/XPGuard, not a nested copy. Keep the platform folders and resources together, then restart X-Plane. Check Log.txt in the X-Plane folder for plugin-loading messages. On macOS, follow the quarantine steps if the download was blocked.

No lights appear

Open the control panel and confirm the server, VATSIM connection, airport, and Publisher. Test on the ground. Above about 1,000 ft AGL, XPGuard enters standby. Ask whether the controller is using XPGuard and has that light group active. Use Reload (re-detect airport + light objects) if the airport did not update after moving.

VATSIM detection fails

Confirm your pilot client is connected under the current flight’s callsign. Force connection is a fallback for failed detection; it does not connect you to VATSIM. Your own FTG session still needs a detected pilot client. Other traffic’s visible greens do not prove that your own session is working.

Only FTG is missing

Confirm the request was accepted and the controller sent a route. The airport needs a published network. A red bar or paused guidance can stop the greens. If original greens obscure the assigned route, check the launcher’s scenery-light settings.

Lights are misplaced

Check Publisher before using a height offset. Use contribution mode for a sideways map correction. Tell ATC if the route leads toward pavement your scenery does not have.

Collect the log

Set Log level → Debug, reproduce the issue once, then return to Info. X-Plane’s Log.txt contains messages marked XPGuard: with UTC times. Include your plugin version, scenery, airport, and steps in the problem report.