All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 35861] New: [r300g] Oilrush: whiter triangle between center of the screen and horizon
Date: Fri,  1 Apr 2011 02:49:14 -0700 (PDT)	[thread overview]
Message-ID: <bug-35861-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=35861

           Summary: [r300g] Oilrush: whiter triangle between center of the
                    screen and horizon
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: medium
         Component: Drivers/Gallium/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: pavel.ondracka@email.cz


Created an attachment (id=45121)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=45121)
terminal output

There is a strange triangle of whiter area and missing effects between screen
center and horizon in Oilrush.

I'm attaching terminal output, however I don't think there is anything
important, just a few of: 

Mesa warning: glDraw[Range]Elements(start 130, end 877, count 1650, type
0x1403, indices=0x1c2)
    end is out of bounds (max=876)  Element Buffer 31 (size 3750)
    This should probably be fixed in the application.
and 

Mesa: User error: GL_INVALID_VALUE in glTexSubImage2D(xoffset+width)
OpenGL error: invalid value

However both of those errors are also present with llvmpipe which renders fine
(not 100% fine, but this bug is not present there). 
RADEON_NOT_TCL=1 also solves this issue, where READEON_DEBUG=noopt has no
effect.

BTW you need to set MESA_EXTENSION_OVERRIDE="-GL_ARB_draw_instanced" when using
llvmpipe of software TCL otherwise you run into other troubles like: 

GLShader::loadVertex(): error in
"core/shaders/default/meshes/vertex_base.shader" file
defines:
UNKNOWN,QUALITY_LOW,MULTISAMPLE_0,USE_INSTANCING,USE_TEXTURE_3D,USE_ALPHA_FADE,USE_ENVIRONMENT,OPENGL,USE_PSEUDO_INSTANCING,USE_PSEUDO_TRANSFORM,HAS_ARB_DRAW_INSTANCED,BASE_AMBIENT_REFLECTION_CUBE,AMBIENT,PAINT,OPACITY,MULTIPLY_0
0:194(39): error: `gl_InstanceID' undeclared
0:194(42): error: Operands to arithmetic operators must be numeric
0:194(19): error: cannot construct `ivec3' from a non-numeric data type
0:194(58): error: Operands to arithmetic operators must be numeric

and almost no rendering at all.

My system
GPU:RV530
mesa: 9f013a8233197d4a0482661cb37cfeac1a61b804
Kernel: 2.6.38

Oilrush version: 0.61

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-04-01  9:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01  9:49 bugzilla-daemon [this message]
2011-04-01  9:50 ` [Bug 35861] [r300g] Oilrush: whiter triangle between center of the screen and horizon bugzilla-daemon
2011-09-19  1:21 ` bugzilla-daemon
2011-09-19  7:05 ` bugzilla-daemon
2011-09-22 23:03 ` bugzilla-daemon
2011-09-23  7:48 ` bugzilla-daemon
2013-01-11 21:53 ` bugzilla-daemon
2013-01-14 13:12 ` bugzilla-daemon
2013-02-08 15:56 ` [Bug 35861] [r300g] Unigine Tropics: " bugzilla-daemon
2019-09-18 18:49 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-35861-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.