Am Donnerstag, den 25.02.2010, 22:23 +0100 schrieb Roy Vegard Ovesen: > FSlint reports that the base package, or the data directory, contains quite a > lot of duplicate files. The file that is wasting the most bytes is > glass_shader.png (some instances named glass.png) with 43 974 656 bytes, or > around 45MB. This file is duplicated 89 times. The second biggest waster is > shader.png (here too some instances are named glass.png) with 31 457 280 > bytes > and 641 instances. > > Running fdupes in the data directory reports that duplicate files occupy > about > 420 megabytes of the 2.7 Gig. Thats roughly 15% (if my math is correct). > > Many of the duplicate files seem to be textures. This begs the question: > would > it be better to have a directory $FG_ROOT/Aircraft/Textures where one would > put textures that are shared by several aircraft? There already is a > $FG_ROOT/Textures directory, but this seems to contain only non-aircraft > textures. > > Comments? > I guess most duplicate files are instruments which are not in the generic folder. Of course it would be desireable to have them all in one place and reference to there, but that would cause severe problems with the aircraft downloads, because every aircraft on the download page would need a second package for instruments which are not in the Base package. Including all these Instruments in the Base Package would greatly increase the download size.
Another thing are textures used in aircraft models. Most 3D Programs prefer to have texture files in the same directory as the model file. A change of texture file paths is possible but requires some post processing of the .ac file, which will be instantly dumped when the file is exported from the 3D Program. This workflow is rather annoying. Additionally the same problem with redistribution, who is going to sort out which files belong to which aircraft and creates download packages? Greetings -- Detlef Faber http://www.sol2500.net/flightgear ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
