IMPORTANT

• For those using the current generation of Player, experiences fail to download successfully on BrightSign devices running OS Version 8.5. We recommend you do not upgrade to Version 8.5, or - if you've already upgraded - downgrade to OS Version 8.4.14
  This limitation does not apply when using Player Next Gen. Player Next Gen supports OS Version 8.5.
• To ensure you haven't accidentally incorporated unsupported features, make sure Play Mode in Composer is set as follows:
  • If using the current generation of Player: Set "Play Mode" to "Simulate Player on other platforms (iPad/Android/...)". To make this selection in Composer, click the Project menu and choose the appropriate option.
  • If using Player Next Gen: Set "Play Mode" to "Simulate Player Next Gen". To make this selection in Composer, click the Project menu and choose the appropriate option.

Important Design Considerations

Depending on the model you choose, the capacity of BrightSign devices to 1) manage a large number of graphics in a single Intuiface scene and 2) keep in memory large graphic media files and animation may be equivalent to that of a modestly powered Windows PC.  As a result, depending on the complexity and size of an Intuiface experience that performs well on a nicely provisioned Windows PC, that same experience might act sluggishly on your chosen BrightSign model.

We highly recommend the following:

1. Minimize the file size of graphic media. For example, a 4k Ultra HD video on a BrightSign device will consume an enormous amount of system RAM, risking performance issues.
2. Endorse modularity. Choose a small number of images on multiple scenes rather than a large number of images on a small number of scenes.
3. Test on the target device often. Even though Composer's Play Mode includes an option for simulating a BrightSign device, it does not reproduce the expected performance. You must run your experience on the target device to assess its true performance quality.
4. Review the rest of this page to be sure you are acquainted with all limitations. This list will shorten over time, but at the moment, not every design option is available for use.
5. Optimize Used Images. On BrightSign, there is no automatic image optimization; this means the size of used images will have their actual size even when displaying them within small containers.

Features Never to be Supported

Certain Intuiface capabilities available in Player on Windows will never be available in Player on BrightSign because the underlying technology is not supported by the BrightSign OS:

• Intuiface Headless CMS: Support for H-CMS on BrightSign will be introduced with Player Next Gen.
• (Microsoft) Deep Zoom asset
• Websites that require a same-origin policy.
  The Web Browser Asset can only display websites that permit cross-origin resource sharing - i.e. that don't require a same-origin policy. If you attempt to load a website requiring a same-origin policy, the Web Browser asset will display an error message stating the connection was "refused" due to "X-Frame-Options". Most public websites (such as Google, Facebook, Instagram, Twitter, YouTube, ...) require the same-origin policy and cannot be displayed in Player on BrightSign. Sites like these may be accessed using embeddable code placed within the HTML Frame Asset instead.
• Any out-of-the-box Interface Asset using a .NET DLL. Over time, all out-of-the-box interface assets will be built using REST or JavaScript, both of which are cross-platform technologies. For a list of which out-of-the-box interfaces are available on BrightSign devices, see this page.
• Launch Application and Call URL actions

Features Currently Unsupported

The following capabilities are not yet part of Intuiface Player on BrightSign but may be added in future releases:

• Intuiface Player can only operate on SD Memory Cards. Player will not operate if you are trying to install it on any other type of storage device when using BrightSign units.
• Retaining deployed experiences after updating Intuiface Player software using BrightSign ControlCloud. 
  Provisioning via ControlCloud acts like a factory reset, erasing all previously downloaded experiences. Redeployment must occur after every Player provisioning event via ControlCloud.
  As an alternative, use Intuiface's remote Player update capability, which does not erase downloaded experiences.
• Automatic screen orientation. For Portrait content, specific autorun.brs needs to be used in order to configure the device's display orientation. You will have to replace the existing autorun.brs on the device, then restart it for the changes to take effect, find the available configurations below:
  • Portrait clockwise configuration can be downloaded here
  • Portrait counter-clockwise configuration can be downloaded here
  • Landscape reversed configuration can be downloaded here
• Nexmosphere Interface Asset : Auto-connect and the Connected/Disconnected status.
  Nexmosphere controllers must be connected to a BrightSign device before launching Player. Re-connection is not possible if the USB cable to the Nexmosphere controller is unplugged and then plugged back in.
• Share via Email - Configurable (i.e. using your own SMTP server)
• Share via filesystem
• Share via USB
• Helix collection
• Timeline collection
• Circular panel
• On-Screen Gestures - only supports Swipe Up/Down, Swipe Left/Right.
• Webcam Asset
• Scratch Card
• Take snapshot action

Additional Limitations

• 3D Model Asset:

  • Light rendering differences may be observed on BrightSign devices
  • Interaction Mode - "Keep model in viewport" property, when set to true, will be ignored by an orbit.

• Bindings:

  • Binding the height of an asset will apply a scale resulting in a visually deformed asset

• Collections:

  • There is no initial scroll effect for the Asset Flow, Asset Grid, and Carousel collections.
  • Only Scale is managed for items in a Group
  • Asset Flow and Asset Grid collections do not manage "justify". When the collection contains fewer items than can fit in a single view - e.g. 3 items in the collection while 5 could be displayed - then items are left-justified.
  • For the Map collection
    • No caching of a live session
    • Bing Maps is blank without an API key

• Design Accelerators:

  • Item Picker

• Document asset:
  • Book style is not rendered the same as on Windows devices. Flipping through Book pages will not have the same rendering effect
  • For the Book style, the following properties are not yet recognized
    • "Show page numbers"
    • "Reading direction" (it is always Left to Right)
    • "DPI"
    • "Show scroll indicator"
  • For the Book style, the following actions are not yet recognized
    • "First page"
    • "Last page"

• Drawing Tools:

  • Snapshot capability is not yet implemented.

• Effects:
  • Blur, Brightness, Sepia, etc. are not supported

• Excel Interface Asset:

  • Unable to read values from cells referencing another sheet that has a spacing character in its name

• Fonts:

  • Some Windows fonts are rendered differently than they appear on Windows PCs. The following contains the known list of fonts with rendering differences but there may be others.
    • Bookshelf Symbol 7
    • Calibri
    • Marlett
    • MS Outlook
    • MS Reference Specialty
    • MT Extra
    • Times New Roman
    • Webdings
    • Wingdings
    • Wingdings 2
    • Wingdings 3
  • In some cases, certain Bold and Italic fonts may be replaced by BrightSign standard fonts.

• Functionality:

  • Concurrent animation performed on the same asset is not supported. For example, you can't rotate and resize an image at the same time.
  • Minimize capability is not available (including the Initial View State property)
  • Preview Mode requires that each individual media file used in an experience be no larger than 100 MB.
  • Cannot respond to local network triggers or remote actions regardless of the source: neither from a running experience, peripheral, or any third-party application. You can use Web Triggers instead.

• HTML asset:
  
  • You may notice rendering differences
  • Open URL action is not supported

• Image asset
  • WebP images from an Excel Interface asset source are not supported

• Scenes:
  • Scene transition effects may greatly decrease the performance of your experience and could even lead to a crash. Limit their use.
  • Triggers with Actions defined for a different scene are not supported.
  • Videos cannot be used for either the experience or scene Background property. Use an experience layer instead.
  • The following scene transition effects are not available:
    • Circular
    • Wipe
    • Black Fade

• Share via E-mail Hosted Interface Asset:

  • Offline stored e-mails will be destroyed if a Player log-out action is performed. This means, the e-mails will not be sent when the device comes back online, even if you log back in using the same account
  • Sending E-mails with a distant attachment is not supported. The attachment resource must be locally present on the device. Use Interface Asset - Shopping List instead.

• Video and Audio Assets
  • For video use MP4 format with H.264 codec.
  • Microsoft WMV format is not supported
  • Can only use timestamps to assign a poster to a video. External images cannot be used as posters.
  • Remote video will not have a poster frame when stopped
  • Remote video cannot be replayed if ended. If the source is changed, a new video will play.
  • “Title” property of the Video, Audio, and Document assets is not supported.
  • Video will not be properly managed when the experience is in portrait mode. The video should be rotated in the experience in this case.

• Web Browser asset

  • No support for website links opened in a new browser window (i.e. _blank)
  • No support for "link is clicked" trigger
  • Clear Cache action is not supported
  • "Has Been inactive" trigger will fire when manipulating the Web Browser
  • Scrolling of web pages will not work if the page changes size dynamically without reloading.

• Text Asset

  • Avoid using centered text that includes unnecessary spacing characters. For example "   text" will include the spacing when the text is centered. As a result, rendering differences may be observed between platforms when centering text contains spaces.

• Text Input Asset

  • Keyboard's "Standard + Numpad" layout is not supported; the "standard" layout or the native keyboard will be shown instead.
  • Avoid using centered text that includes unnecessary spacing characters. See the Text Asset above for an explanation.

• Triggers and Actions

  • Actions targeting assets on a different scene will not be executed
  • Returned Trigger coordinates will always be asset-based. In other words, the value of the coordinates will be relative to the asset itself and not the scene.