1. 26.04.1 Release

These release notes describe the changes introduced in Foretellix products in version 26.04.1. Features are classified as New, Changed, or Deprecated. "Changed" indicates either interface modifications or behavioral changes to existing functionality.

1.1 Evaluation V-Suite

[New] Expand Coverage Metrics to Additional L0 Scenario Nodes (Phase 1) (SDL-72274)

Extended the evaluation V-Suite with coverage metrics for additional L0 scenario nodes, expanding behavioral coverage across the drive_in_lane, nav_intersection, and nudge scenario families.

• Added new scenario family files for drive_in_lane, nav_intersection, nudge, and their base variants, with coverage structure reorganized per L0 node for clearer separation across behavioral categories.
• Introduced new coverage items applying to all scenario families and a centralized enum configuration consolidating shared enums across the V-Suite.
• Added a new change_lane evaluation example with XODR map and run script to accelerate onboarding; additional L0 nodes will follow in subsequent releases.

See NVIDIA Evaluation Scenarios.

1.2 Foretify Manager

[New] Create Synthetic VRUs in the Scenario Designer (SDL-73357)

• Users can now add synthetic pedestrians and cyclists.
• Their trajectory can be composed of multiple line segments travelled at a constant speed.

[New] Monitor License Usage with License Report API (SDL-72146)

Added support for monitoring real-time license usage from Foretify Manager using the License Usage Report API.

• Exposes a REST endpoint and Python SDK access returning total, used, and available license counts per feature, including active checkout details such as username, hostname, and start time.
• Enables automated tracking of license consumption across your deployment to optimize license allocation and identify usage patterns

See Monitoring license usage.

[New] Reorder Coverage Items in VPlan Tree (SDL-71575)

Added the ability to sort coverage metric items within a coverage group in the VPlan tree by Name or Grade in ascending or descending order.

• Sorting options are available directly in the VPlan tree header for each coverage group, improving navigation and readability for complex VPlans with many coverage items.
• The selected sort order persists across sessions, ensuring a consistent view for each user.

See Sort display of metric items.

[New] Visualizer-focused layout for Single Run Debugger ( (SDL-69789)

• New layout option maximizes the Visualizer and tucks away detailed panels, which can be expanded on demand.
• Layout switching is now preset-based, so you can always return to a known layout.
• Admins can set the default layout for new users, each user’s layout configuration still persists in their preferences.

[New] Define Node Weights per VPlan View (SDL-67974)

Extended the VPlan Views feature in Foretify Manager with the ability to define a custom weight for each node in the VPlan tree on a per-view basis, giving users full control over how individual nodes contribute to the final coverage grade.

• Users can increase or decrease the weight of any bucket, metric item, metric group, struct, or section within a VPlan view without affecting the shared base VPlan or other users' views.
• Setting a node's weight to 0 removes all impact of that node and its entire subtree from the coverage grade calculation, providing a more precise alternative to simply excluding a node.
• Weight adjustments are stored per VPlan view, allowing different teams or stakeholders to maintain their own grading perspective on the same underlying test plan data.

[Changed] Improved control over Traffic Infrastructure visualization (SDL-73252)

Replaced the single Signals toggle in Visualizer's View Tools configuration with independent Traffic lights, Stop signs, and Yield signs toggles.

[Changed] Persist Coverage Bucket Visualization Preference (List or Histogram) (SDL-71571)

Changed the coverage bucket visualization in Foretify Manager so that the selected display mode — list view or histogram — is automatically saved and restored across sessions.

• Histogram view is now set as the default, providing immediate visual insight into coverage distribution upon first use.
• Users can switch between list and histogram view at any time; their preference is restored on next login without requiring reconfiguration.

See view buckets as histogram chart.

[Changed] Support overriding any environment setting from the Launch dialog (SDL-71501)

• Previously, you could only override settings that already existed in the selected Environment Settings.
• Now, you can enable Show all environment settings to view and modify any available setting, including specifying settings not yet configured.

[Changed] Prevent Accidental Execution of Long Running Operations in VPlan Viewer (SDL-70732)

Improved the VPlan viewer experience by moving buttons that trigger long-running operations into a three-dots menu to prevent accidental execution.

• Actions that could degrade system performance or produce inconsistent results are no longer exposed as primary buttons in the viewer.
• Users must explicitly open the menu to initiate these operations, reducing the risk of unintended side effects during analysis.

See VPlan viewer.

1.3 Evaluation Pipeline

[New] Extrapolation of stationary vehicles (SDL-72115)

• Stationary vehicle extrapolation automatically extends detected stationary vehicles (primarily parked cars) across the full clip duration.
• This enables the generation of ground truth data, including data that was not fully recorded by the Ego (such as occluded vehicles and VRUs), particularly when modifications are applied to create new scenarios that were not part of the original recording.
• For complete documentation, see Viewing the ingested scenario.

1.4 Bugs fixed

1.4.1 Foretify Manager

1.5 Known Limitations

The dispatcher/orchestrator currently only supports 1 replica (SDL-68883)

The Kubernetes dispatcher and orchestrator currently only support 1 replica.

Only one Orchestrator pair is supported per Foretify Manager. Each Orchestrator should use its own namespace.