[Development] Problems running Qt3D examples

Sean Harmer sean.harmer at kdab.com
Tue Mar 24 10:33:53 CET 2015


Hi,

On Tuesday 24 March 2015 13:09:23 Christian Gagneraud wrote:
> Hi there,
> 
> I've just build qt5 from git (5.5 branch, commit cdc3bf5) and I'm having
> problems running some qt3d examples.
> 
> I've run *all* examples and only a few don't work:
> - assimp, multiviewport: window content is black

This will only work if the assimp libs and headers are found by pkgconfig at 
build time. Remove your Qt3d build including the .qmake.cache file, install the 
assimp development package and rebuild Qt3d. If it still fails to detect 
assimp take a look in the generated config.log file for hints.

> - gltf: window content is never drawn

The gltf spec is still evolving. We should disable this until it matures more. 
Please disregard for now.

> Don't know if it's related, but the following examples gives me a
> warning message 'Xlib: extension "NV-GLX" missing on display ":0"' but
> run fine:
> - simple-cpp
> - materials
> - loader-qml
> - deferred-renderer-qml
> - deferred-renderer-cpp
> - cylinder-cpp
> - cpp_example
> - wave
> - wireframe

Yes I see this too but have not been able to track it down yet but I don't see 
any bad side effects from it.

> 
> These one don't run and give me the NV-GLX warning:
> - gltf
> - assimp
> 
> These ones don't run and don't produce the NV-GLX warning:
> - multiviewport

This also uses the assimp scene loader so without assimp support you won't see 
anything here.

> 
> Some examples produce as well messages like 'Xlib: sequence lost
> (0x1026b > 0x26d) in reply type 0x23!':
> - shadow-map-qml
> - deferred-renderer-qml
> - defered-renderer-cpp
> 
> All other examples run fine with no Xlib warnings.
> 
> I'm running KUbuntu 14.10, with all the updates, my GPU config is:
> GL_VERSION:  4.4.0 NVIDIA 331.113
> GL_VENDOR:   NVIDIA Corporation
> GL_RENDERER: Quadro 600/PCIe/SSE2
> 
> I'm not sure what the problem is, is it a Qt issue, an NVIDIA driver
> issue or maybe i'm missing some libs or using the wrong OpenGL lib?
> 
> Here are some libs debugging info:
> $ LD_DEBUG=libs ./assimp/assimp 2>&1 | grep -i gl | grep -v libglib
>       26728:     find library=libGL.so.1 [0]; searching
>       26728:       trying
> file=/home/krys/src/qt5/build/qtbase/lib/libGL.so.1
>       26728:       trying file=/usr/lib/nvidia-331/libGL.so.1
>       26728:     find library=libnvidia-glcore.so.331.113 [0]; searching
>       26728:       trying
> file=/usr/lib/nvidia-331/libnvidia-glcore.so.331.113
>       26728:     calling init:
> /usr/lib/nvidia-331/libnvidia-glcore.so.331.113
>       26728:     calling init: /usr/lib/nvidia-331/libGL.so.1
>       26728:     find library=libxcb-glx.so.0 [0]; searching
>       26728:       trying
> file=/home/krys/src/qt5/build/qtbase/lib/libxcb-glx.so.0
>       26728:       trying file=/usr/lib/x86_64-linux-gnu/libxcb-glx.so.0
>       26728:     calling init: /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0
>       26728:     calling init:
> /home/krys/src/qt5/build/qtbase/plugins/xcbglintegrations/libqxcb-glx-integr
> ation.so Xlib:  extension "NV-GLX" missing on display ":0".
>       26728:     calling fini:
> /home/krys/src/qt5/build/qtbase/plugins/xcbglintegrations/libqxcb-glx-integr
> ation.so [0]
>       26728:     calling fini: /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0 [0]
> 26728:     calling fini: /usr/lib/nvidia-331/libGL.so.1 [0]
>       26728:     calling fini:
> /usr/lib/nvidia-331/libnvidia-glcore.so.331.113 [0]
> 
> So it looks to me that i'm using the right freshly built Qt library and
> the right NVidia proprietary drivers.

All looks as I see too, except for the lack of assimp support.

Cheers,

Sean
--
Dr Sean Harmer | sean.harmer at kdab.com | Managing Director UK
Klarälvdalens Datakonsult AB, a KDAB Group company
Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
KDAB - Qt Experts - Platform-independent software solutions



More information about the Development mailing list