Page MenuHomeFeedback Tracker

class V_PlateCarrierGL_rgr using two different models
Closed, ResolvedPublic

Description

class V_PlateCarrierGL_rgr: Vest_NoCamo_Base
{

		scope = 2;
		displayName = "$STR_A3_V_PlateCarrierGL_rgr0";
		picture = "\A3\characters_f\Data\UI\icon_V_plate_carrier_2_CA.paa";
		model = "\A3\Characters_F\BLUFOR\equip_b_vest01.p3d";
		class ItemInfo: ItemInfo
		{
			uniformModel = "\A3\Characters_F\BLUFOR\equip_b_vest02.p3d";
			containerClass = "Supply120";
			mass = 80;
			armor = "5*0.8";
			passThrough = 0.4;
		};

};

Details

Legacy ID
1135295299
Severity
None
Resolution
Fixed
Reproducibility
Always
Category
Config
Additional Information

Type: Public Beta
Branch: Development
Version: 0.77.109067

Event Timeline

surpher edited Steps To Reproduce. (Show Details)Aug 16 2013, 12:15 PM
surpher edited Additional Information. (Show Details)
surpher set Category to Config.
surpher set Reproducibility to Always.
surpher set Severity to None.
surpher set Resolution to Fixed.
surpher set Legacy ID to 1135295299.May 7 2016, 4:03 PM
surpher added a subscriber: surpher.

class V_PlateCarrier2_rgr has the same problem, it is inheriting model = "\A3\Characters_F\BLUFOR\equip_b_vest01"; from class V_PlateCarrier1_rgr.

Edit: Also has the wrong displayName.

Although not currently used by any unit this helmet has the same model uniformModel problem.

class H_HelmetB_camo: H_HelmetB
{

		model = "\A3\Characters_F\BLUFOR\headgear_b_helmet_camo";
		hiddenSelections[] = {"camo1","camo2"};
		hiddenSelectionsTextures[] = {"\A3\Characters_f\BLUFOR\Data\equip1_co.paa","\A3\characters_f\common\data\ghillie2_co.paa"};
		class ItemInfo: HeadgearItem
		{
			uniformModel = "\A3\Characters_F\BLUFOR\headgear_b_helmet_ballistic";
			modelSides[] = {3,1};
			hiddenSelections[] = {"camo1","camo2"};
		};

};

Logan added a subscriber: Logan.May 7 2016, 4:03 PM

Thank god someone has noticed this issue it has happened twice to me , both times after a larger update , basically reversing the 3D models on the light , heavy and GL plate carriers for the BLUFOR.(PS I have added a photo of what the issue is so you are not alone on this , also there is no way to fox this)

Why does this even matter? The GL carrier doesn't even have grenades on it, both for this and for opfor and indfor.

Sirloin added a subscriber: Sirloin.May 7 2016, 4:03 PM

InstaGoat: It's basically an aesthetic thing, but the difference in capacity between the Carrier Lite and the Carrier Rig can be an issue if you want your soldiers to have a particular look, but still carry enough gear.

Also the Coyote variant of the Lite Carrier appears correctly (though it is green).

Claimed fixed...

http://forums.bistudio.com/showthread.php?149636-Development-Branch-Changelog&p=2523846&viewfull=1#post2523846

I advise that this is re-tested and confirmed so the ticket can be closed.

Confirmed Fixed.

class V_PlateCarrierGL_rgr: Vest_NoCamo_Base
{

		scope = 2;
		displayName = "$STR_A3_V_PlateCarrierGL_rgr0";
		picture = "\A3\characters_f\Data\UI\icon_V_plate_carrier_2_CA.paa";
		model = "\A3\Characters_F\BLUFOR\equip_b_vest02.p3d";
		class ItemInfo: ItemInfo
		{
			uniformModel = "\A3\Characters_F\BLUFOR\equip_b_vest02.p3d";
			containerClass = "Supply120";
			mass = 80;
			armor = "5*0.8";
			passThrough = 0.2;
		};

};

The config file might be fixed but the visual bug is not. The Carrier Lite still appears with the Carrier Rig 3D model. There is a version of the Carrier Rig that now appears correctly, but the GL Rig still uses the model for the Lite Carrier.

Mass-closing resolved issues not updated in 10 days.