QtWebEngine

Ipv4 or IPv6 you need an ip 'ws:// {ip}:{port}' or if you need open ssl use 'wss://' you can use Qurl.

Hi @Pippin, You're right that managing 20k+ users with QTcpServer and raw sockets can be very resource-heavy. Instead of using plain HTTP, I'd recommend looking into WebSockets with QWebSocketServer, which allows real-time, two-way communication and scales better for game updates. For encryption, you can either use QSslSocket directly or offload SSL using a reverse proxy like Nginx to handle HTTPS/WSS and let your server deal with plain TCP internally. As for syncing game state: the server should act as the single source of truth. When Player A makes a move, the server processes it, validates it, then pushes the same update to Player B and any watchers using WebSocket messages. This way, all players receive the actions in the same order, keeping everything in sync. Starting with a small prototype using a few clients will help you get the architecture right before scaling up. Good luck!

@Dilloncarr hi, From what @cobook wrote, the main fix was to move to Ubuntu. Did you already tried that ? Also, which version of Qt are you using ? How did you install it ?

Mingw does not provide webengine. You have to use msvc

You either have to build QWebEngine (or WebEngineWidgets) from source if you want it for Qt 6.7.2. QWebEngine is available through the Qt Maintenance Tool only in certain versions. For example 6.6.2. I just upgraded from 6.6.2 to 6.9.0 but faced the same problem. Luckily, 6.9.1 (downloaded via Maintenance Tool) Includes Qt WebEngine Module for msvc2022_64, so I upgraded directly to 6.9.1.

Hi @Axel-Spoerl, Just checking in to see if you had a chance to look at the code I posted earlier. I'd really appreciate any insights or suggestions when you get a moment. Thanks again for your time and guidance. Regards, Soumyanil

Hello, @raphm01 Doyou resolve your problem? I have similar issue with terrible flickering of Webpage when using PyQT6 on windows OS

@wojciech_kazubski If you suspect the issue is related to the driver, post your problem in Nvidia forum and you may be able to be helped. Or you can download or build a new driver and try it out. On Linux, you can try to run your debug build with valgrind for some clues.

This issue is reported here: https://bugreports.qt.io/browse/QTBUG-136953. And there's a fix to qtwebengine-chromium: https://codereview.qt-project.org/c/qt/qtwebengine-chromium/+/646656

This command worked for me sudo pacman -S libxml2-legacy

I found the issue. When I migrated to the new QT Visual Studio tools upon being prompted by VS (I'm upgrading from Qt 5.15.0), this section was added to a higher level .props file where it was not previously. <PropertyGroup Label="QtSettings"> <QtInstall>Qt_Qt-6.9.0</QtInstall> <QtModules>core;gui;network;widgets;webenginecore</QtModules> </PropertyGroup> Deleting the "network" and "webenginecore" items got the webenginecore error to disappear.

Looks like this is going to be fixed in Qt 6.9.1, related patch - https://codereview.qt-project.org/c/qt/qtwebengine-chromium/+/634034

I've reported this issue as a bug at: https://bugreports.qt.io/browse/QTBUG-136652

Do we have a solution for this?

@DJBob-Gaming Is this spam? Does not sound like any answer to the question.