Release Date

Introduction

frontline.io PC App V26.1 introduces improvements to the Digital Twin Editor, AI-powered Knowledge Base search, an extended FlowCode scripting engine, and smarter procedure layout behaviour. Seven bugs are resolved in this release, and ten known issues are documented below.

• Digital Twin Editor - Adaptive Reference Grid

• Digital Twin Editor - Auto-Save View on Animate Steps

• AI Insight - Knowledge Base Search

• FlowCode - Extended Scripting Engine

• Procedures - Adaptive Layouts

What's New at a Glance

New Features

Digital Twin Editor - Adaptive Reference Grid Content Creators

The reference grid in the Digital Twin Editor now automatically rotates to face the user when switching to orthographic side views, matching the behaviour of professional 3D tools. Previously the grid disappeared when viewing from the side because it was parallel to the view direction.

• Front/Back ortho views: Grid aligns to the XY plane.

• Left/Right ortho views: Grid aligns to the YZ plane.

• Top/Bottom and Perspective views: Grid stays on the default XZ floor plane.

• Axis colours: Red = X, Green = Y, Blue = Z.

• On exit: Grid snaps back to the floor when leaving ortho mode or rotating to a non-cardinal angle.

How to access: No action needed. The grid adapts automatically in the Digital Twin Editor when switching between camera views.

Digital Twin Editor - Auto-Save View on Animate Steps Content Creators

When completing an Animate step in the Digital Twin Editor, the current camera view is now saved automatically. Previously, creators had to manually save the view after each animation step, creating a risk of losing the view in multi-step workflows.

How to access: No action needed. Applied automatically once updated to 26.1.

AI Insight (AI Chat) - Knowledge Base Search All Users

AI Insight in the PC app can now search and retrieve relevant Knowledge Base items in response to user questions. Results are relevant and clearly displayed within the existing AI Chat interface, without leaving the app.

How to access: Open AI Insight in the PC app and ask a question. Matching Knowledge Base items will be included in the response where available. Availability depends on what your workspace administrator has configured.

FlowCode - Extended Scripting Engine Advanced Content Creators

The FlowCode scripting engine has been extended with new capabilities. If you do not use FlowCode, no action is needed.

New scripting capabilities:

• HTTP requests: GET, POST, PUT, and DELETE with callback handling.

• Procedure scoring: SetScore function for assessment and graded training scenarios.

• Persistent storage: Read, write, and delete key-value pairs across sessions.

• Timers: setTimeout and setInterval with cancel support (max 50 concurrent, 16ms minimum interval).

• UI manipulation: Control text, images, sliders, toggles, and visibility from script.

• Unity types: Vector2/3/4, Quaternion, Color, Mathf, and Time available in script.

Security controls: Configurable CLR access control, feature-flag gates for HTTP and GameObject extensions, 5-second script execution timeout, 100,000 statement limit, PlayerPrefs namespace isolation (flcode_ prefix), and audit logging on all sensitive operations.

How to access: Available in the FlowCode editor within the Interactive Flow Editor. Full API documentation is being prepared for advanced creators.

Procedures - Adaptive Layouts All Users

The procedure step card now adapts its position and size based on the device screen orientation and aspect ratio.

• 3D procedures, landscape/wide screens: Step card anchors to the top-left with a draggable resize handle. User-set width is preserved across orientation changes.

• 2D procedures and portrait/narrow screens: Step card anchors to the bottom-centre.

• Dynamic switching: Layout updates automatically on device rotation or window resize, without interrupting the procedure.

• Small screens: Minimum width clamps to the available screen width rather than overflowing.

How to access: No action needed. Applied automatically once updated to 26.1.

Resolved Issues

Digital Twin Editor

• Object Target - Polygon Count Limit Removed: The 64,000 polygon cap has been removed when creating an Object Target. Object Targets can now be created and saved from models of any polygon count.

• Hidden Parts Persisting Across Sessions: Hiding or isolating parts in the first editor session saved those parts as permanently not visible. In subsequent sessions, the parts could not be made visible again. Parts hidden or isolated in the first session now reset correctly - visibility can be toggled as expected in all sessions.

• QR Target Appearing Transparent: QR Targets created in the Digital Twin Editor appeared transparent without displaying the QR texture, making it impossible to verify correct placement or orientation. QR Targets now display with the correct texture and orientation indicator.

Digital Twin

• Selection Outline Rendering: Selecting a part rendered a flat colour overlay across the entire mesh surface instead of a clean edge outline, making it difficult to identify selected parts in complex or overlapping geometry. Selected parts now display a clean edge outline around the silhouette only.

Login

• Guest Popup on Deep Link: Opening a deep link with the app fully closed and the user not logged in showed a guest login popup instead of the normal login screen. Users are now taken directly to the login screen. Deep link content loads automatically after login.

Interactive Flows

• 3D Procedure Animation Reset on Next/Previous: Rapidly pressing Next then stepping back with Previous caused animations not to reset correctly - parts appeared in wrong states at steps where they should have been hidden. Animation state now resets correctly when navigating between steps.

Custom Tools

• Custom Tool Pivot Not Persisting in Digital Twin Editor and Animation Builder: Pivot position and rotation edits made to a Custom Tool in the Tools Editor saved correctly within the editor session, but were not applied when the tool was added to the Digital Twin Editor or Animation Builder - requiring the user to re-apply the pivot each time. All other tool properties (name, thumbnail, material, position, scale) saved as expected. Custom Tool pivot position and rotation now persist correctly in both the Digital Twin Editor and Animation Builder.
  

  

  Custom tools placed before this update may shift to their corrected pivot — review positioning in existing 3D content after updating.

Known Issues

The following issues were identified during testing of this release and are not yet resolved.

Digital Twin Editor

• Save Prompt on Unchanged Files: The save prompt appears when closing the Digital Twin Editor even when no changes have been made. Expected behaviour is for the prompt to only appear when there are actual unsaved modifications.

• X-Ray View Displays Hidden Parts: Parts hidden in the Digital Twin Editor appear visible when X-Ray mode is enabled. The parts remain correctly marked as hidden in the data - this is a display issue in X-Ray mode only.

• Hidden Part Not Hiding on Back Step: When stepping backward through a 3D procedure animation, a part that should be hidden at the previous step may remain visible.

• Hidden Part Not Hiding Immediately on Restart: When restarting a 3D procedure, hidden parts may remain briefly visible before their hidden state is applied.

Interactive Flows

• Rich Text Formatting in Step Nodes: Italic formatting, numbered list spacing, and block quote styling do not render correctly in the 2D/3D procedure player. These formatting options display correctly in the Flow Editor but not in the app.

• Animate Step Tool Not Loading Until Reset: When a tool is used for the first time in an Animate step (not present in any earlier step), it may fail to display during playback. Restarting the procedure resolves the issue for that session.

• Procedure UI Small and Scattered: On certain screen configurations, procedure UI elements may appear scattered, button styles may appear inconsistent, and description text may appear very small.

Remote Assist

• Camera Ratio Not Refreshing on Camera Change: Switching camera during an active Remote Assist session does not refresh the video aspect ratio. The incoming feed may appear distorted if the two cameras use different aspect ratios.