Jump to content
The simFlight Network Forums

TCAS Table size


Recommended Posts

Hello everyone,

The total TCAS table size accessible in FSUIPC is 192 (96 air + 96 ground), but I've seen that more than 192 AI aircraft can be animated at the same time. With traffic explorer of TrafficToolbox.dll I can observe up to 250 aircrafts (and maybe many more).

My question is, can I also access these informations with fsuipc ? Is it a limit of fsuipc offset adressing or are is TrafficTool using a different way to get informations ?

With some 'real' AI traffic and good afcads, the total number of sleeping planes on ground can be very high, many more than 96

Thanks.

Link to comment
Share on other sites

The total TCAS table size accessible in FSUIPC is 192 (96 air + 96 ground), but I've seen that more than 192 AI aircraft can be animated at the same time. With traffic explorer of TrafficToolbox.dll I can observe up to 250 aircrafts (and maybe many more).

Yes, I know. Sorry, the FSUIPC limits are a function of the design and won't be changed now.

But FSUIPC does include the nearest 96 in the air and the most significant 96 on the ground (nearest active, rather than sleeping). I haven't come across any aplication that cannot be satisfied with that.

My question is, can I also access these informations with fsuipc ?

No, sorry.

is TrafficTool using a different way to get informations ?

It uses the same interfaces, but it isn't limited to a form of memory mapping to support the communication of this information.

With some 'real' AI traffic and good afcads, the total number of sleeping planes on ground can be very high, many more than 96

Yes, but active planes are more important for most purposes -- extra sleeping ones are the first to be lost off the end of FSUIPC's list.

What exactly is your problem?

Regards,

Pete

Link to comment
Share on other sites

Thanks Pete!

I have no problem in particular, just writing a radar panel for an AWACS plane. Anyway the main issue is probably the AI range. The radar of an E-3A has a range of ~200 nm which is far beyond the limits of simulated AI planes (~60 nm around user plane). This is internal FS settings that cannot be changed.

For a ground surveillance model (like E-8) the range is less (150 nm). But since it cannot see motionless targets, only "active" FS planes would be of interest. No problems here too.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.