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 17:07:14 +0000 [thread overview]
Message-ID: <bug-95285-502-WgxAp8izHR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95285-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2531 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95285
Kai <kai@dev.carbon-project.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kenneth@whitecape.org
--- Comment #4 from Kai <kai@dev.carbon-project.org> ---
(In reply to Ilia Mirkin from comment #2)
> Try some of Ken's patches at
>
> https://cgit.freedesktop.org/~kwg/mesa/log/?h=tombraider-2
Thanks for the pointer, Ilia! I've applied the following patches:
fb4f8f9 glsl: Make opt_constant_variable() bail in useless cases.
a6bebce glsl: Remove bonus tree walking in opt_constant_folding().
b01114f glsl: Consolidate duplicate copies of constant folding.
2040a80 glsl: Avoid excess tree walking when folding ir_dereference_arrays.
285e966 glsl: Don't do constant propagation in opt_constant_folding.
862fb32 glsl: Make lower_const_arrays_to_uniforms work directly on constants.
341ee51 glsl: Don't constant propagate arrays
Additionally, I think I should mention, that I've applied
<https://patchwork.freedesktop.org/patch/85101/> locally, since I'm using a
LLVM > 268259. Just in case that could have an impact.
Anyway, with those patches applied the game freezes the system (ie. the system
stops responding to any kind of input) while entering the main menu. The only
output I could capture was "[0505/185411:WARNING:x11_util.cc(1490)] X error
received: serial 1001, error_code 3 (BadWindow (invalid Window parameter)),
request_code 4, minor_code 0 (X_DestroyWindow)"
CCing Kenneth, maybe he has an idea which of his patches could cause this.
> There are some issues which tressfx happens to hit. (And some other option
> too...)
Do you mean bug 95190 or something else? I'm seeing bug 95190 as well.
Therefore I've kept post processing disabled so far.
> However at least on nouveau, tressfx is still a fail even with
> those. [Sorry, don't have the game myself, so don't have further details.
> Just an FYI with the current state of affairs.]
No need to apologize! Any piece of information is appreciated. As far as access
to TR goes: did you try contacting Feral? They were willing to give access to
XCOM 2 to some Mesa developers IIRC, maybe they're willing to do the same here?
(In reply to Nicolai Hähnle from comment #3)
> If the patches mentioned by Ilia don't help, an apitrace showing the problem
> would be useful.
Ok, I'll do that.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4648 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
next prev parent reply other threads:[~2016-05-05 17:07 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 [this message]
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-WgxAp8izHR@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