dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95285] [radeonsi,apitrace] Tomb Raider: enabling TressFX makes hair disappear
Date: Thu, 05 May 2016 18:58:09 +0000	[thread overview]
Message-ID: <bug-95285-502-O4vekoard1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95285-502@http.bugs.freedesktop.org/>


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

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

Kai <kai@dev.carbon-project.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |NOTOURBUG
             Status|NEW                         |RESOLVED

--- Comment #6 from Kai <kai@dev.carbon-project.org> ---
Ok, I did one last test. I only set "MESA_GLSL_VERSION_OVERRIDE=430" (notice
the missing override for MESA_GL_VERSION_OVERRIDE in comparison to comment #0).
When launched this way, TressFX works (at least in the benchmark, I used to
check this and to produce the trace from comment #5)!

I'm closing this bug as NOTOURBUG as it seems the game is using functionality,
when the TressFX option is enabled, it should only use when GLSL 4.30 is
available. Or put differently: it shouldn't offer TressFX unless GLSL 4.30 is
available, ie. this is a game bug.

The launcher problem described in comment #0 seems to stem from the fact, that
MESA_GL_VERSION_OVERRIDE also overrides the compatibility profile version as
well and the launcher then uses that instead of a core profile. While forcing
GLSL to 4.30 only enables 4.3 in the core profile.

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

[-- Attachment #1.2: Type: text/html, Size: 2977 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

      parent reply	other threads:[~2016-05-05 18:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05 14:36 [Bug 95285] [radeonsi] Tomb Raider: enabling TressFX makes hair disappear bugzilla-daemon
2016-05-05 14:39 ` 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 [this message]

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-O4vekoard1@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