Ok, this is driving me nuts.. I vaguely remember TCAS used to work on boeing and airbus planes.. these days i'm flying GA and not able to get TCAS to show AI on the traffic map at all.. 

I tested on the TBM and vision jet (both have G3000).. I don't have any WT or other mods other than default stuff from AAU1.. 

I tested with FSLTL and offline AI as well.. can see a ton of AI flying around but nothing on my traffic map (which is set to operate and not standby).. have tried above, below and even unrestricted options.. no joy..

have tested while flying and on ground.. different range radii.. nada.. any ideas, anybody?

I see the same problem, TCAS not showing at all and i don't know the reason..

cheers 😉

Working Title G3000 v0.6.2

Release Highlights for v0.6.2

Please refer to the changelog for a more detailed description of changes in this release.

• Enabled support for laurinius’s MSFS Traffic Service app (available on Github), which adds Offline AI traffic and SimConnect-injected traffic to the mod’s traffic systems. This feature requires that you download and install laurinius’s app separately and must be manually enabled via the mod config file.

Enabling Offline AI and SimConnect (e.g. VATSIM) Traffic

The base sim only provides information on Live AI Traffic to JS/HTML instruments. As a result, by default the mod’s traffic systems only support Live AI traffic. However, the mod provides the option to enable support for Offline AI and SimConnect-injected traffic using a third-party app. To do so, please complete the following steps:

1. Download and install laurinius’s MSFS Traffic Service app (https://github.com/laurinius/MSFSTrafficService). The app requires .NET Core 3.1 to run (https://dotnet.microsoft.com/download).
2. Change the useTrafficService setting in the mod configuration file to true.
3. Start the MSFS Traffic Service app and ensure that the service is running (this can be done before or after starting the sim).
4. (Optional) Configure the port used by MSFS Traffic Service app by changing the port number within the app itself and changing the trafficServicePort setting in the mod configuration file to match. Not recommended unless the default port (8383) is not working and you know what you are doing.

Once you have completed these steps, the mod will display and issue traffic alerts for the additional types of traffic supported by the MSFS Traffic Service app. If the mod encounters any errors retrieving traffic data from the traffic service app during a flight, it will fall back to using the default sim’s traffic data until it detects that the traffic service app is sending good data again. Lastly, it is recommended to set the useTrafficService mod configuration setting to false when you are not planning to use the traffic service app; while leaving the setting at true will not result in any errors, it does incur a small and otherwise unnecessary performance cost.

Fixes

• [General] Fixed a bug with initializing airport data with no listed runways.
• [NavMap] While in TRACK UP mode on the ground, the compass arc’s reference tick mark now correctly indicates the aircraft’s current heading instead of ground track (which cannot always be reliably calculated on the ground).
• [Traffic] Fixed an error with ground track computation for traffic contacts.
• [PFD] Airspeed altimeter speed bugs are no longer mispositioned when airspeed is below the minimum indicated airspeed.
• [GTC] Fixed a bug where the Charts page would sometimes automatically change the selected airport after closing a popup or navigating back to it from the pan/zoom control page.
•  

do we have to do something like what i pasted above from WT website.. this was for a much older version 0.6.2 where you had to do some extra stuff for TCAs to work;.. with AAU1 I thought all that should have been included.. 

6 minutes ago, vin747 said:

Working Title G3000 v0.6.2

Release Highlights for v0.6.2

Please refer to the changelog for a more detailed description of changes in this release.

• Enabled support for laurinius’s MSFS Traffic Service app (available on Github), which adds Offline AI traffic and SimConnect-injected traffic to the mod’s traffic systems. This feature requires that you download and install laurinius’s app separately and must be manually enabled via the mod config file.

Enabling Offline AI and SimConnect (e.g. VATSIM) Traffic

The base sim only provides information on Live AI Traffic to JS/HTML instruments. As a result, by default the mod’s traffic systems only support Live AI traffic. However, the mod provides the option to enable support for Offline AI and SimConnect-injected traffic using a third-party app. To do so, please complete the following steps:

1. Download and install laurinius’s MSFS Traffic Service app (https://github.com/laurinius/MSFSTrafficService). The app requires .NET Core 3.1 to run (https://dotnet.microsoft.com/download).
2. Change the useTrafficService setting in the mod configuration file to true.
3. Start the MSFS Traffic Service app and ensure that the service is running (this can be done before or after starting the sim).
4. (Optional) Configure the port used by MSFS Traffic Service app by changing the port number within the app itself and changing the trafficServicePort setting in the mod configuration file to match. Not recommended unless the default port (8383) is not working and you know what you are doing.

Once you have completed these steps, the mod will display and issue traffic alerts for the additional types of traffic supported by the MSFS Traffic Service app. If the mod encounters any errors retrieving traffic data from the traffic service app during a flight, it will fall back to using the default sim’s traffic data until it detects that the traffic service app is sending good data again. Lastly, it is recommended to set the useTrafficService mod configuration setting to false when you are not planning to use the traffic service app; while leaving the setting at true will not result in any errors, it does incur a small and otherwise unnecessary performance cost.

Fixes

• [General] Fixed a bug with initializing airport data with no listed runways.
• [NavMap] While in TRACK UP mode on the ground, the compass arc’s reference tick mark now correctly indicates the aircraft’s current heading instead of ground track (which cannot always be reliably calculated on the ground).
• [Traffic] Fixed an error with ground track computation for traffic contacts.
• [PFD] Airspeed altimeter speed bugs are no longer mispositioned when airspeed is below the minimum indicated airspeed.
• [GTC] Fixed a bug where the Charts page would sometimes automatically change the selected airport after closing a popup or navigating back to it from the pan/zoom control page.
•  

I think this has not to be done in case you use AAU1, otherwise it should be said from WT, what i do not see is, but i am not 100% shure about that..

cheers 😉

https://youtube.com/watch?v=8YztKWorgRo&si=EnSIkaIECMiOmarE

Above link is an old YouTube video from JayDee on how to get TCAS working for WT G3000. 

But we may not need the steps shown in the video anymore with new AAU update. 
 

can someone confirm if tcas is working on G3000 or G1000?

just completed a TBM flight.. I did see one AI on the TCAS finally.. granted, I was flying in a less busy area.. let me make a few more flights and see if i can spot more..