Skip to content

M2A3_Commander_Turret.et exists twice in 7Cav Vehicles with the same GUID (583F19F5752BA737) #79

Description

@Smiggus

Two prefabs in 7Cav Vehicles claim the same resource GUID 583F19F5752BA737:

  • Prefabs/Vehicles/Tracked/BFV/VehParts/Turret/M2A3_Commander_Turret.et (newer; last touched by "Add Thermals to BFV" and "RHS Supply crate contents")
  • Prefabs/Vehicles/Wheeled/BTR70/VehParts/Turret/M2A3_Commander_Turret.et (older ChopShop-era copy; last touched by "BFV Thermal fix commander turret")

The two files differ by 26 lines. The BTR70-dir copy contains config the BFV-dir copy lacks:

  • RHS_TurretStabilizationComponent with m_bStabilizationEnabled 1
  • SCR_2DSightsComponent with the ISU reticle, NVG-compatible flags
  • WCS_Armament_TurretStabilizationComponent with stabilization enabled

Duplicate GUIDs inside one addon make resource resolution ambiguous: whichever file the engine indexes last wins. M2A3_II_Commander_Turret.et inherits from this GUID, so whether the Bradley II commander turret gets stabilization and the 2D sight currently depends on indexing order rather than on anything anyone chose.

Suggested resolution

  1. Decide which config is correct. Most likely: merge the stabilization and sights blocks from the BTR70-dir copy into the BFV-dir file.
  2. Delete the copy under Prefabs/Vehicles/Wheeled/BTR70/VehParts/Turret/. It sits in the wrong folder anyway (it is an M2A3 turret in a BTR70 directory).

Found during a full repo GUID integrity scan; happy to provide the scan script.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions