Outpace.
The Panoramic 3D Cockpit
Your Designers and Developers
Actually Want to Build

Yes, on mid-range silicon. Outpace runs a full pillar-to-pillar 3D cockpit on a MediaTek MT8676, a mid-range automotive SoC rather than a flagship board. Qt Quick 3D is built to render on embedded devices. Photorealistic models, weather and terrain modes, and ADAS visualisation run from one scene graph at real-time frame rates while the same chip still serves the cluster, IVI, and ADAS.

Through a separate, certified safety system that stays isolated from the main cockpit.

Qt Safe Renderer renders the safety-critical content, including cluster telltales, warnings, and lane and hazard visualization, on its own isolated system. That can be a dedicated RTOS, on separate hardware if the program needs it, or its own container on a hypervisor. The safety layer and Qt Quick 3D never share a rendering pipeline. What they share is the display output, composited onto the same screens.

Qt Safe Renderer is TÜV NORD certified to ISO 26262 up to ASIL-D. This way you avoid late-program retrofits as the safety path is designed in from the first prototype.

Yes. The UI is built from the same QML components, so the look and the brand identity carry across every screen and across platforms without being rebuilt. Outpace runs on Android Automotive today, and the same cockpit runs on QNX, on Linux, and on the SoC families automotive programs already use. The next operating-system or silicon decision doesn't force an HMI rewrite, so the experience you design once follows the program across platforms.

You don't have to replace Android Automotive. Qt isn't tied to it.

For this project, Qt was built on top of Android Automotive. The native AAOS services stay in place, including media, maps, connectivity, and apps, and Qt handles the cockpit's 3D and visual design. That is the configuration Outpace ships in.

Within an Android Automotive program, how you split the work is up to you. Qt can deliver the full 2D and 3D experience, or you can keep Android Automotive for the 2D and use Qt for the 3D, whichever you prefer.

If a program would rather not run Android Automotive at all, Qt runs natively on Linux and QNX, and the same cockpit goes there too. The choice of operating system stays yours.

The practical alternative is a rendering stack built for embedded automotive silicon instead of for gaming. Our answer to that is Qt Quick 3D.

It matches a 3D engine on screen and beats it in production and over the program's life. With Outpace, we proved it renders the full panoramic dashboard on a mid-range automotive chipset, at the quality your designers signed off on and on less RAM and CPU than leading 3D-engine alternatives.

Certified ASIL-D safety rendering runs alongside, and the same cockpit ports to Linux, QNX, and other OSs without a rewrite.

Outpace is Qt's reference panoramic cockpit, a full pillar-to-pillar real-time 3D in-vehicle experience on a 44.1-inch panoramic mini-LED at 7680 × 936.

Its reference configuration runs on Android Automotive on a MediaTek MT8676, using Qt Quick 3D, Qt for Android Automotive, and Rendering as a Service, with Qt Safe Renderer for the certified safety layer.

The same architecture scales to other SoC families and operating systems, and down to a single curved cluster or a three-screen split.