8,574
edits
m (→Saving the files: clarification: Texture does not have to be a square, but must have n^2 pixel long sides; + Users on low end computers might experience a delay when loading large textures on other MP aircraft) |
(→Saving the files: corrections) |
||
Line 36: | Line 36: | ||
=== Saving the files === | === Saving the files === | ||
''Start'' the work by saving your livery while it is still empty. That way you will not get carried away, forgetting to save it just to be reminded in the harshest way, maybe having hours of work lost. The file should usually have a size of 1024*1024 pixels, but it does not have to bee a square and any rectangle with | ''Start'' the work by saving your livery while it is still empty. That way you will not get carried away, forgetting to save it just to be reminded in the harshest way, maybe having hours of work lost. The file should usually have a size of 1024*1024 pixels, but it does not have to bee a square and any rectangle with 2<sup>n</sup> pixels side, for example 256, 512 and 2048 pixels, will do. Larger image size will result in more detail being shown, but also a slower running FlightGear. In particular users with lower end computer might experience a delay when loading the model and texture of other multiplayer aircraft coming within a certain distance. | ||
If you are working with raster files, remember to use a two or four times larger size, while working on the livery, in case you later on need a livery in a larger size. When you are done you can save a version in the right size. Save the file in a larger size also when creating a raster image paintkit from scratch. | If you are working with raster files, remember to use a two or four times larger size, while working on the livery, in case you later on need a livery in a larger size. When you are done you can save a version in the right size. Save the file in a larger size also when creating a raster image paintkit from scratch. |