Explore the features of Qt 3D Design Studio
summary
Harman uses Qt 3D Design Studio to build multi‑display automotive HMIs (up to four or five screens) and finds that having a single shared project with branch-based sync per product increment avoids massive rework; heavy, costly visuals get moved to C++/vertex shaders to hit CPU and FPS KPIs; embed QML or use OpenGL texture paths for efficiency; treat 3D Studio files as a living requirement spec and measure performance continuously to find hotspots.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 3:11Qt 3D Studio workflow
- 6:06Shared project and feedback loop
- 10:20Qt 3D Studio as requirement spec
- 13:17Designer-developer collaboration limits
- 15:44Performance and architecture choices
- 18:07Practical implementation tips
- 18:50Measuring and optimizing KPIs
- 19:54Summary and Q&A
related talks
48mBuilding Desktop and Embedded Uis with Qt 3D
51mQt Quick 3D & the Emerging Developer Paradigm
48mBuilding Desktop and Embedded Uis with Qt 3D
01h 12mQt/3D QML Scripting for UI Designers and Hackers
01h 35mIntroduction to Qt 3D - Giuseppe D’Angelo - [ACCU 2017]
01h 08mDesigning UIs with Qt Quick 1/6 - Design Workflow Part 1
10mLightning Talk, Qt 3D CAD demo
01h 25mAdvanced Qt -A Deep Dive 1/6 Graphics View Part 1