3. 26.05.0 Release

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

3.1 Release Highlights

• Faster calculate in Foretify Manager leads to significant turnaround reduction. Performance work on the grade calculation path has cut calculate duration by up to 4x, so coverage and grading results land sooner after a run completes. Teams iterating on scenarios should see a noticeable drop in end-to-end cycle time, with no changes required to existing flows.

3.1.1 Backward Compatibility

Compatibility Guidance for Foretellix Tool Versions

To ensure full support and optimal performance, we strongly recommend updating both Foretify and Foretify Manager to the same version. Backward compatibility between versions cannot always be guaranteed, although we are trying to keep it for two releases. When data is uploaded to Foretify Manager, it is automatically validated for compatibility.

Please note that forward compatibility—using results from newer versions of Foretify in older versions of Foretify Manager—is intentionally not supported.

Key Non-Compatible Changes in Recent Foretellix Releases

• With this release, Foretellix removes outdated and deprecated old checkers and related infrastructure, a detailed list and migration plan is shared in the Release Notes below.

Please review all Features marked as [Changed] in this release for further details on backward compatibility.

3.2 Evaluation V-Suite

[New] Expand Coverage Metrics to Remaining L0 Scenario Nodes (Phase 2) (SDL-72275)

Extended the NVIDIA evaluation V-Suite with additional coverage metrics.

• Added remaining coverage items for the drive_in_lane, nav_intersection, and nudge L0 scenario families, building on the centralized enum and per-node file structure introduced in Phase 1.
• Added a new Navigate Construction Zones L0 node with dedicated coverage metrics (subject to data availability from NVIDIA).
• Added slope coverage item applying across the V-Suite.

See NVIDIA Evaluation Scenarios.

[Changed] Extend vehicle.in_junction Modifier to Support List-Based Matching for junction_entry and turn_direction (SDL-74683)

The vehicle.in_junction scenario modifier was extended to accept lists of values for the junction_entry and turn_direction parameters.

• Previously, both parameters accepted only a single value, requiring scenario writers to duplicate scenario variants when multiple junction entries or turn directions were valid.
• Scenarios targeting multiple junction geometries — such as those based on the JAMA 58 scenario standard — can now specify a set of acceptable values directly on the modifier.
• Existing single-value usages remain unchanged; the change is purely additive.

See match scenario modifiers for the updated parameter descriptions.

[Deprecated] Remove all deprecated checks from old infrastructure (SDL-73637)

Breaking Change: Removal of Deprecated Vehicle Checks

All deprecated vehicle policy checks, physical checks, and the legacy kinematic_behavior watcher have been removed. These APIs were deprecated and have been replaced by the Global Evaluators framework, which provides richer intervals, configurable thresholds, and per-category monitoring.

Users referencing any of the removed symbols will see a compilation error and must migrate to the corresponding global evaluator.

3.2.1 What Was Removed

3.2.1.1 Kinematic infrastructure

3.2.1.2 Vehicle policy fields

3.2.1.3 Vehicle checker params

3.2.1.4 Issue kinds

The following issue_kind values have been removed: distance_physical, turn_physical, speed_physical, acceleration_physical, speed_policy, speed_limit, acceleration_policy, jitter_policy, ttc_policy, jerk_policy, unplanned_standing_time_policy, minimum_highway_speed_policy, minimum_highway_vru_distance_policy, off_lane, car_does_not_move.

3.2.1.5 C++ checker implementations

All legacy C++ checker classes have been removed from foundations_lib/checks/, including speed, acceleration, jerk, TTC, lane direction, movement, teleport, and unplanned standing checkers.

Migration Guide

Example: Disabling a Replacement Checker

If you previously disabled a deprecated checker (e.g., keep(vehicle_checker_params.enable_physical_acceleration_check == false)), use the new config:

extend ftlx_global_eval_config:
    set ego_kinematic_physical_checker_config.enabled = false

3.3 Foretify

[New] Caching for compilation, maps, and modeler (SDL-60084)

• Introduced caching in Foretify for compilation, maps, and the modeler to speed up repeated runs and reduce turnaround time when iterating on scenarios and environments.
• For more information, see Foretify caching.

3.4 Evaluation Pipeline

[New] NVIDIA flow with a single Foretify invocation (SDL-65646)

Foretify supports the NVIDIA work flow by running all required elements in a single invocation.

3.5 Known Limitations

Unsaved changes in Scenario Designer are lost when using the browser Back button (SDL-75521)

• A future fix will add a warning to inform users about potential data loss.

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.