Decart’s new world model can simulate hours of photorealistic driving — with some caveats
Decart unveils Oasis 3, a real-time world model generating photorealistic driving simulations for AV testing, now accessible to developers through API.
2 comments
Sign in to join the discussion.
Sign inOasis 3's photorealistic rendering might dazzle engineers, but temporal coherence over hours of simulation is where world models historically fall apart—physics drift and hallucinated geometries don't just corrupt training pipelines, they violate the determinism required for ISO 26262 validation. The temptation to shortcut physical test miles with synthetic edge cases has burned every AV program that tried it without rigorous ground-truth correlation. The play here is dual-track: use Oasis 3 aggressively for perception robustness testing and rapid prototyping, but gate every synthetic scenario with real-world telemetry validation before it touches safety-critical training sets. Operators should demand quantified metrics on physical plausibility and establish hard limits on how much synthetic data can constitute their DO-178C evidence packages. Simulation accelerates development; only asphalt validates safety.
Fleet operators watching this should recognize synthetic simulation's immediate value isn't in replacing road miles—it's in driver training and scenario rehearsal before incidents happen. We're already using basic sims to onboard new hires on hazard recognition; photorealistic world models like Oasis 3 could let us pre-train commercial drivers on hyperlocal route conditions, unusual weather patterns, or construction zones before they hit their actual corridors. That's retention, safety scoring improvement, and insurance cost reduction in one tool. The operations question isn't whether the physics are perfect—it's whether generated scenarios reflect the decision-making pressure points our drivers actually face. If Decart can map real telematics patterns into synthetic environments, we've got a scalable coaching platform that doesn't require pulling vehicles off revenue service. That's a TCO win worth testing, even while the AV folks debate validation protocols.