6. Technology and weapons
Technical data are separate by entity and provenance. Precision numbers belong to canonical TECHNREF .data; research maps and publications remain in DEV _ RESEARCH; only 100% source-backed and runtime-relevant facts are studied in runtime data.
Weapons data path
According to the gun, there may be additional canonical engine, seeker and guidance parts. Player sets helicopter and load for your PLAYER machine and for every actual wingman active player flight; each flight member may have its own helicopter type, hardware, fuel, countermeasures and ammunition. Other ALLY / OPFOR / NPC are not editors: their platform, loadout / ammo, sensor profile and readability is determined by the developer in canonical data or Campaign World Editor mode and applied according to world / camp / mission parameters. A historical mission may propose a realistic default to a player, but the player remains limited by technical / time / unit compatibility.
TECHNREF Provence
| Condition | Meaning |
|---|---|
| SOURCE_FACT | value / context verified by source and with known semantics |
| SIMULATION_BASELINE | explicit simulation parameter, not issued for historical source fact |
| PENDING | the data is not sufficiently verified; it must not be assumed |
P5.7.109 - M1A1 Abrams source gate
Canonical M1A1_ALLY was deepened from 13 / 24 to 16/24 (66,7 %): U.S. Army source directly evidenced AGT 1500 and 504,4 US gal JP-8 in the M1A1 context and the acquisition handbook 1994, M1A1 NBC microclimatic protection is evidenced. Later M1A1 SA values (e.g. 30 mph cross-country) are not automatically transferred to older baseline.
In global-unit data there is M1A1_ALLY sources-backed tied to 9th Iraq Army in OIR West Mosul 12. 3. 2017. This is the operator / unit point binding, not the claim of an accurate Iraqi modernization subvariant of each machine.
Damage and materials
Weapon effect is not evaluated by a universal "damage number." The terminal effect respects cover / occupation, armor / component / personnel and structural-material profile for constructions. Therefore, the same small HE rocket can destroy a light hut and only damage the wall or the reinforced concrete structure locally.
P5.7.110 - TECHNREF closure pass
CH47F_BLOCK_II newly used by the U.S. Army Block II source for estimated empty weight 26 800 lb, minimum crew 3, capacity 36, 24 litters and accurate cargo-hook limits. The pendings remain weapon, detailed sensor and survival group.
MI24D_HIND_D_NPC was rectified against already stored VHU source facts: rotor / length, empty mass, speed / range / cailing and TV3-117 power no longer false-guided as missing. AH1Z_VIPER no longer leads dimensions / empty-mass as boarding; detailed sensor / survival decay remains open.
P5.7.127-129 - canonical 3D model / GAME- quality pipeline
Older canonical model is no longer automatically target quality. Practically every pre-P5.7.127 model is in the new review OLD baseline; if there is a better GLB, the placeholder is replaced and the new candidate is going through a deterministic import / LOD / material / orientation / validation / review gate.
- Orientation: RIGHT = + X, FRONT / nose = + Y, REAR = -Y, LEFT = -X, TOP = + Z. The model doesn't overturn for the AI.
- GLASS: only real source-backed window / canopy; in GAME review opaque pale blue.
- RUBBER: only real tyre / rubber; black. Rim / disc / mushroom is not RUBBER. Track is dark-metal / track material.
- Authoring authority: source node / material slot or explicit face / region autoering. Bitmap texture may help as a reference, but it itself is not runtime material classification.
- Review authority: OLD canonical vs NEW regenerated candidate; user annitation determines promotion. Damage-part references are also validated after geometry replacement.
PLAYER helicopter base model / load
Canonic base PLAYER heli contains airframe, structural pylons / seagulls / hardpoints and only truly integral fixed equipment. Missiles, Rockets, Bombs and Changeable Gun / Rocket Pods are dynamic stores and the authority is runtime loadout. Quality weapon geometry from GLB can be extracted as a separate weapon model source.
Hangar / Loadout uses the same canonical mesh as the game. Before graduation, PLAYER heli must pass FRONT = + Y gate to be in neither the loadout nor the flight runtime ass forward.
P5.7.129 - WORLD / ERA and party technology
Equipment cover is not considered to be one global pile. For each WORLD / ERA, the explicitly assigned technique is recorded separately for US / ALLY / OPFOR, its category and status of model. ASSIGNED is the OOB / snapshot binding; MODEL PRESENT is only an asset readability signal. Regional candidate pool is a research lead and must not be automatically spawned.
P5.7.145 TECHNREF in ALT scenios
ALT / WHAT-IF / CUSTOM may mix eras, but a real platform, weapon or experimental program still uses its canonical actual TECHNREF. Scenario freedom is not limitation to rewrite real technical data.
P5.7.150 - Global application / material authority
GS2D, GS2K, Object Editor GAME LOOK and GS Encyclopedia use one appearance_catalog.data. Model carries semantic surface (e.g. CAMO_MAIN, GLASS, RUBBER, HULL_PAINT, WOOD_DECK, FLIGHT_DECK, BRICK, CONCRETE, FABRIC_MAIN); specific color selected by platform, operator, period, role and WORLD / AO.
A verified standard code or published colorimetry is a de facto authority. GAME_ART_RGB_APPROX is only a screen approximation. Precise historical camouflage, markers and date- specific lives are SOURCE_GATED. PLAYER / ALLY / OPFOR itself is not a paint authority.
Current source-backed set includes U.S. CARC / MIL-DTL-53072C, CH-47F FS 34201, NAVSEA Haze Gray / Deck Gray, Bundeswehr RAL F9, Czech ČOS 801001 and MIL-STD-2161C scheme / marking authority. For operators without public numerical paint authority, the game can use explicitly marked GAME _ ART operator baselinewhich must not be presented as a historical shade.