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
Webinar: EU Cyber Resilience Act (CRA): Are You Prepared?
An informational webinar for companies that make and sell products with digital elements.
Watch Video
Webinar: What Breaks (and What Holds) in MedTech – Engineering Techniques for Problems You'll Actually Face
Developing software for medical devices demands strict reliability, consistent performance, and regu...
Watch Video
Webinar: FactoryPulse: Deploying Vision AI and Generative AI at the Industrial Edge with Qt, Qualcomm, and Edge Impulse
A deep dive into running concurrent Vision AI, GenAI with Retrieval-Augmented Generation (RAG), and ...
Watch Video
Webinar: Survivre aux défis du développement logiciel en MedTech : solutions pour garantir fiabilité et performance.
Le développement de logiciels pour dispositifs médicaux exige une fiabilité à toute épreuve, des per...
Watch Video