public inbox for dri-devel@lists.freedesktop.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77785] New: (radeonsi) Some lighting issues in games, textures goes black
Date: Tue, 22 Apr 2014 21:23:44 +0000	[thread overview]
Message-ID: <bug-77785-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1345 bytes --]

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

          Priority: medium
            Bug ID: 77785
          Assignee: dri-devel@lists.freedesktop.org
           Summary: (radeonsi) Some lighting issues in games, textures
                    goes black
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: smoki00790@gmail.com
          Hardware: x86 (IA32)
            Status: NEW
           Version: 10.1
         Component: Drivers/Gallium/radeonsi
           Product: Mesa

Created attachment 97777
  --> https://bugs.freedesktop.org/attachment.cgi?id=97777&action=edit
bad case

Athlon 5350 (so Radeon R3 or Radeon 8400), current Debian Sid and mesa 10.1. I
also tried current mesa git master 10-devel, kernel 3.15-rc3, etc... the same
issue with lighting appear. hyperz (enabled/disabled) does not metter here.

 So, in wine with some opengl games (i guess native are also affected, but not
found example) for example AirStrike3D or 18 WoS: Pedal to the Metal games. In
18 WoS: Pedal to the Metal. issue appear when i turn on truck headlights,
everything beside headlights goes black of course until i turn off
headlights... some screenshots i will attach.

 And yeah swrast works OK, fglrx too :)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2749 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2014-04-22 21:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22 21:23 bugzilla-daemon [this message]
2014-04-22 21:27 ` [Bug 77785] (radeonsi) Some lighting issues in games, textures goes black bugzilla-daemon
2014-04-22 21:28 ` bugzilla-daemon
2014-04-22 21:29 ` bugzilla-daemon
2014-04-22 21:29 ` bugzilla-daemon
2014-04-22 21:30 ` bugzilla-daemon
2014-04-22 21:45 ` bugzilla-daemon
2014-04-22 22:25 ` bugzilla-daemon
2014-04-23  9:27 ` bugzilla-daemon
2014-04-23 13:57 ` bugzilla-daemon
2014-04-23 16:11 ` bugzilla-daemon
2014-05-16 23:01 ` bugzilla-daemon
2014-05-17  2:12 ` bugzilla-daemon
2014-05-17 12:06 ` bugzilla-daemon
2014-05-17 12:27 ` bugzilla-daemon
2014-05-17 13:10 ` bugzilla-daemon
2014-05-17 13:11 ` bugzilla-daemon
2014-05-17 13:20 ` bugzilla-daemon
2014-05-17 14:15 ` bugzilla-daemon
2014-05-17 14:52 ` bugzilla-daemon
2014-05-17 15:38 ` bugzilla-daemon
2014-05-18 15:27 ` bugzilla-daemon
2014-05-19  6:09 ` bugzilla-daemon
2014-05-20  0:31 ` bugzilla-daemon
2014-05-20  0:32 ` bugzilla-daemon
2014-05-20 13:30 ` bugzilla-daemon
2014-05-20 17:08 ` bugzilla-daemon
2014-05-20 18:58 ` bugzilla-daemon
2014-05-20 18:59 ` bugzilla-daemon
2014-05-21 14:58 ` bugzilla-daemon
2014-05-21 17:52 ` bugzilla-daemon
2014-07-15  7:44 ` 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-77785-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox