PLEASE FOLLOW THE STEPS DESCRIBED BELOW, IN ORDER, ONE AT A TIME
DON'T SKIP ANY
Thanks !

Lighted Taxi Paths is a feature only available on Microsoft Flight Simulator 2020 and 2024 currently. We are considering bringing this to XPlane 11/12 at a later date. If you are running FS20/FS24 and it does not seem to be working, below are some troubleshooting steps you can try to get it running before requesting support in discord.

Confirm the setting in the Pilot Portal is not set to ‘Never’ for taxi path.

Visit the pilot portal at https://portal.sayintentions.ai/

Navigate to Settings from the left menu and then under the Misc section, locate ‘Taxi Assist’

If the “When” is set to ‘Never’, then taxi paths can never be shown, even if you ask for them! Set it to either ‘Request’ or ‘Always’ depending on your preference. Feel free to customise the style and color to suit your preferences too.

Confirm that you are asking for the right thing if it’s on request

If you have chosen the “When” setting to be ‘request’, you must also say something appropriate for the ATC to understand you wish to see the taxi path. 

It’s recommended to either request PROGRESSIVE taxi in your initial taxi request, e.g. 

“Manchester Ground, Speedbird-Eight-Three-Alpha, Request Progressive Taxi”

Or make a separate request after your taxi request to “Show taxi path”. 

You may also indicate verbally what style to use and override your default at this stage, e.g. “Show taxi path with big red arrows” if you wish.

Confirm that SayIntentions-Simobjects-Optional is installed and visible in your community folder

SayIntentions includes a system that should automatically install these files and create a Symbolic Link to your simulator(s) Community Folders, however sometimes an over-excited antivirus or firewall can prevent normal operation of this process.

You should navigate in the Windows File Explorer to just double check the files are visible in your community folder. The location of this folder can vary depending on whether you are using MSFS 2020, or 2024, whether it’s the steam version or the MS Store version and possibly even if you have customised the location yourself at some stage. 

Sadly we cannot be detailed on where to find it if you have customised the location yourself, however the standard locations are as follows:

For MSFS 2020 (Steam Edition):
C:\Users\[Your User name here]\AppData\Roaming\Microsoft Flight Simulator\Packages\Community
(or as a special alias you can paste in to the path bar in File Explorer):
%appdata%\Microsoft Flight Simulator\Packages\Community

For MSFS 2020 (MS Store Edition):
C:\Users\[Your User name here]j\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\
(or as a special alias you can paste in to the path bar in File Explorer):
%localappdata%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\

For MSFS 2024 (Steam Edition):
C:\Users\[Your User name here]\AppData\Roaming\Microsoft Flight Simulator 2024\Packages\Community
(or as a special alias you can paste in to the path bar in File Explorer):
%appdata%\Microsoft Flight Simulator 2024\Packages\Community

For MSFS 2024 (MS Store Edition):
C:\Users\[Your User name here]j\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community
(or as a special alias you can paste in to the path bar in File Explorer):
%localappdata%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community

Once you have located the community folder, look for the SayIntentions-SimObjects-Optional sub folder within:


You might notice these appear with a little ‘arrow’ in the corner of the folder icon, this denotes a symbolic link.

Please ensure you are checking the correct folder for the version of the simulator you are actually using. It’s quite possible to end up in the wrong one if you have both 2020 and 2024 installed simultaneously.

Confirm you have restarted the simulator at least one time since the SimObjects were installed

Both Microsoft Flight Simulator 2020 and 2024 only read the contents of that folder once during start up. It is possible that if the files are present, they were added AFTER the simulator first started up, please try restarting the simulator once and testing the lighted taxi path feature again. This solves the issue surprisingly often.

Check the My Library/Content Manager in FS24/FS20 and that the SimObjects are listed and not disabled.

Although very rare, it is possible that the simulator itself has set the package to be disabled. You can verify this by navigating to the correct menu of the simulator, searching for SayIntentions and verify the package is listed and has not been disabled.

For MSFS 2020 this is on the second tab of the main menu ( “Profile”), under something called the “Content Manager”:

For FS2024 this is under the ‘Marketplace’ Option, then the ‘My Library’ Option:

We are looking for the ‘SAYINTENTIONS.AI OPTIONAL MODELS” here. Ensure it is not disabled:

If it is, tick the small box in the bottom left corner and then choose the ‘Enable’ button in the right bottom right of your screen.

Try asking for a follow me car to confirm that sidecar is functioning

While rare, it’s possible that an important component known as ‘SayIntentions Sidecar’ has not been installed correctly or is not able to communicate correctly with the cloud servers. A quick way to try to confirm if this is working is to test other features that are not reliant on the SimObject files being installed, e.g. try asking ATC: “Request follow me vehicle” after your taxi request and see if a truck appears driving along the taxi route in front of you.

The SayIntentions pushback feature would also demonstrate that sidecar is active and working without requiring any other files to be installed too.

If these functions do not appear to be working, continue with the last two diagnosis steps below:

Confirm that sidecar is installed

Similar to the steps we performed before to verify the SimObjects files are installed, we will now check if the sidecar component is installed. This can be found in the SayIntention’s main folder at this location:
C:\Users\[Your User Name]\AppData\Roaming\SayIntentionsAI\SayIntentionsAI\sidecar

(or using the special alias):
%appdata%\SayIntentionsAI\SayIntentionsAI\sidecar

Verify that folder exists and all files (especially si_sidecar.exe) are present:

Confirm that sidecar is running in the task manager

If the sidecar files appear to be present and correct, let’s verify it is actually launching successfully by opening the windows task manager. This can often be achieved by right clicking on a blank area of your task bar or the windows start menu logo and choosing ‘Task Manager’ from the list:

Once task manager has opened, under the ‘processes’ tab on the side, you can use the top search bar to look for sidecar and verify if it’s in the list:


NOTE: This will only be present if the SayIntentions client is running and your flight is initialized, if the main client is noting that it is waiting for the simulator, then this component most likely will not be running and that is normal, intended behaviour.

Ensure that it is present and remains stable in the list. If you see it disappear and reappear every few seconds, you may require additional support help.

What to do if the SimObjects or Sidecar appear to be missing:

The most common reason, by far, for this to happen is an overzealous antivirus or firewall system has blocked, deleted or refused internet access to a key file known as sidecar_updater.exe

This file can normally be found in the main SayIntentions Folder:

C:\Users\[Your User Name]\AppData\Roaming\SayIntentionsAI\SayIntentionsAI\

(or using the special alias):
%appdata%\SayIntentionsAI\SayIntentionsAI\

While we cannot provide specific instructions for the multitude of different AntiVirus and firewall security solutions out there, we recommend consulting the documentation or help for any such products and ensure that this file has not been blocked or “Quarantined”, and if necessary add specific exclusion rules to the file in your firewall and/or AntiVirus software.

If none of the above helped, please contact us for additional support on our discord server