weaponarchetypes.meta: tying a weapon model to its textures

#A real example

<CWeaponModelInfo__InitDataList>
  <InitDatas>
    <Item>
      <modelName>w_ar_myrifle</modelName>
      <txdName>w_ar_myrifle</txdName>
      <ptfxAssetName>NULL</ptfxAssetName>
      <lodDist value="500"/>
    </Item>
    <Item>
      <modelName>w_ar_myrifle_mag1</modelName>
      <txdName>w_ar_myrifle</txdName>
      <ptfxAssetName>NULL</ptfxAssetName>
      <lodDist value="300"/>
    </Item>
  </InitDatas>
</CWeaponModelInfo__InitDataList>

Here the rifle and its magazine share one texture dictionary, w_ar_myrifle.ytd. That is common: several models can read from the same dictionary, which keeps the texture count down.

#The four fields

#How it connects to your textures

A model asks for textures by name; txdName tells it which dictionary to search. If you retexture a weapon and rename the dictionary, update txdName too. If textures come out pink or missing, the problem is either this name or the texture names inside the .ytd — see pink weapon textures and .ytd texture dictionaries.

#lodDist and other players

You always see your own weapon up close. lodDist matters for everyone else: it is how far away other players can still see the weapon in your hands or on your back. A value of a few hundred metres is enough; very high values make every weapon in the area draw from far away for no benefit.