[Bug] [2.9.5.55300] AIM-7E-2s same textures as the AIM-7E (missing black stripe on fins)

[DSplayer]

The AIM-7E-2s and newer should have a black stripe marking on its forward fins compared to the unmarked standard AIM-7E fins.

 

DCS Screenshot (7E-2 in the rear and standard 7E in the front)

Spoiler

 

IRL AIM-7E-2 or newer

Spoiler

Spoiler

 

 

IRL AIM-7E

Spoiler

Spoiler

 

Edited May 24, 2024 by HB_Painter

[DSplayer]

Looks like the model already exists in-game but the 7E-2 was erroneously just given the base 7E model on top of the bug that reverts the model back to the 7F after launch.

[HB_Painter]

Thanks for the report! We will take a look!

[SgtPappy]

On 5/22/2024 at 4:19 PM, DSplayer said:

The AIM-7E-2s and newer should have a black stripe marking on its forward fins compared to the unmarked standard AIM-7E fins.

 

DCS Screenshot (7E-2 in the rear and standard 7E in the front)

  Hide contents

 

IRL AIM-7E-2 or newer

  Hide contents

  Hide contents

 

 

IRL AIM-7E

  Hide contents

  Hide contents

 

 

Forgive me if I'm incorrect but aren't your last 2 pics E-2's (clipped wings)? I don't remember regular E's having anything but fully pointed wings wings. Maybe this is a field mod?

Edited May 24, 2024 by SgtPappy

[DSplayer]

8 hours ago, SgtPappy said:

Forgive me if I'm incorrect but aren't your last 2 pics E-2's (clipped wings)? I don't remember regular E's having anything but fully pointed wings wings. Maybe this is a field mod?

 

Es and E-2s have the same wings. The clipped-wing thing for the E-2 is something that is spread everywhere but has no actual supporting evidence.

[DSplayer]

13 hours ago, HB_Painter said:

Thanks for the report! We will take a look!

To further elaborate on this, the solution would be to replace the filename with the correct file for the the 7E2 and not to the 7E (HB_F-4E_EXT_AIM-7E2 instead of HB_F-4E_AIM7E).

 

Spoiler

 

[NRG-Vampire]

57 minutes ago, DSplayer said:

To further elaborate on this, the solution would be to replace the filename with the correct file for the the 7E2 and not to the 7E (HB_F-4E_EXT_AIM-7E2 instead of HB_F-4E_AIM7E).

The problem is a bit more complex:
Phantom modul first read entry.lua (\CoreMods\aircraft\F-4E)
and read Weapons.lua (\CoreMods\aircraft\F-4E\Entry)
but seems like the "primary" weapon data(s) (aim7_family.lua in \CoreMods\aircraft\AircraftWeaponPack) overwrite HB's weapon data(s)
wrong AIM-7E2 3D model problems comes from aim7_family.lua too
line 252 and line 302
            model  = "HB_F-4E_AIM7E",
            file  = "HB_F-4E_AIM7E";

both line(s) must be: "HB_F-4E_EXT_AIM-7E2"  in aim7_family.lua as well
 

Edited May 24, 2024 by NRG-Vampire

[DSplayer]

57 minutes ago, NRG-Vampire said:

The problem is a bit more complex:
Phantom modul first read entry.lua (\CoreMods\aircraft\F-4E)
and read Weapons.lua (\CoreMods\aircraft\F-4E\Entry)
but seems like the "primary" weapon data(s) (aim7_family.lua in \CoreMods\aircraft\AircraftWeaponPack) overwrite HB's weapon data(s)
wrong AIM-7E2 3D model problems comes from aim7_family.lua too
line 252 and line 302
            model  = "HB_F-4E_AIM7E",
            file  = "HB_F-4E_AIM7E";

both line(s) must be: "HB_F-4E_EXT_AIM-7E2"  in aim7_family.lua as well
 

 

From what I could see, the AIM-7E2 on the F-4E (and in F-4E/Entry/Weapons.lua) is technically a different from the AIM-7E2 that is declared in the aim7_family.lua (in the AircraftWeaponPack) as seen by the different CLSIDs. The AIM-7E-2 used on the F-15C (which is from the aim7_family.lua) doesn't have the issue of it reverting to an AIM-7F/M model after launch but currently uses the 7E model unlike the AIM-7E-2 on the F-4E. 

Edited May 24, 2024 by DSplayer

[Northstar98]

On 5/24/2024 at 9:34 PM, NRG-Vampire said:

The problem is a bit more complex:
Phantom modul first read entry.lua (\CoreMods\aircraft\F-4E)
and read Weapons.lua (\CoreMods\aircraft\F-4E\Entry)
but seems like the "primary" weapon data(s) (aim7_family.lua in \CoreMods\aircraft\AircraftWeaponPack) overwrite HB's weapon data(s)
wrong AIM-7E2 3D model problems comes from aim7_family.lua too
line 252 and line 302
            model  = "HB_F-4E_AIM7E",
            file  = "HB_F-4E_AIM7E";

both line(s) must be: "HB_F-4E_EXT_AIM-7E2"  in aim7_family.lua as well
 

 

This isn't the case - DSplayer is correct - the HB AIM-7Es are treated separately and have their own independent definitions.

I've made the relevant changes myself to the model and file lines for the CoreMods\aircraft\F-4E\Entry\Weapons.lua for both the AIM-7E (which also turns into an AIM-7M when launched) and the AIM-7E-2 - I've got them both appearing as they should, both when attached to the aircraft or after launch, the animations for the control surfaces also work.

Edited August 20, 2024 by Northstar98

[Northstar98]

Looks like this is still an issue as of 2.9.8.1107

1. The AIM-7E-2 uses the AIM-7E model
2. Both the AIM-7E and AIM-7E-2 transform into an AIM-7M when launched (as far as artwork goes).

Both these issues can be fixed with small edits to Weapons.lua found in CoreMods\aircraft\F-4E\Entry:

To fix issue #1, change "HB_F-4E_AIM7E" to "HB_F-4E_EXT_AIM-7E2" on line 575.

To fix issue #2, change "aim-7" to "HB_F-4E_AIM7E" on line 324 and to "HB_F-4E_EXT_AIM-7E2" on line 524.

I've attached a modified Weapons.lua file that fixes both issues (tested with both player and AI aircraft), this will however break IC so be sure to back up your original.

F-4E_AIM-7E_model.trk F-4E_AIM-7E-2_model.trk

Weapons.lua

Edited October 31, 2024 by Northstar98
Updated line numbers for 2.9.9.2280, updated fixed weapons.lua