Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

TCAS problem

Featured Replies

Dear Forumers,I've ran out of idea on how to fix my TCAS problem. I dont know what went wrong until one day when I start FS9, Flight1ATR/Wilco A320 and Wilco 737-400, the TCAS is no longer working.Not showing any traffic even though i fly nearby. I've tried re-install the FSUIPC and even register it. The problem still the same. I didnt make any modifications or install any add-on prior to this problem. I believe this happens after I "clean/defrag" my pc.2,For ATR 72, the VSI TCAS ring coloured with red/green and yellow at all times.Wilco A320/737 no AI traffic info display in the Navigation displayI've turned on the TCAS to ALT and TA/RAI hope someone can come up with solutions. Your help is much appreciated.Thank you.

did u press the traffic button on the efis?

 Intel I7 12700KF / 32 GB Ram-3600mhz / Windows 11 - 64 bit / NVIDIA GeForce RTX 3060TI / 32" Acer Monitor, Honeycomb alpha/bravo, CH rudder pedals, Tobii 5, Buttkicker, Logitech radio panel. 

First gat the latest version of FSUIPC as follows:------------------Get the base FSUIPC version from:http://www.schiratti.com/dowson.htmland then interim update from the modules link on this page:http://forum.simflight.com/forum/142-download-links/FSUIPC now self installs initially based on your registry entry for your FS path. Check that with this free utility:FSX/FS9 Registry Repair Tool (36KB) from http://www.flight1.com/view.asp?page=library-------------------Reinstall it in case something overwrote it in your modules folder.In the general section of FSUIPC.ini, after making a safe copy outside of any FS folder, be sure this statement is in there:TCASrange=0which sets it to maximum range.To verify your traffic is being generated get this application from the additional utilties section from this link:Useful additional programs[TrafficLook Updated 3rd January 2011]http://forum.simflight.com/forum/142-download-links/Install Traffic Look. You can run it after FS is started. While you are flying alt-tab to it as needed and back to FS. It will generate a table of what AI FSUIPC is seeing and reported to the application or gauge.If traffic is OK then you need to look at the integrity of the gauges themselves in each model. If the TCAS gauge has a test mode it may generate a pattern so make sure the gauge is set properly. If a third party gauge like weather radar was installed to overlay the navigation display and radar is in test mode it can generate a rainbow test pattern.The chances are if you installed a new panel or aircraft it may have overwritten a gauge or dedicated module used. One called TCASV7.dll or similar comes to mind.Also be sure your altitude and TCAS modes are set correctly as suggested by checking your radio panel and EFIS control panel (the center button on the map range) . On the 737 the navigation display should show TA ON or similar to indicate the status.

Opps i missed the part where you said it affects all aircraft, Sorry!!!

 Intel I7 12700KF / 32 GB Ram-3600mhz / Windows 11 - 64 bit / NVIDIA GeForce RTX 3060TI / 32" Acer Monitor, Honeycomb alpha/bravo, CH rudder pedals, Tobii 5, Buttkicker, Logitech radio panel. 

First gat the latest version of FSUIPC as follows:------------------Get the base FSUIPC version from:http://www.schiratti.com/dowson.htmland then interim update from the modules link on this page:http://forum.simflig...download-links/FSUIPC now self installs initially based on your registry entry for your FS path. Check that with this free utility:FSX/FS9 Registry Repair Tool (36KB) from http://www.flight1.c...sp?page=library-------------------Reinstall it in case something overwrote it in your modules folder.In the general section of FSUIPC.ini, after making a safe copy outside of any FS folder, be sure this statement is in there:TCASrange=0which sets it to maximum range.To verify your traffic is being generated get this application from the additional utilties section from this link:Useful additional programs[TrafficLook Updated 3rd January 2011]http://forum.simflig...download-links/Install Traffic Look. You can run it after FS is started. While you are flying alt-tab to it as needed and back to FS. It will generate a table of what AI FSUIPC is seeing and reported to the application or gauge.If traffic is OK then you need to look at the integrity of the gauges themselves in each model. If the TCAS gauge has a test mode it may generate a pattern so make sure the gauge is set properly. If a third party gauge like weather radar was installed to overlay the navigation display and radar is in test mode it can generate a rainbow test pattern.The chances are if you installed a new panel or aircraft it may have overwritten a gauge or dedicated module used. One called TCASV7.dll or similar comes to mind.Also be sure your altitude and TCAS modes are set correctly as suggested by checking your radio panel and EFIS control panel (the center button on the map range) . On the 737 the navigation display should show TA ON or similar to indicate the status.
Hi Sir,Thanks for your reply. I've downloaded to registry fix and installed the latest ver and reg the FSUIPC but seems it doesnt work. Here I attached the screenshot.Thx
Hi Sir,Thanks for your reply. I've downloaded to registry fix and installed the latest ver and reg the FSUIPC but seems it doesnt work. Here I attached the screenshot.Thx
That looks more like a problem with your TCAS gauge. Reinstall that first. Then establish if your AI is flying. Test your reinstalled TCAS then set it to TARA.
gauge88=Conc2k_TCAS!Logic,  345,261,1,1,trafficinfo:no volume:-200 pic:nogauge89=Conc2k_TCAS!IVSI,  420,713,123,123,fontscale:1.2 other:45 pic:no

If you want it to read from FSUIPC you must set it to "trafficinfo:no"vololiberista

3VlzBGn.jpg?1

Super VC10 into LOWI with PF3 at a cinema near you

https://www.youtube.com/watch?v=298UDyNmgUA

 

Did you run the application trafficlook.exe as advised to insure AI is present?

Did you run the application trafficlook.exe as advised to insure AI is present?
If you have FSUIPC DO NOT run trafficlook. Adjust your a/c cfg. as I have shown above. Read the TCAS manuel carefully it's all in there.vololiberista

3VlzBGn.jpg?1

Super VC10 into LOWI with PF3 at a cinema near you

https://www.youtube.com/watch?v=298UDyNmgUA

 

Thank you sir,Problem solved. I can see traffic in A330 now. if any other issue, i will post it here.Thanks for your concern.

Why not? It is just a diagnostic and does not modify anything. I'm not suggesting it be run all the time.

If you have FSUIPC DO NOT run trafficlook. Adjust your a/c cfg. as I have shown above. Read the TCAS manuel carefully it's all in there.vololiberista
Why not? It is just a diagnostic and does not modify anything. I'm not suggesting it be run all the time.
If you read the TCAS manuel it specifically states to do one or the other, and recommends that if you have FSUIPC then to use that instead.vololiberista

3VlzBGn.jpg?1

Super VC10 into LOWI with PF3 at a cinema near you

https://www.youtube.com/watch?v=298UDyNmgUA

 

Traffic Look just runs off FSUIPC. If the installation of FSUIPC itself does not interfere with the gauge in the other option then I think it is safe to check AI in Traffic Look.So the real question is whether FSUIPC and the other gauge interface conflict, not Traffic Look. I have some other gauges that do not use FSUIPC and I have had no conflicts with FSUIPC installed and examining for diagnostics with Traffic Look. Perhaps they mean the gauge configuration should not be configured for both FSUIPC and the dedicated module it uses. FSUIPC is used by many gauges and applications so just having it installed running for those others should not be a conflict.

Traffic Look just runs off FSUIPC. If the installation of FSUIPC itself does not interfere with the gauge in the other option then I think it is safe to check AI in Traffic Look.So the real question is whether FSUIPC and the other gauge interface conflict, not Traffic Look. I have some other gauges that do not use FSUIPC and I have had no conflicts with FSUIPC installed and examining for diagnostics with Traffic Look. Perhaps they mean the gauge configuration should not be configured for both FSUIPC and the dedicated module it uses. FSUIPC is used by many gauges and applications so just having it installed running for those others should not be a conflict.
That may be, but the TCAS manuel specifically states to use FSUIPC if it is installed. It is quite clear on this.vololiberista

3VlzBGn.jpg?1

Super VC10 into LOWI with PF3 at a cinema near you

https://www.youtube.com/watch?v=298UDyNmgUA

 

Correct. Agreed. I misunderstood your comment stated NOT to use Traffic Look and FSUIPC together. The gauge author then prefers to use FSUIPC. Does it register itself if the user does not have a fully registered (paid) FSUIPC?If using FSUIPC for a TCAS then (sorry if I'm repeating) after backing up FSUIPC.ini insert in the general section:TCASrange=0which sets FSUIPC to maximum range AI reporting around the user aircraft.Another way to look at AI traffic for diagnostic use is the install the FS9 Traffic Toolbox SDK. After doing so in the FS menu Bar their will be an option that when dropped down will offer Traffic Explorer, a display similar to Traffic Look. Again, this would be just to check if indeed there are AI around the user aircraft to be shown in the TCAS gauge.http://download.microsoft.com/download/f/2/8/f287f6a9-1cb3-4067-a720-0bdaf3543ff6/traffictoolbox_sdk_setup.exe

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.