The LuxMark 3 tool is now patched to be built with Qt5 so that simplifies a lot the dependencies (before it required to build Qt4 first that required to build GCC7 first that required GCC 10… that was a hell of a hell
![Laughing :lol:](./images/smilies/icon_lol.gif)
Some highlights:
- Luxmark 3.1 now catches all the various OpenCL errors (missing platform, platform without device, OpenCL compilation error…) instead of just crashing, printing the useful log message.
- The log is also printed on stderr to avoid losing it in case of LuxMark crash.
- Various environment variables to select specific code paths (BVH, QBVH, image support or not), add extra OpenCL compiler options, pre-fill submission form, etc.
- The bugfix to be compatible with LLVM-based platforms (Clover, ROCm), see https://forums.luxcorerender.org/viewtopic.php?t=4600
I only tested those patches on Linux, the build script is meant to run on Linux (I use it on Ubuntu 22.04).
This was motivated to make LuxMark 3 a good tool to test and debug OpenCL platforms.
![Cool 8-)](./images/smilies/icon_cool.gif)
I use LuxMark 3 a lot to test OpenCL platforms including the work-in-progress and promising RustiCL.
Maybe in the future I'll evaluate the ability to make a flatpak from that (including all the useful patches) as I have verified it's possible to run a flatpak application with a non-system OpenCL platform using some advanced flatpak options. It means an OpenCL platform developer would be able to test its work-in-progress OpenCL implementation with the flatpak.
Maybe some features can be ported to the work-in-progress LuxMark 4 or even the released LuxCoreRender if there are things that can be used?
![Question :?:](./images/smilies/icon_question.gif)