Optimizing the images in your presentation can substantially improve both the startup and runtime performance of your application, as well as the visual quality in certain situations.
Unoptimized images can hurt the performance of your application in several ways:
Additionally, choosing an appropriate size for your images and using mipmaps can prevent aliasing issues if your image is going to be shown substantially smaller at some points.
Note: Make your image small, but with dimensions that are multiple of 4.
The first thing you need to do is resize your image to be almost as small as possible. Smaller images can be loaded faster by the graphics system as they need less bandwidth and memory. Think about the largest size that your image will ever be seen at, and resize your image down to that size. If your texture will be tiling at about 32 pixels per repetition, don't save it at 1024×1024.
However, note that both the horizontal and vertical dimensions of your image must be a multiple of 4 to be stored on the graphics card. If you save an image at
107×29, Qt Quick 3D scales it up asymmetrically to
108×32, before sending it to the graphics card. This smears your image slightly, and also wastes performance while the image is resized.
Note: If you are using mipmaps, there are further constraints on image dimensions.
Note: Use mipmaps when your image may be seen smaller than the original size, including portions in perspective.
Enabling mipmaps creates many smaller copies of the image at an additional 1/3 memory usage. Each mipmap dimension is halved from the one preceding it, and is downsized in image editing tool with good image resampling. The result speeds up rendering, decreases the time that the graphics card uses for texture lookup, and also reduces aliasing artifacts such as moiré effects or texture subsampling.
Note: Mipmaps require specific image dimensions to work correctly at all levels, depending on which encoding is used.
Just as the original image needs to have dimensions that are independently some multiple of 4, each mipmap level that you want to display must also be a multiple of 4. If it is not, you will see rendering artifacts as the mipmap level is displayed.
For example, if you save an image that is
132×44, the image renders just fine at its normal size. The first mipmap, however, is created at
66×22. As these values are not integer multiples of 4, the image looks incorrect at smaller sizes.
So, if you're going to use mipmaps for your image, your image dimensions must be a multiple of 4×(2×number_of_mip_levels). If you ensure that your mipmapped image dimensions are multiples of 32, the first 3 mipmaps work correctly, allowing your image to shrink to 1/8 of its original size efficiently and without smearing.
Most of the time when dealing with images with semi-transparent regions, it is easier to use image editing tool's transparent layers when editing such images. If you choose a compressed encoding that supports alpha, the transparent regions of your scene are properly used for the alpha information.
However, in certain cases you need to control the RGB values of fully transparent pixels. Specifically, you can see visual artifacts if:
In this case, the texture interpolation between a fully-transparent pixel and its neighboring somewhat-opaque pixel blends the RGB values between the two. If you use the image editing tool's transparent layers, the RGB values for certain transparent pixels are saved as white, and you will thus see white fringing at the edges of your transparent regions.
For such cases, instead of creating a semi-transparent layer in your image editing tool, create a layer with no transparency at all, setting the RGB value for every pixel you care about. Then, save the alpha information in a fourth channel.
© The Qt Company Ltd
Licensed under the GNU Free Documentation License, Version 1.3.