Description

Intuiface supports the following image formats: .avif, .webp, .png, .jpg, .jpeg, .bmp, and .gif.

To add an Image Asset into an experience, you can either:

• import an image into Composer from your hard drive by either dragging & dropping it from File Explorer, or using the Import Content button in the Content Library,
  OR
• reference, rather than import, an image by entering its file path or Web URL in the Image property of the Image Asset (see image below)

Imported image files are automatically copied by Composer into your Intuiface project's file structure. As a result, there is no need to store a separate copy of each image on the devices hosting Player.

Referenced image files must have paths/URLs that are universally consistent from one device to the next to ensure successful deployment across multiple devices.

About AVIF support

For Composer and Player on Windows, you must pre-install the “AV1 Video Extension” (AV1 Video Extension - Microsoft Apps). The Windows operating system does not natively support AVIF files. Even Microsoft apps like “Photos” need this extension to display AVIF images.

Web-deployed experiences are fine on Windows PCs, even if the AV1 Video Extension is not installed.

About use of animated GIFs

Starting with Intuiface Version 5.6, animated GIF images are supported across all Intuiface platforms, with or without transparency (i.e. with or without an alpha channel).

For non-looping animated GIFs, like the one below, you can force the animation to restart by calling the Show action (using any trigger of your choice) of the corresponding Image asset, even if the GIF is already visible.

NOTE: Animated GIFs are automatically converted to non-animated GIFs if the file's resolution is above 2 Megapixels.

Performance recommendations

• To minimize the occurrence of high memory consumption experiences, both Intuiface Composer and Player implement an automatic resizing mechanism to optimize the amount of RAM consumed by any given image.
  • You may notice a brief blurring effect as you increase or decrease the size of an image.
  • The underlying image is not affected; the original, full-resolution image is stored in your experience. Only the visual representation of that image - and thus the amount of RAM used to store that image - is impacted in Composer and Player.
• To minimize the physical size - i.e. disk space used - of your experiences, you are encouraged to reduce the pixel density of images to a size no larger than necessary.
  • Adding a true color 3500x3500 image to a scene and resizing it to 600x600 does not change the fact that a 3500x3500 image will be stored on disk. You are better off resizing your large image to the size you require BEFORE adding it into the experience. The result is an experience that may take up significantly less disk space.
  • Open-source tools like Gimp or Light Image Resizer can be used to process your images before importing them in Intuiface.
• If you don't need transparency in your image, e.g. for a background, use the JPG format as it will take up less space than a PNG.

Properties, Triggers & Actions

Properties

Triggers

Actions

Limitations

• The EXIF orientation tag of an image is not taken into account. This means that some images imported in Intuiface will be displayed with the original orientation of the camera that took the picture.
• Using URL-accessible Image Sources with WebP images is not supported