Summary: | Some Ogre 2.1 demos doesn't render properly | ||
---|---|---|---|
Product: | Mesa | Reporter: | MWATTT <megwattt> |
Component: | Mesa core | Assignee: | mesa-dev |
Status: | RESOLVED NOTOURBUG | QA Contact: | mesa-dev |
Severity: | normal | ||
Priority: | medium | ||
Version: | 11.2 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Apitrace of "Sample_Hdr" demo
The demo on Catalyst (good) The demo on r600g (bad) |
Description
MWATTT
2016-04-24 19:39:00 UTC
Created attachment 123218 [details]
Apitrace of "Sample_Hdr" demo
Created attachment 123262 [details]
The demo on Catalyst (good)
Created attachment 123263 [details]
The demo on r600g (bad)
The apitrace contains invalid OpenGL calls, which may work with incorrect drivers, but not with Mesa. This is the list of GL errors: Mesa: User error: GL_INVALID_ENUM in glTexImage2D(incompatible format = GL_DEPTH_COMPONENT, type = GL_DEPTH_COMPONENT) Mesa: User error: GL_INVALID_ENUM in glTexImage2D(incompatible format = GL_DEPTH_STENCIL, type = GL_DEPTH_STENCIL) Mesa: User error: GL_INVALID_OPERATION in glTexImage2D(incompatible format = GL_BGR, type = GL_UNSIGNED_SHORT_5_6_5) Mesa: User error: GL_INVALID_OPERATION in glTexImage2D(integer/non-integer format mismatch) Mesa: User error: GL_INVALID_VALUE in glBindAttribLocation(index) Mesa: User error: GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete framebuffer) Mesa: User error: GL_INVALID_FRAMEBUFFER_OPERATION in glMultiDrawElementsIndirect(incomplete framebuffer) The GLSL compiler also detected uninitialized variables in various shaders: 0:249(28): warning: `nNormal' used uninitialized 0:252(14): warning: `material' used uninitialized 0:252(14): warning: `ROUGHNESS' used uninitialized 0:288(54): warning: `diffuseCol' used uninitialized 0:290(37): warning: `specularCol' used uninitialized etc. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.