_TCAS_DATA id = 0???

[Bryn]

Hi Peter,

I'm grabbing the TCAS data tables and am stumbling across a bunch of AI that have id set to zero (even though idATC is valid and the plane exists in the sim). I should add that I'm setting range to unlimited at E068 and F068 prior to grabbing the table.

Have you seen this before - that is, aircraft in the table with ids set to zero? It's a pain, because I can't do anything with them (for instance, the program I have deletes AI with the same callsign and flight number as me).

eg,

_ALL_AI thisScan (_ALL_AI is a collection of the 4 tcas tables)

FSUIPC_Read(0xF080, 3840, &thisScan.tcas1Air, &dwResult)

process

loop through 96 slots,

cout << thisScan.tcas1Air.id;

For me, some of these have idATCs for planes that are active and ids set to 0.

Cheers,

Bryn.

[Pete Dowson]

I'm grabbing the TCAS data tables and am stumbling across a bunch of AI that have id set to zero (even though idATC is valid and the plane exists in the sim). I should add that I'm setting range to unlimited at E068 and F068 prior to grabbing the table.

As it clearly states in the documentation, entries with zero ID are empty slots. the data in the other fields would have been relevant to the previous occupant. FSUIPC only sets the ID to zero when an aircraft disappears, it is inefficient for it to clear al the rest of the stuff, not just for it but for any WideFS clients it is being sent to.

For me, some of these have idATCs for planes that are active and ids set to 0.

If they are active still they will be present in another slot. They may have temporarily disappeared, and got another slot when they reappeared. Please simply ignore all slots with a zero ID. That's the only indicator of an empty slot.

Pete