reported TSD: wrong point type assignment by identifier (possible bug)

[AstonMartinDBS]

According to a tutorial video (AFAIR it was a tutorial by Casmo, but I didn't find the resource right now) it shouldn't be absolutely necessary to select a point type on the TSD format by pressing T3/T4/T5/T6 for WP/HZ/CM/TG, when an identifier will be defined via KU. In that case the point type should be selected automatically, depending on the entered identifier.

This worked 100 % for me so far - until I recogniced, that I cannot add a BP (battle point) to my route, because the BP was wrongly identified as a TG (target) instead of a CM (control measure).

This behaviour only occurs, when the BP will be added while TSD is switched to ATK phase (BP will be incorrect identified as a TG)
CA AH-64D PointTypeAssignmentIssue.trk

When the exact same procedure is done during NAV phase, the automatic assignment of the point type works (BP will be identified as a CM) CA AH-64D PointTypeAssignmentCorrect.trk

Edited April 16, 2022 by AstonMartinDBS

[Raptor9]

2 hours ago, AstonMartinDBS said:

 it shouldn't be absolutely necessary to select a point type on the TSD format by pressing T3/T4/T5/T6 for WP/HZ/CM/TG, when an identifier will be defined via KU. In that case the point type should be selected automatically, depending on the entered identifier.

That is inaccurate behavior in the current build. It should not automatically assign the point type based on the IDENT code entered. For example, if you select WP as the point type and enter an IDENT code of a point that is a HZ, CM, or TG, the KU is supposed to flash at you indicating an invalid entry.

Yes, currently it will change the point type for you, but it should not, and I would expect this to be fixed in the future.

[AstonMartinDBS]

2 minutes ago, Raptor9 said:

That is inaccurate behavior in the current build.

2 minutes ago, Raptor9 said:

Yes, currently it will change the point type for you, but it should not, and I would expect this to be fixed in the future.

Well, thanks for clarification.

Hopefully I'll find the base of my initial claim...

[Raptor9]

Try adding the BP as specifically a CM type (don't let the system choose for you) when in ATK phase and see if you can add it to a route. If that doesn't work, it may qualify as a bug report.

[AstonMartinDBS]

1 minute ago, Raptor9 said:

Try adding the BP as specifically a CM type (don't let the system choose for you) when in ATK phase and see if you can add it to a route.

This works without problems (already tested before created this thread).

[frostycab]

You may have been able to get away with taking a bit of a shortcut like that before as you didn't have an identifier conflict. However, as was pointed out to me a while ago, not all ident abbreviations are unique to a point type. In this case BP can be a Control Measure for a Battle Point (manual p 349,) but it also appears under Targets/Threats as the ident for a Blowpipe SAM System (manual p356.) As such, if you don't make the distinction between point types then you may get the wrong result when you input the identifier.

Edited April 17, 2022 by frostycab

[AstonMartinDBS]

1 hour ago, frostycab said:

In this case BP can be a Control Measure for a Battle Point (manual p 349,) but it also appears under Targets/Threats as the ident for a Blowpipe SAM System (manual p356.)

Great catch.

I assumed the identifiers were unique.

[BIGNEWY]

reported to the team for checking. 

thanks