lc0277 Posted June 1, 2006 Report Share Posted June 1, 2006 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 More sharing options...
Pete Dowson Posted June 1, 2006 Report Share Posted June 1, 2006 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 More sharing options...
lc0277 Posted June 1, 2006 Author Report Share Posted June 1, 2006 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 More sharing options...
lc0277 Posted June 1, 2006 Author Report Share Posted June 1, 2006 read echo-eight-charlie :? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now