Player Next Gen (PLN) shares the limitations of the current-gen Player running on all platforms but Windows (such as our limitations on Android and the iPad).

The list below captures limitations exclusive to PLN.

Features Never to be Supported

Certain Intuiface capabilities available in Player on Windows will never be available in Player Next Gen.

• (Microsoft) Deep Zoom asset.
• Any JavaScript-based Interface Asset.
  All out-of-the-box interface assets are being rewritten using TypeScript. Any customer-created interface assets will have to be rebuilt using Intuiface's TypeScript CDK.
• Player has to be re-activated if it was previously downgraded to any version inferior to 7.0.14.

Features Not Yet Supported in Player Next Gen

Assets:

• YouTube Asset
  • Not supported on any Samsung SSP running TizenOS version below 6.5.
  • Will not be able to interact with Video controls when YouTube is nested inside the Carousel collection.
• Web Browser
  • Website resources coming from http:// (non secured) protocol are not supported. 
  • "Disable Scroll" Web Browser property is not supported on Samsung SSP and iOS devices.
  • Web Page drop-down controls will not respect Web Browser's rotation
  • Multiple Web Browser assets cannot be simultaneously manipulated.
  • "Website fails to load" triggers will not be raised on iOS and Android devices.
  • Depending on their Content Security Policy, some websites cannot be loaded.
  • The Web Browser asset's Web Page Width will not be taken into account. The website will adapt to the container's size.
  • Scrolling is not supported for browsers with an orientation different than 0°
  • Interactions with the Web Browser will not stop "inactivity timers" nor raise the "User activity detected" triggers.
• 3D Model Asset
  • Some rendering differences might be observed 
  • Supports only GLB/GLTF format
  • Model Light properties that can be defined in Composer are not supported
  • "Keep Model in Viewport" Pan property is not supported
  • When running on iOS, a minimum version of iOS 16 is required
  • Models using relative textures cannot be loaded via URL

  • Spec/gloss PBR textures are not supported

  • 3D models will not be loaded if they are contained in a folder named with a hash symbol (#)
  • Trackball Orbit and Pan Interaction modes will all behave the same

  • Some models will not appear to be rendered correctly due to texture occlusion settings. The engine used in Intuiface (Three.js) does not render texture occlusions properly. Removing texture occlusion of the model will help with rendering.

• Webcam Asset 
  • Only one resolution will be displayed when using more than one Webcam asset with different resolutions in the same scene.
  • Delay property is not supported.
  • Android-based devices do not support multiple Webcam Assets in the same scene.
  • it is not possible to use both Front and Back-configured Webcam assets at the same time.
• Document
  • When using the Book style, the Book Cover encounters some rendering issues on iOS devices when fullscreen.
  • Does not display scrollbars.
  • Does not scale in size.
  • Supported only on TizenOS 6.5 or superior.
  • Not supported in web deployments.
  • Distant PDF (from a URL as a source) is not supported on iOS-based devices.
  • Does not support the 'Show curtain shadows' property.
  • Changing multiple documents simultaneously with the same source coming from Airtble is not supported.
• Video Asset:
  • Native web browsers do not permit video autoplay until the website is interacted with.
    Workarounds:
    - Have a user interact with the website 
    - Set the volume property of the Video Asset to 0 
  • For experiences published with Views Licensing, videos will be streamed, meaning offline video playback is impossible. You must use Player Licensing with web-deployed experiences - i.e. deploy your experiences as Progressive Web Apps - if you want to run videos while offline.
  • For web-published experiences, the .mov extension is not supported

Collections:

• Ken Burns.
• Map.
  • The ability to force map tile caching through map manipulation is not supported.
  • Maps cannot be zoomed or dragged if the map container is rotated.
  • Mapbox
    • No support for raster tilesets or styles
• Carousel:
  • Vertical Carousel - the item in focus has a vertical alignment that differs in Composer's Edit Mode vs. Play Mode. When designing your experience, guides can be used to center the item in focus properly.
• "Tap to Open" and "Drag&Drop item to open" collection properties cannot be used with multi-touch gestures. In other words, only one element at a time can be Tapped to open or Drag & Dropped to open. Also, while actively manipulating a free asset in the scene, "Tap to open" and "Drag&Drop item to open" will not work.

Asset and Collection features

• Loading indicator for Collections is not displayed

Experience properties, triggers, actions

• Gradient colors.
• Call URL.
• Launch Application action.
• Drawing Tool.
• Creating Snapshots.
• Scene Reload action
• Translating and manipulating assets is not supported in a Flipped experience;
• Is Tapped and Is Manipulated triggers will fire at the same time if placed at the experience level
• Drag&Drop triggers will not be raised on hidden targets.

Expressive Features:

• Geocoding - Latitude/Longitude.
• Device Accelerometer.
• Device Orientation.
• Shake (to quit).
• Effects:
  • Samsung SSSP devices only support Brightness and Grayscale effects.
• Excel Interface Asset Limitations:
  • Saving edits to Excel spreadsheets via the Excel Interface Asset.
    • Edits are only retained in memory for the current session.
  • Will not display content after ten empty rows.

  • Using a formula inside a formula is not supported. For example, the following is not possible: MID(In!A2,1,FIND("~",In!A2,1)-1)

  • The following column names are not supported: "Result"; "Rows"; "RowCount"
• Pinboard:
  
  • Emphasis animation effects when manipulating assets.
• Scroll Collection:
  • Extended zone auto-recalculation.
• Collections:
  • Show Icons (property).
  • Show Curtain Shadow (property).
  • Elasticity (property).
• Asset Shadows.
• Non-flat Button rendering (Button asset will always be flat).
• Rich Text, the following actions are not supported:
  • Set Font.
  • Set Font Color.
  • Set Font Size.
  • Set Font Style

Auxiliary

• Data Tracking:
  
  • Experience Started and Experience Stopped events will not be recorded when using web-published experiences
• .NET DLL-based Interface Asset
  • Will never be supported
• API Explorer:
  • Currently, the Web API response must be JSON-formatted; XML-formatted responses are not yet supported.
• Philips HUE Lights (Interface Asset).
• Share and Deploy Console:
  • Scheduling
  • Batch Player Activation
  • Snapshot (live tracking in Share and Deploy Console) for iOS, Android and BrightSign
  • Player Settings such as Player Tags, Nickname, and Launch preferences will only be taken into account after a Player restart.
• Player Services:
  • Email - Share by email configurable.
  • File (Share by filesystem).
  • Print
  • Unable to accept remote actions
• Exclusive to web-published experiences
  • Credential keys - either those generated by Intuiface or those used for third-party service authentication - are not currently obfuscated and thus can be extracted using browser-based developer tools. We recommend you ensure that the scope of credential key rights is limited to only what is necessary for your running experience.
  • Nexmosphere Interface Asset
    • Nexmosphere IA is currently supported only 1) when using the in-venue player running 2) on the following platforms:
      • Windows
      • Android
      • BrightSign

Unsupported / Supported platforms

Unsupported Platforms

• In-venue Player:
  • iOS
  • ChromeOS
  • LG WebOS

Supported Platforms

Player Next Gen is currently supported on the following Platforms: 

• In-venue Player:
  
  • Windows (via Composer's Play Mode)
    
  • Android
  • BrightSign 8.5 or newer
  • Samsung SSP Tizen 6.5 or newer
  • Raspberry Pi
• On the web
  
  • • Chrome
    • Safari
      • Limitation: Videos cannot be triggered to play using Triggers and Actions. User input must be performed on the video.
    • Edge (Chrome-based)
    • Firefox
    • Brave
      • For iFrame embedding, you must disable "Block cookies"
        
• As an app (Progressive Web App - aka PWA)
  
  • Windows (via Chrome or Edge)
  • iOS (via Chrome or Edge)
  • Android (via Chrome)
  • MacOS (via Chrome)
  • ChromeOS

Platform-specific limitations

• Samsung SSP Limitations
• BrightSign Limitations