Question about future of Qt3d with Python
-
wrote on 5 Jun 2025, 21:12 last edited by
Hi,
My team is working on a PySide 6 based project using Qt3d heavily. It's a level editor for some old game. The project is still in development, although started a good few years ago. In the meantime I learnt, that Qt3d is deprecated...Given the fact, that we have another year or two of development (in our spare time), I'm wondering if there is even a point in continuing with this technology. Can someone try to estimate how long this technology may be functional? I may not need any updates for Qt3d, but I wonder if bindings for Qt3d will be made for another time, for future versions of Python. What I would like to avoid is a situation, where let's say in 5 or 10 years time, nobody won't be able to run our app on the latest version of Windows, because it may no longer support Python 3.12 or 3.13 or if the underlying Qt libraries simply won't run on Windows 12 etc...
Is there any way to tell how long the current version 6.9 may be still running on future systems?
-
wrote on 11 Jun 2025, 10:47 last edited by
Similarly to what was discussed in https://forum.qt.io/topic/159077/moving-away-from-qt3d-is-qtquick3d-ready/2 I'd say you might need to evaluate if you can:
- Rely on QtRHI for a new rendering ad-hoc system
- Check if Qt Quick 3D is enough for your project.
Because it's not tied anymore to the qt meta repo, we might face issues from the Qt for Python side of things, and we might stop providing it in newer versions. So far, it's present in 6.9, and hopefully we can provide it for 6.10.
Like any piece of software, being deprecated since 6.8, Qt3D will not get new features, or might not have active development. I wouldn't expect for it to go completely away in 1-2 years, but it's highly probable that it might be fully replaced in a few years.
This is only my 'feeling' and not what it will happen.
1/2