UML has the option to load different remodels based on map type (summer/winter/desert). 
It also allow a dedicated model to be set up exclusively for hangar.
This feature is in place as long as UML is installed. And it doesn't distinguish own tank or other players' tank.
Modders do not need to build a profile for your work in 'UMLprofiles' folder

It only works on undamaged model and tracks at this time for I see no need to use it on damaged ones. 
Burned painting layer of a destroyed model should be the same regardless of its seasonal paint colour.
You can assign a seasonal damaged chassis however, since damaged UV-bend tracks are displayed when player's tank is
de-tracked still alive.
======================================================================================================================
[Introduction]

Winter and desert models should be placed in folder named 'winter' and 'desert' under main model directory.
Hangar model should be placed in folder named 'hangar' under main model directory.
'summer' folder is in fact supported but typically not used, because if a map is neither desert nor winter then it must be summer, so the default model path will suffice.
If winter/desert/summer/hangar folder is found and its content valid, UML will load the corresponding model variant. 
If winter/desert/summer/hangar folder is not found or its content invalid UML will continue to use the default model.

For example default (and summer) undamaged chassis model will be in 
res_mods/0.9.17.1/vehicles/russian/R11_MS-1/normal/lod0/chassis.model

While undamaged chassis models intended for winter map shoule be in
res_mods/0.9.17.1/vehicles/russian/R11_MS-1/winter/normal/lod0/chassis.model

Optionally you can have winter segmented tracks at
res_mods/0.9.17.1/vehicles/russian/R11_MS-1/winter/track/segment_L.model

Optionally you can have winter destroyed tracks at
res_mods/0.9.17.1/vehicles/russian/R11_MS-1/winter/crash/lod0/chassis.model
But not destroyed hull/turret/gun
======================================================================================================================
[About model file structure]

For beginner:
xxx.model and xxx.visual files are xml file with different extension. WarGaming shipped them in packed binary format. 
Use WoT Mod Tools 0.5 to unpack these files.
Be careful what decimal is used for your local OS. WoT only accept '.' while many countries use ','
WoT Mod Tools 0.5 will always use your local OS setting.

Inside xxx.model file it will specify linked visual file path and possible LoD submodel and transition range.

Inside xxx.visual file it will define logic node structure and render parameters. If <primitivesName> is defined it will be linked to this .primitives file.
If such node is not found it will be linked to a primitives file under the same folder with the same name.

======================================================================================================================
[Prepare a full set of .model files, but not necessarily the primitives/visual files]


Do remember that under seasonal/hangar folder there should be an entier set of .model files like a standard remodel should be.
You should treat /winter/ /hangar/ or /desert/ as if it's the main model directory.
You can't place only chassis hull and turret then ignored gun.

And these .model files should be valid and ready to be used by its own right.
That means you can either direct these .model to the default .visual which will cause winter model to use the same model and texture as summer one.

Or direct it to a different visual file for example res_mods/0.9.17.1/vehicles/russian/R11_MS-1/winter/normal/lod0/chassis.visual 
so that you can specify a different texture for the winter model for example res_mods/0.9.17.1/vehicles/russian/R11_MS-1/winter/MS-1_chassis_01_AM.dds
A visual file needs its companion primitives file, so either place one under the same path, or save some harddisk space by using the <primitivesName>
override clause in visual file.
======================================================================================================================
[4 possible components]

When winter/desert/summer/hangar folder is detected, ownModelLoader will first attempt to load all four component model files (chassis hull turret gun) to verify its content.
If any error occured during this process, default models will be used.

Seasonal model validation is executed seperately for:
# normal chassis+hull+turret+gun 
# segmented track
# crash chassis
# physical track

Failing the validation of one of the above will not affect the other three.
Meaning for example you can use seasonal segmented tracks without using seasonal chassis+hull+turret+gun


======================================================================================================================
[Seasonal splineTrack]


Seasonal variant of splineTrack model should be placed inside 'track' folder of its corresponding seasonal folder. 
For example the winter track for R07_T-34-85 should be:
	res_mods\x.x.x.x\vehicles\russian\R07_T-34-85\winter\track\segment.model
	and the associated primitives/visual/texture. etc.
        This 'track' folder is mandatory. 


======================================================================================================================
[Seasonal physicalTrack]

PhysicalTrack requires a dedicated config.xml inside seasonal folder, in addition to the actual seasonal remodel.
This is because adding the winter extension kit to a regular track makes left track different from the right one, so they could 
not share the same track segment model like most of the vanilla WoT tank. So modding the segment shape is not enough, track configuration also needs to be altered.

1. place seasonal track segment model to 'track' folder under the corresponding seasonal folder, just like the seasonal splineTrack.
   for example,  res_mods\x.x.x.x\vehicles\russian\R07_T-34-85\winter\track\segment.model
   and the associated primitives/visual/texture. etc.
   This 'track' folder is mandatory. 
3. Create config.xml under seasonal folder, not seasonal track folder.
   For example create an empty text file under res_mods\x.x.x.x\vehicles\russian\R07_T-34-85\winter\
   Then rename it to config.xml
   File extension must be '.xml'. If the original .txt extension is hidden so that you can't rename it, use windows folder option to reveal file extension.
4. Copy the entire <physicalTracks> section from vehicle definition xml into our new config.xml, then edit the model reference path accordingly.
   Note that xml format requires a base <root> node as the outter-most node.
   You should end up with something similar to this:

	
<root>
      <physicalTracks>
        <left>
          ...
          <mainSegment>
            <model>vehicles/russian/R07_T-34-85/winter/track/segment.model</model>
            <length>	0.154542	</length>
          </mainSegment>
          <secSegment>
            <model>vehicles/russian/R07_T-34-85/winter/track/segment2.model</model>
            <length>	0.159299	</length>
          </secSegment>
          ...
        </left>

        <right>
          ...
          <mainSegment>
            <model>vehicles/russian/R07_T-34-85/winter/track/segment.model</model>
            <length>	0.154542	</length>
          </mainSegment>
          <secSegment>
            <model>vehicles/russian/R07_T-34-85/winter/track/segment2.model</model>
            <length>	0.159299	</length>
          </secSegment>
          ...
        </right>
      </physicalTracks>
</root>


