reported Incorrect typeName for AIM9 using Unit.getAmmo()

[Webber]

Attached to the table obtained with getAmmo() applied on an F18 in late activation. The typeName should be "weapons.missiles.AIM_9", as is correct with other armaments, but currently it is "AIM_9".

The code I am creating is to set the items in the warehouses based on a template that is given by the arero in late activation. The new warehouse API is fantastic but with problems like the one mentioned above it becomes a half-baked tool.

The problem mentioned above is difficult to solve even by cross-referencing the data with getResourceMap (attached file)/DBUG_getAmmo.luaDBUG_getResourceMap_wsType.lua

Edited November 20, 2023 by Webber

[Flappie]

Hi, I'm bad at scripting. Can you please attach a miz file demonstrating the issue?

[Webber]

15 hours ago, Flappie said:

Hi, I'm bad at scripting. Can you please attach a miz file demonstrating the issue?

Hi, thanks for the reply. As soon as I can I will attach the mission but this issue can only be "understood" by those who know the code: the mission I will attach only has an f18 in late activation which does not present gameplay problems. This issue is visible only by executing the Unit.getAmmo() function, which I remind you is a function of the native code of DCS (SSE: Simulator Scripting Engine), which returns a table which must then be printed to be displayed. The printed table is one of the attachments above, have you had a chance to open and read them??

So I've already proven the issue. In the next few days I will attach the mission anyway.

 

Edited November 21, 2023 by Webber

[Flappie]

4 hours ago, Webber said:

In the next few days I will attach the mission anyway.

Thank you. I can guarantee you that the fix will come way faster if I bring a mission to devs. It's how things work here, for the most part.

[Webber]

This is the file .miz.. Script inside, enjoy..
null

dcs_issue.miz

[Flappie]

Many thanks.  It seems like it does this with all AA missiles:

I'll keep digging, then I'll report.

[Webber]

Not all, i think only with fox 2 category, with 120c work

Edited November 21, 2023 by Webber

[Webber]

@Flappie 

 

[Flappie]

On 11/21/2023 at 9:07 PM, Webber said:

Not all, i think only with fox 2 category, with 120c work

R-77 and R-27ER are also affected.  Issue reported.

I'll check that other thread of yours.

[Webber]

Hello @Flappie how are you?
I inform you that the bug has not yet been resolved.

Edited May 29, 2024 by Webber

[Flappie]

Hello. I'm fine, thank you. How are you?

Yes, I know this bug is still waiting for a fix. Unfortunately, it's not the only one in the queue, and it's not a game breaking bug either, which is why it is low priority.