All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95285] [radeonsi] Tomb Raider: enabling TressFX makes hair disappear
Date: Thu, 05 May 2016 14:36:25 +0000	[thread overview]
Message-ID: <bug-95285-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 95285
           Summary: [radeonsi] Tomb Raider: enabling TressFX makes hair
                    disappear
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: kai@dev.carbon-project.org
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 123497
  --> https://bugs.freedesktop.org/attachment.cgi?id=123497&action=edit
No hair with TressFX

When I enable TressFX in Tomb Raider with the stack detailed below, Lara's hair
disappears partially (the part rendered with TressFX). Going back to "normal"
settings makes the hair fully visible again. The attached screenshot shows how
it looks with TressFX enabled.

I thought it might help to set the GLSL and GL overrides to 430 and 4.3
respectively, but then the game launcher refuses to start with tons of
GL_INVALID_OPERATION errors (see <https://paste.debian.net/hidden/84a0115a/>).
Not sure if this is a bug in the launcher or Mesa, but since 4.3 support is
imminent I thought I mention it here as well.


The following stack (Debian testing as a base) was used:
GPU: Hawaii PRO [Radeon R9 290] (ChipID = 0x67b1)
Mesa: Git:master/76a36ac3ea
libdrm: 2.4.67-1
LLVM: SVN:trunk/r268388 (3.9 devel)
X.Org: 2:1.18.3-1
Linux: 4.5.1
Firmware: firmware-amd-graphics/20160110-1
libclc: Git:master/20d977a3e6
DDX: 1:7.7.0-1

Let me know, if you need something else.

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

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

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

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

             reply	other threads:[~2016-05-05 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05 14:36 bugzilla-daemon [this message]
2016-05-05 14:39 ` [Bug 95285] [radeonsi] Tomb Raider: enabling TressFX makes hair disappear bugzilla-daemon
2016-05-05 15:09 ` bugzilla-daemon
2016-05-05 16:38 ` bugzilla-daemon
2016-05-05 17:07 ` bugzilla-daemon
2016-05-05 18:28 ` [Bug 95285] [radeonsi,apitrace] " bugzilla-daemon
2016-05-05 18:58 ` 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-95285-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.