View Single Post
Old 11-07-2025, 09:48 AM   #12
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,930
Karma: 207182180
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by MacDougal View Post
QT_QUICK_BACKEND=software
I have great luck with QT_QUICK_BACKEND=software on Linux systems with proprietary nvidia drivers (and Qt6.8+). It makes QWebEngine rendering on my system (which is not underpowered in the least) positively snappy again. It also gets rid of the annoying "driver does not support GBM" warning. But I don't have to use QTWEBENGINE_CHROMIUM_FLAGS=--disable-gpu in that situation. It renders fine--it's just sluggish.

On Windows, I find that QT_QUICK_BACKEND=software shifts any and all GPU QWebEngine hardware usage to the CPU regardless of whether QTWEBENGINE_CHROMIUM_FLAGS=--disable-gpu is set or not.
DiapDealer is offline   Reply With Quote