[Development] Failed assertion in QSGBatchRenderer::ShaderManager::prepareMaterial()

Gunnar Sletta gunnar at sletta.org
Tue Feb 17 14:21:10 CET 2015


What is the output when you run with QSG_INFO=1 in the environment?

cheers,
Gunnar

> On 17 Feb 2015, at 13:07, Bojan Petrović <bojan85 at gmail.com> wrote:
> 
> Hi Gunnar,
> 
> It's the official dynamic build for VS 2013. I am working on a laptop with AMD Radeon HD 7470M card. Driver is 8.93-111205a-131054C (OpenGL version 6.14.10.11399).
> 
> Bojan
> 
> On 17 February 2015 at 16:56, Gunnar Sletta <gunnar at sletta.org <mailto:gunnar at sletta.org>> wrote:
> The renderer will give that assertion if your OpenGL context isn’t working correctly. For instance, if you compiled Qt with desktop gl, but you don’t have up to date drivers. Though this should have been caught by the error checking in the render loop already, so it is a bit puzzling.
> 
> What kind of Qt build is this? dynamic, desktop GL, Angle? What kind of driver / hardware?
> 
> cheers,
> Gunnar
> 
> 
>> On 17 Feb 2015, at 07:22, Bojan Petrović <bojan85 at gmail.com <mailto:bojan85 at gmail.com>> wrote:
>> 
>> Hi,
>> 
>> I am using Qt 5.4 on Windows. I have encountered a failed assertion in QSGBatchRenderer::ShaderManager::prepareMaterial(QSGMaterial * material), line 158 C++. It happens when I start my application, but not every time. This is the message I got in the console:
>> 
>> uniform highp float _qt_zRange;
>> void main()
>> {
>>     gl_Position = matrix * vertexCoord;
>>     color = vertexColor * opacity;
>>     gl_Position.z = (gl_Position.z * _qt_zRange + _qt_order) * gl_Position.w;
>> }
>> ***
>> QOpenGLShader::compile(Fragment): Fragment shader failed to compile with the fol
>> lowing errors:
>> *** Problematic Fragment shader source code ***
>> #define lowp
>> #define mediump
>> #define highp
>> varying lowp vec4 color;
>> void main()
>> {
>>     gl_FragColor = color;
>> }
>> ***
>> ASSERT: "shader->id_zRange >= 0" in file scenegraph\coreapi\qsgbatchrenderer.cpp
>> , line 158
>> 
>> Am I failing to respect some restriction or could this be a Qt bug?
>> 
>> I created a debugger dump and I;m downloading Qt source now so I can see it in debugger, but I am not familiar with that code so I doubt that I will help me too much.
>> 
>> Bojan
>> _______________________________________________
>> Development mailing list
>> Development at qt-project.org <mailto:Development at qt-project.org>
>> http://lists.qt-project.org/mailman/listinfo/development <http://lists.qt-project.org/mailman/listinfo/development>
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20150217/fb6ab1f9/attachment.html>


More information about the Development mailing list