Bug #1926

MG-36: 30 round magazines look like 100 round drum magazines

Added by Fred_DM about 6 years ago. Updated over 4 years ago.

Status:Duplicate Start date:06/08/2009
Priority:Low Due date:09/28/2010
Assignee:- % Done:

0%

Category:Model
Target version:-
Affected ArmA II version:1.07.71750 First affected build:
Reproduced by another DH user:No First affected ArmA II version:
I am using some Mods:No Single / Multi Player?:
I am using: BIForumURL:
Reproducible for you:No NGUrl:
Related to content of DLC: WIKIurl:

Description

you can load 30 round G-36 banana magazines in the MG-36, but the magazine that is visible on the gun is still the 100 round drum magazine.

Pyrodox wrote:

This also occurs on other weapons, such as the M249 when using 30-round magazines, the Mk12 SPR when using 30-round magazines and the M4s/M16s when using 20-round magazines. I believe there is a static magazine as part of the weapon model mesh that you see on your screen, and it's not updated when changing magazine types.

Reproduction:

  1. Confirm 100 Rnd drum magazine is attached using freelook
  2. Use action menu to load 30 Rnd magazine.
  3. Use freelook to confirm attached magazine.

Expected:

30 Rnd clip to appear on the rifle

Results:

Drum magazine still shows.

CIT_1926.utes.pbo (1.6 kB) Squelch, 08/08/2009 00:55


Related issues

related to ARMA2 Community Issue Tracker - Bug #4065: MG issues - ammo belt Expired 08/27/2009
duplicates ARMA2 Community Issue Tracker - Feature #11383: Magazines should be proxies within weapon P3Ds. Assigned 06/21/2010

History

Updated by kju about 6 years ago

  • Priority changed from Low to Normal

Updated by alef about 6 years ago

  • Target version deleted (1.01.57751)

Updated by Pyrodox about 6 years ago

This also occurs on other weapons, such as the M249 when using 30-round magazines, the Mk12 SPR when using 30-round magazines and the M4s/M16s when using 20-round magazines. I believe there is a static magazine as part of the weapon model mesh that you see on your screen, and it's not updated when changing magazine types.

Updated by kju about 6 years ago

Are you sure to only have the new mag in?

Updated by kju about 6 years ago

  • Status changed from New to Feedback

Repro and mission needed please.

Updated by Fireball about 6 years ago

A video would probably better outline the repro and prove the issue.

Updated by kju about 6 years ago

It would help, yet for testing the dev needs to recreate the
scenario. If a demo mission with repro steps is available, this
is way more likely to happen.

Updated by alef about 6 years ago

  • Due date set to 06/22/2009

Please confirm latest version.

Updated by alef about 6 years ago

  • Due date changed from 06/22/2009 to 07/20/2009
  • Maxmem parameter set to Not set

Updated by Squelch about 6 years ago

  • File CIT_1926.utes.pbo added
  • Affected ArmA II version changed from 1.01.57751 to 1.03.58627

I can confirm this. Example mission attached.

Updated by Squelch about 6 years ago

  • Due date changed from 07/20/2009 to 09/08/2009
  • Status changed from Feedback to Assigned

Updated by Fireball almost 6 years ago

  • Due date changed from 09/08/2009 to 09/18/2009
  • Difficulty set to Not set

Updated by Dwarden almost 6 years ago

  • Assignee set to Dwarden

Updated by Fred_DM almost 6 years ago

just saying, it's still the same with v1.04.
not sure if it's a bug, though. seems like it just wasn't intended to show the exact magazine on the model. just thought i'd report it in case it was a bug. never mind if it is not.

Updated by kju almost 6 years ago

  • Affected ArmA II version changed from 1.03.58627 to 1.04.59026

Updated by Fireball almost 6 years ago

  • Due date changed from 09/18/2009 to 10/18/2009

Updated by Dwarden almost 6 years ago

  • Priority changed from Normal to Low
  • Reproduced by another DH user set to No

Updated by Fireball almost 6 years ago

  • Due date changed from 10/18/2009 to 12/18/2009
  • CPU set to Please specify!

Updated by kju about 5 years ago

  • Due date changed from 12/18/2009 to 07/14/2010
  • Status changed from Assigned to Feedback
  • Assignee deleted (Dwarden)
  • Affected ArmA II version changed from 1.04.59026 to 1.05.62017
  • Size of OS swap file set to Please specify!

Still valid in 1.07 / OA?

Updated by Fred_DM about 5 years ago

as of ArmA 2 v1.07, it's still valid.

Updated by kju about 5 years ago

  • Due date changed from 07/14/2010 to 09/28/2010
  • Status changed from Feedback to Assigned
  • Affected ArmA II version changed from 1.05.62017 to 1.07.71750

3x meh :)

Updated by zGuba over 4 years ago

  • Status changed from Assigned to Duplicate

In fact this is dupe to #11383

Also available in: Atom PDF