prtkilo

aiseparation resolving conflicts now (without that parameter) with 4957f, in both p3d 3.3 and 3.4. On other note could you tell more on the simconnect not reporting ai addition/removal? I am using UT2 and start having some duplicate and dead (which never move) AIs parked after letting sim run for a while. UT2 log shows unrecognized_id error when this happens and seems to create AIs that it is unable to track. Sometimes a couple of AIs and their plans also get mixed up. I was able to trigger these by overloading the cpu by running a file compression program in background that caused heavy stutter in the sim. If so is this something that could be fixed by LM in a future release? I have nagle disabled through simconnect.cfg but not sure if it has improvement as I still get these problems sometimes.

Running p3d 3.3.5, with fsuipc 4957d aiseparation did not resolve conflicts, but did after adding UseAIClient=No entry. Ran TrafficLook which showed traffic in both cases.

Installed p3d 3.3.5 client again and found that aiseparation is able to resolve conflicts with fsuipc 9.955 but not with 9.957c. Doesn't with either, on p3d 3.4. So something must have changed in both fsuipc and p3d.

I think I mixed up Traffic ID with TCASid then. In any case this should not be the issue area since there hasn't been any change to the aiseparation-fsuipc interface so the utility must be calling fsuipc correctly as before. Sorry for the confusion there, I just meant to say aiseparation does not attempt to maneuver AI in flying mode which would involve multiple commands and difficult to narrow down to the problem one as you mentioned. But it is using slew mode which should make it simpler. Unfortunately I do not have experience working with fsuipc or simconnect commands so I will wait till your able to get back and look at it again, or someone knowledgeable in this matter may chip in.

Found the TrafficLook utility, running it shows the airborne traffic normally as does the aiseparation table. However the IDs shown in the latter are of the type "&HFFFFFF7C" whereas TrafficLook shows the AI flight name as the ID, which is shown in the aiseparation utility under "flight" column. But this shouldn't indicate any problem as it has been like that since before. The aiseparation utility does not try to fly/control AI in any way, only aims to shift it to desired distance. This is what the aiseparation readme says: "the planes are slewed backwards for a period of time calculated upon the speed of the SLEW and the distance to be moved" (capitals as original in the manual), which hints a simple slew might have been employed.

AIseparation is an old utility (last updated 2005) so pretty sure it works through fsuipc only. It has a table for showing AI in 40-50 mile vicinity and another to show conflicts (based on set criteria). AI information (including ID) is being shown normally in its tables as before, only that it is not doing anything to the conflicts i.e. aircraft are not getting slewed away to maintain required set distance. I haven't looked into TrafficLook but I think traffic is being detected fine, only the control message not seem to be reaching p3d.

Hi I just updated to p3d 3.4 and fsuipc 9.957c (free function), but after update aiseparation seems not be resolving any conflicts. Prior to updating to 957c I ran briefly with only p3d updated to 3.4 and had the same issue. Previously I was using p3d 3.3.5 and fsuipc 9.955 where aiseparation mostly worked, occasionally failing to act on some conflicts. Would appreciate any info on resolving this. Regards