Is a Global Retry Policy Needed for Babylon.js Asset Loading?

Asset Loading Retry in Babylon.js

Babylon.js exposes a SceneLoader option called retry that can be set per asset load, but the official documentation does not detail its default value or limits. In current releases the default behavior is to attempt a single load with no automatic retry; if the request fails, an error event is emitted and the asset is omitted. There is no global retry policy that applies to all asset loads; each load must specify retry logic manually or rely on external code. The retry logic, when enabled, does not implement exponential backoff or delay between attempts; it simply retries immediately up to the configured count. The API for retry options was present in v4.x but was removed or refactored in the 5.0 release, making the behavior version‑sensitive.

Given these observations, the following questions remain unresolved:

• What is the default retry count for SceneLoader in Babylon.js v5?
• Does the retry option support exponential backoff or configurable delay?
• Should a global retry policy be reintroduced to automatically retry all failed asset loads with configurable backoff?