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.

how to run tcas over a lan?

Featured Replies

Just downloaded Lee's fantastic TCAS gauge. I've 2 PCs running Win XP on a LAN, I was trying to run 2 PIC sessions in multiplayer mode in the 2 machines and see how the TCAS works. It is not working although I used FSUIPC 2.95 and started AIBridge 1.0 on both machines, using either IPX or TCP protocol, only one machine will see one aircraft, not 2 and the same shows on Traffic Look as supplied by FSUIPC. Needless to say TCAS on FSUIPC is set to 40nm.Any help or experience on LAN setup appreciated.BTW, if you just run a non-multiplayer session of FS with AI traffic at 100%, you don't need AIBridge to show the traffic. TCAS gauge is a beauty, many thanks Lee.Francis Leung

>Just downloaded Lee's fantastic TCAS gauge. I've 2 PCs >running Win XP on a LAN, I was trying to run 2 PIC sessions >in multiplayer mode in the 2 machines and see how the TCAS >works. It is not working although I used FSUIPC 2.95 and >started AIBridge 1.0 on both machines, using either IPX or >TCP protocol, only one machine will see one aircraft, not 2 >and the same shows on Traffic Look as supplied by FSUIPC. >Needless to say TCAS on FSUIPC is set to 40nm. >Any help or experience on LAN setup appreciated. We never tested in that configuration that I know of because, at least I, never thought about anyone wanting to do that. Are you saying that one of the machines has the target on TCAS but the other does not? Sorry but no idea what to tell you. The issue with having to use FSUIPC 2.95 is strictly related to the targets blinking on and off, not a "can't see other aircraft" issue. That problem will be gone with the next FSUIPC release.>BTW, if you just run a non-multiplayer session of FS with AI >traffic at 100%, you don't need AIBridge to show the >traffic. TCAS gauge is a beauty, many thanks Lee. I beleave Lee addressed that in the readme file, AIBridge is not required for AI only configurations.

I've contacted Jose, the author of AIBridge and he has sent me a V2 Beta version to test. Here is the result:===1. Start FS on 1st computer P1, host multiplayer using tcp, start AIBridge, manual connect, tcp, searched with blank tcp address.2. start FS on 2nd computer P2, join multiplayer, start AIBridge, manual connect, tcp searched with blank address for host.3. P1 takes off, once airborne, is shown on P2 tcas working all right.4. However, when P2 takes off, once airborne, tcas show itself only as having a zero altitude and distance, P1 disappeared from tcas view.5. no aircraft ever shows on P1's tcas.6. when traffic look (from FSUIPC package) is run, P2 is shown on P1, both P1 and P2 are shown on P2.Any idea? Is this fixable on AI Bridge or it is a FSUIPC or Lee's panel problem? Feel free to ask me for more info.Best regards,Francis

Hi FrancisActually I don't think this is the way AIBridge is supposed to work.AIBridge is supposed to connect as a join to each machine running a FS Host session. As it is now, you are starting one host and one join session. My guess is that your two instants of AIBridge connects to the same computer, namely the one with the host session.Just my two cents ;-)

Mats Johansson
PMDG Flight Test Dept
Boeing777_Banner_BetaTeam.jpg

| Asus Z270-A | Intel i5-7600K @ 4.8 GHz OC/H2O | nVidia Geforce GTX 1070 8GB OC/O2|

That was in 1.0 then a Multiplayer only VA found me and asked if it can be done. It's done and working for them but there's some problems with Leung configuration.Personally I never imagined that someone could fly in such configuration.Jos

Ok Jos

Mats Johansson
PMDG Flight Test Dept
Boeing777_Banner_BetaTeam.jpg

| Asus Z270-A | Intel i5-7600K @ 4.8 GHz OC/H2O | nVidia Geforce GTX 1070 8GB OC/O2|

I was surprised that it seems this configuration was rare. :-(The reason that I was running 2 FS sessions over a home network is to show my son how to fly FS and it adds a bit of fun for him to follow me and I chase him, or sort of.When I saw and downloaded Lee's TCAS panel, I was eager to see how it showed our 2 planes on TCAS. It was a bit disappointed that we can see each other on FS window view but not on such a good TCAS gauge. Cheers to all,

Well, rare comparing with the 50,000 Vatsim users ;) The problem could be a lot of things just keep those maillings commning and I'm sure we will find the problem. That's why it's beta 2.0 and not 2.0 :)Jos

Many thanks to Jose for solving the problem. It was only an installation problem on my side. Now I can see myself being chased in a dog fight with tcas on . I'm sure the PIC fans out there would object to using a 767 for this :-)BTW, will the original AIBridge V1.0 still works on such LAN setting or I need your new version 2?Best regards. You make my day!

Use version 2.0 it's nicer. I think it's almost time to drop the beta and publish it.Jos

Good to hear that one is solved. AIBridge has been a very valuable addition to my collection of FS add-on software. Thanks Jose for providing it and your continued support is appreciated. Let us know here on the forum when 2.0 is available. We will be looking forward to it.And Francis, your using the in-home multiplayer session with your son sounds very reasonable to me. I hope you and your son have many hours enjoyment with it.

AIBridge 2.0 beta didn't seemed to still cause blinking TCAS targets when used with FSUIPC 2.972. FSUIPC 2.973 beta seemed to fix the blinking problem when used with AIBridge 1.0.Lee Hetherington (KBED)http://vatsim.pilotmedia.fi/statusindicato...tor=OD1&a=a.jpg

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.