;
; This file contains the model linkages for both strategy map and battlefield; it gets
; parsed on application startup but is not otherwise referred to. The data format is thus:
;
; ; indicates a comment ;-)
;
; type indicates a new model type
;
; must be followed by id name string
;
; skeleton indicates which skeletons should be used for these models
; must be followed by id name string (cf descr_skeleton.txt); the
; first skeleton is used for the primary weapon (geometry marked in
; file as "primary weapon"), the second is used for the secondary
; weapon (which should be marked as "secondary weapon")
;
; skeleton_horse alternate skeletons can be provided for models that need to be able to work
; skeleton_elephant in multiple units, i.e generals. If alternate skeletons are specified the normal skeleton
; skeleton_camel (the one specified with the skeleton keyword) is the infantry skeleton.
; skeleton_chariot For generals all alternate skeletons must be specified
;
; scale (optional) this indicates a global scaling factor to be applied to
; the model - as always, it's your responsibility to make sure that
; the size of the model and the size of its skeleton match!
;
; indiv_range indicates at what point we start rendering men individually even if
; we can 'group render'
;
; must be followed by an integer (whole number) range in metres
;
; group render means the whole unit will be rendered using one
; model, individual render means the soldiers will be tested
; individually for which model lod to use (slower)
;
; (models) there must be at least one; the model_ keywords indicate a new model in
; the lod series; each must be followed by a filename and either the
; lod range in metres or the word 'max' for maximum range... all lods
; must be in order, from shortest distance (highest detail) to furthest
; distance. The model_ keywords are *so on....*:
Script Error in data/descr_model_battle.txt Expecting skeletons.
Reply With Quote
Originally Posted by MasterOfNone
