For the average Houdini user, are there any noticeable differences between the QT4 & QT5 builds?
I,e - “This works in one but not the other” or “This feature is faster in one than the other”
Functional Differences Between Qt4 & 5 versions
10150 12 4- Luke Letellier
- Member
- 241 posts
- Joined: 4月 2014
- Offline
- mtucker
- スタッフ
- 4517 posts
- Joined: 7月 2005
- Offline
- rvinluan
- スタッフ
- 1274 posts
- Joined: 7月 2005
- Offline
Hi Luke,
The feature sets in the Qt4 and Qt5 builds are the same.
And in theory you should have the same general user experience in both builds however since the Qt5 build is much newer than the Qt4 one there are more issues (UI-related) that need to be ironed out of it.
One area where you will notice a big difference between Qt4 and Qt5 is with Python Panel development. The Qt4 builds require that you use PySide/PyQt4 for building UI in Python Panels while the Qt5 builds require that you use PySide2/PyQt5. The same goes for building standalone Python UI in Houdini. And similarly for building C++ UI in the HDK.
My suggestion is to start with the Qt5 build and fallback to Qt4 only if you run into strange UI issues that make Houdini unusable. Though if you fallback to Qt4 please submit bug reports for the Qt5 problems so that we can fix them for later releases.
I hope this helps.
Cheers,
Rob
The feature sets in the Qt4 and Qt5 builds are the same.
And in theory you should have the same general user experience in both builds however since the Qt5 build is much newer than the Qt4 one there are more issues (UI-related) that need to be ironed out of it.
One area where you will notice a big difference between Qt4 and Qt5 is with Python Panel development. The Qt4 builds require that you use PySide/PyQt4 for building UI in Python Panels while the Qt5 builds require that you use PySide2/PyQt5. The same goes for building standalone Python UI in Houdini. And similarly for building C++ UI in the HDK.
My suggestion is to start with the Qt5 build and fallback to Qt4 only if you run into strange UI issues that make Houdini unusable. Though if you fallback to Qt4 please submit bug reports for the Qt5 problems so that we can fix them for later releases.
I hope this helps.
Cheers,
Rob
- Luke Letellier
- Member
- 241 posts
- Joined: 4月 2014
- Offline
- Alexey Vanzhula
- Member
- 538 posts
- Joined: 12月 2006
- Offline
- SreckoM
- Member
- 379 posts
- Joined: 12月 2006
- Offline
- Alexey Vanzhula
- Member
- 538 posts
- Joined: 12月 2006
- Offline
SreckoM
I can not start Qt5 build on KDE Neon which has latest Qt libraries…
Can't try linux version this time, but I think there is a problem with environment variable where you should override Qt libraries path to houdini folder.
Try to add this line to /home/user/houdini16.0/houdini.env:
LD_LIBRARY_PATH = /path/to/your/houdini/bin/folder
Or google for something like “override environment variables in linux”
Edited by Alexey Vanzhula - 2017年3月18日 15:35:17
- Ostap
- Member
- 209 posts
- Joined: 11月 2010
- Online
vuxSreckoM
I can not start Qt5 build on KDE Neon which has latest Qt libraries…
Can't try linux version this time, but I think there is a problem with environment variable where you should override Qt libraries path to houdini folder.
Try to add this line to /home/user/houdini16.0/houdini.env:LD_LIBRARY_PATH = /path/to/your/houdini/bin/folder
Or google for something like “override environment variables in linux”
Hi,
I had the same problem (only with Qt5 build) but in my case it was issues with OpenGL context,
reinstall graphics card driver helped.
Cheers
Ostap
Edited by Ostap - 2017年4月5日 05:35:33
- SreckoM
- Member
- 379 posts
- Joined: 12月 2006
- Offline
- Ostap
- Member
- 209 posts
- Joined: 11月 2010
- Online
- SreckoM
- Member
- 379 posts
- Joined: 12月 2006
- Offline
- SreckoM
- Member
- 379 posts
- Joined: 12月 2006
- Offline
- TheTex
- Member
- 7 posts
- Joined: 4月 2014
- Offline
-
- Quick Links