fixed PFZ no longer affect FCR target prioritisation

[AvroLanc]

As of the latest patch BAM PFZ's no longer affect the FCR target priority order.

If you create an active PFZ, it should be the top priority for selecting the NTS target. Instead the logic seems to ignore the PFZ completely. This USED to work perfectly...........rather like C-scope used to. This patch hasn't been kind to the AH-64.

No Fire Zone's NFZ's, continue to work correctly.

Thanks.

AH64 PFZ.trk

[Raptor9]

This was already reported internally; unfortunately it was discovered during final testing right before the most recent update went out and we were not able to fix it in time.

In the interest of specificity, the bug isn't really about the activated PFZ as much as the fact that the NTS (and ANTS) are being designated immediately upon initial target detection within the first scan cycle. When a scanburst is initiated, the NTS, ANTS, and the entire target ranking process should only be finished when a) the first scan cycle within the scanburst has been completed or b) the scanburst is aborted by the crewmember in any way. As a result, currently the FCR is not getting a chance to complete its first full scan cycle and getting a full look at the entire scan volume (to include all targets inside and outside the activated PFZ), its just putting the NTS on one of the first targets it sees, and the entire ranking process is thrown out of whack. The bug doesn't affect the NFZs since those areas are occluded from the FCR page entirely.

But thank you for the report, in case others find similar behavior in the short term. 

[AvroLanc]

58 minutes ago, Raptor9 said:

This was already reported internally; unfortunately it was discovered during final testing right before the most recent update went out and we were not able to fix it in time.

In the interest of specificity, the bug isn't really about the activated PFZ as much as the fact that the NTS (and ANTS) are being designated immediately upon initial target detection within the first scan cycle. When a scanburst is initiated, the NTS, ANTS, and the entire target ranking process should only be finished when a) the first scan cycle within the scanburst has been completed or b) the scanburst is aborted by the crewmember in any way. As a result, currently the FCR is not getting a chance to complete its first full scan cycle and getting a full look at the entire scan volume (to include all targets inside and outside the activated PFZ), its just putting the NTS on one of the first targets it sees, and the entire ranking process is thrown out of whack. The bug doesn't affect the NFZs since those areas are occluded from the FCR page entirely.

But thank you for the report, in case others find similar behavior in the short term. 

Thanks for your reply. Yes, I noticed that the NTS was being assigned immediately too, and suspected that was wrong. I couldn't fully assess the bug though in my limited time available to test, it was only clear that PFZ's are not working, despite being fine in the past.

It's actually super irritating that previously working features in this module are breaking with almost every patch. Admittedly it's complicated but I thought the new 4-6 week patch cycle was supposed to be an improvement. 

Anyway, thanks for your explanation Raptor.