Page MenuHomeFeedback Tracker

Engine ignores/disables custom unit model when class SoldierWB/EB/GB/Civilian have scope=1/2
New, WishlistPublic

Description

In A1 the classes SoldierWB/EB/GB/Civilian are actual units with scope 2.
Since A2 they are just base classes with scope 0.

To achieve A1 missions compatibility, the said classes need scope 1 at least.

However when doing this, all subclasses will now use the model defined in those classes and no longer the model defined in the subclasses. {F19942} {F19943} {F19944} {F19945}

Details

Legacy ID
1793665768
Severity
None
Resolution
Open
Reproducibility
Always
Category
Engine
Steps To Reproduce
  1. Download 2013-06-15 AiA release: https://dev-heaven.net/projects/all-in-arma/files
  2. Extract to .\Arma3\@AllInArma
  3. Use Automated.bat to launch it
  4. Editor
  5. Utes
  6. Load attached mission
  7. Start to game
  8. Notice how all units have the basic A2 models even though some are OA units or other A2 factions
Additional Information

I assume the problem comes from infantry subclasses in between have scope 0 and somehow confuse the engine.

Sample

SoldierWB: CAManBase
scope = 1;
model = "\ca\characters2\USMC\usmc_soldier";

class US_Soldier_Base_EP1: SoldierWB
scope = 0;

class US_Soldier_EP1: US_Soldier_Base_EP1
scope = 2;
model = "\ca\characters_e\US\US_rifleman";

Event Timeline

kju-PvPscene edited Additional Information. (Show Details)
kju-PvPscene set Category to Engine.
kju-PvPscene set Reproducibility to Always.
kju-PvPscene set Severity to None.
kju-PvPscene set Resolution to Open.
kju-PvPscene set Legacy ID to 1793665768.May 7 2016, 2:38 PM

Added another demo mission on Desert world (OA) that has all A2 and OA models present.

The text file contain the scope values for A2 and CO infantry classes as reference.