LGTM decode of "unknown" bytes.

[GoogleCodeExporter]

The byte array of length 32 in the middle of LGTM records appears to have the 
same structure as the DALC subrecord.  Not only are the colors that result from 
this decoding very similar to those in some of the new DALC subrecords, but 
there's a curious correlation between the specular being present in the unknown 
bytes when it's missing from the DALC subrecord.  My guess is that there was 
some kind of transition from the "unknown" bytes to the DALC subrecord which 
allows partial transition.

Probably not coincidentally, this resolves some short records in Skyrim.esm 
(four with size 72 and one with size 64).  LGTM record version 31 has a DATA 
subrecord length of 72, which matches a complete DALC subrecord and makes the 
fields after this an extension post version 31.  One version 30 record (HHFar) 
has a DATA length of 64 which is consistent with the same malformation 
encountered in the DALC subrecord of "TESTCloudyRain", which was version 31.  
Thus I conclude that the transition to the new DALC subrecord started around 
this time, although there's little other evidence.

By the way, I've been working on a cross-platform Python decoder for Skyrim 
ESP/ESM files, and I've found the TES5Edit source to be very helpful.  Thanks 
for your great work!  I've found a few other similar decoding issues if you're 
interested.  BTW, I rarely check my gmail account.

Original issue reported on code.google.com by cfcohe...@gmail.com on 18 Jan 2015 at 2:08

[GoogleCodeExporter]

SKSE agrees as it define there the same structure as for the DALC. But 
obviously the code handle incomplete records by zero filling the DATA SubRecord 
up to 0x60 bytes.

Original comment by HuguesLe...@gmail.com on 21 Jan 2015 at 9:56

[GoogleCodeExporter]

see r1886

Original comment by HuguesLe...@gmail.com on 2 Feb 2015 at 11:45