thanks for trying to shed some light on this. As I said, I have already installed the vulkan SDK (the "official" one from LunarG as I am trying to build for windows). I have even added the include directory directly in the *.pro file, and have observed that when opening the qt3d project with QtCreator, it can correctly resolve the vulkan libraries, so I think this is not the problem. I will try your suggestion of putting the vulkan headers directly in the qt directory and see if that gets me anywhere..

@kkoehne Ah I see, so it is an issue with the source tree, but in particular with MSVC static builds. I guess I'll also playing around with a workaround for now as I'd like to make use of changes I sent upstream for 6 but I'm sure 6.0.1 shouldn't be too far behind since this is a little more than a minor issue. Thanks.

@noone said in QtFuture not found: workaround ? #include <QFuture>

@EmileDW See https://doc-snapshots.qt.io/qt6-dev/android.html "Android 6.0 or later (API level 23 or higher)"

As the configure scripts prints at the end: if you re-run configure, you have to clean first. Otherwise you may have leftovers from your previous configure/build attempt that will make it so that not all tests are rerun.

Hi, From the looks of the report, you should be able to build the dev branch and test it with your code. Unless you are using one of the few effects that have been removed.

Hi this might be due to the new Qt RHI, an abstraction over OpenGL, Vulkan, Metal, DirectX (might have forgotten some or mentioned some that shouldn't be). Qt Quick will no longer be speaking directly to OpenGL but there will be an abstraction on top of it to ensure compatility with other graphical stacks. You will get more info about this by googling around or watching this webinar : https://www.youtube.com/watch?v=eInD6H4XrpM

https://bugreports.qt.io/browse/QTBUG-87735 bug fixed) Fix Version/s: 6.0.0 RC

@Christian-Ehrlicher I understand the reasons why they deprecate it. I have the same use-case as described there. So a solution seems to be: bool SortedModelVectorView::lessThan(const QModelIndex &source_left, const QModelIndex &source_right) const{ const auto left = ....; const auto right = ....; switch (left.type()) { case QVariant::Int: return left.value<int>() < right.value<int>(); case QVariant::Bool: return left.value<bool>() < right.value<bool>(); case QVariant::String: return left.value<QString>() < right.value<QString>(); } qWarning() << "Can not compare " << left << " and " << right << ". Type " << left.type() << " not handled"; return 0; Where you have to implement all types that you will handle. Ok this is one solution, but still why says QMetaType::compare that a comparison is not possible?