Failed to load texture: Handling Babylon.js Texture Constructor Errors

Goal

To design a robust texture loading strategy in Babylon.js that gracefully handles the Failed to load texture error emitted by the Texture constructor.

Constraints & Uncertainties

The error can arise from network failures, invalid URLs, or CORS restrictions. Different Babylon.js releases may alter the error message format. Texture cache size limits may indirectly cause load failures when the cache is full. Developers can supply an onError callback or use Texture.createFromURL for promise-based handling, but the optimal balance between retry logic, placeholder substitution, and cache eviction remains unclear.

Questions

1. How can a developer reliably detect whether a Failed to load texture error is due to a missing file versus a CORS policy restriction?
2. What configuration or coding patterns allow automatic retry of texture loads after a transient network error without flooding the server or causing UI stalls?
3. In what scenarios should the texture cache be resized or cleared to prevent load failures, and what best practices exist for managing cache eviction when the cache limit is reached?