On 2/17/21 4:30 PM, Daniel Patel wrote:
Regarding assimp, it is not in qt3d_build_dir/plugins/sceneparsers,
only gltf is there.
I see in the sceneparsers\assimp source code that it seems to use
zlib, so perhaps this is the problem. I will recompile things with
zlib library included.
The abil
Regarding assimp, it is not in qt3d_build_dir/plugins/sceneparsers, only
gltf is there.
I see in the sceneparsers\assimp source code that it seems to use zlib, so
perhaps this is the problem. I will recompile things with zlib library
included.
The ability to now choose opengl/vulkan/metal/directx
On 2/17/21 11:15 AM, Daniel Patel wrote:
Actually all errors except the missing assimpl plugin problem went
away when also setting environment variable QSG_RHI_BACKEND to opengl
So the only open question now is how to get the assimp to work.
Do you have a sceneparsers/libassimpgsceenimport in y
Hi Nuno,
Check your implementation of type(). It should return something unique for all
the different 'source' values (i.e. for every different vertex+fragment shader
combinations). Right now, with the same static type object is returns,
VSMaterial::createShader() is only ever called once, so a
Actually all errors except the missing assimpl plugin problem went away
when also setting environment variable QSG_RHI_BACKEND to opengl
So the only open question now is how to get the assimp to work.
And a new question is: why does it matter what QSG_RHI_BACKEND is set to
when I already specified
Thank you Mike for telling how to send in parameters correctly. For the
qt-configure-module.bat the syntax "-DFEATURE_qt3d_simd_avx2=ON" worked but
I didn't need to set it. The other syntax "-- -qt3d-simd=avx2" worked for
the qt6 configure script and I was able to tell it where zlib was by using
"c
