13.11.2008, 06:38
Hi Neil,
Yes, inspecting original cooked map_c.tga and the associated map_c.tga_table files was what allowed me to deduce the encoding used and build the Map_c Toolbox application. The original .tga's only contain one all white and one all black chunk. The .tga_table file is simply a list of what chunk number in the .tga file represents a particular map location, nothing fancy really. There might even be room for further optimisation by eliminating identical non-all white/black chunks but I doubt it's worth the effort - processor load would be prohibitive and the gains marginal.
As an experiment you could try and reassemble a file pair with the Map_c Toolbox, threshold the raw map_c so all grayscale values greater than 127 are set to 255 and re-cook. Would be interesting to see the reduction in the size of the cooked map_c.tga file. 8)
Yes, inspecting original cooked map_c.tga and the associated map_c.tga_table files was what allowed me to deduce the encoding used and build the Map_c Toolbox application. The original .tga's only contain one all white and one all black chunk. The .tga_table file is simply a list of what chunk number in the .tga file represents a particular map location, nothing fancy really. There might even be room for further optimisation by eliminating identical non-all white/black chunks but I doubt it's worth the effort - processor load would be prohibitive and the gains marginal.
As an experiment you could try and reassemble a file pair with the Map_c Toolbox, threshold the raw map_c so all grayscale values greater than 127 are set to 255 and re-cook. Would be interesting to see the reduction in the size of the cooked map_c.tga file. 8)