Common Graphics Performance and Rendering-Related Issues when Moving from Qt 5 to 6
Qt 6.0 introduced some important changes in the Qt graphics stack, further followed in the 6.x series by many improvements, with more coming in Qt 6.8 and 6.9. Over the course of the Qt 6 releases, some users found that migrating existing projects from Qt 5 (and occasionally Qt 4) sometimes tend to run into visual issues, rendering performance regressions, unexpected CPU, GPU, and memory usage profiles, or perceived "memory leaks"; problems that were not there before with Qt 5. Sometimes these turn out to be misunderstandings. Sometimes they turn out to be real problems. And sometimes they turn out to be something in-between. Taking Qt 6.8 LTS as the basis, while also looking at a few upcoming Qt 6.9 improvements, this talk is going to walk through a number of typical problems and questions that tend to pop up when moving graphics-intensive Widget and Qt Quick applications onto modern Qt 6 versions, focusing on painting, windowing, 3D acceleration, and various application-level consequences of rendering engine internals.
Oh, here is more
On-Demand Webinar: How to Design Production Ready UX
We will do a deep dive into the new tool for embedded UI/UX designers: available in beta by the time...
Watch VideoOn-Demand Webinar: Qt Custom Drawing Methods: From Past to Present
Qt's custom painting story spans decades, from QPainter and classic widgets to hardware-accelerated ...
Watch VideoOn-Demand Webinar: From Rectangles to Shader Effects: How Controls, Graphs and Everything Between Works Together
A hands-on look at Qt's UI framework. Discover how to combine basic controls, animations, graphs, an...
Watch VideoOn-Demand Webinar: Designing for Real-World Devices: Why Is It a Field of Its Own and How Qt Is Tackling the Most Complex Design Challenge
In this keynote, we discuss UX design for real-world devices and why we believe it needs solutions t...
Watch Video