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 94705] [radeonsi] blue ground in Company of Heroes 2
Date: Tue, 05 Apr 2016 20:35:12 +0000	[thread overview]
Message-ID: <bug-94705-502-pOcd1XIP5R@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94705-502@http.bugs.freedesktop.org/>


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

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

Nicolai Hähnle <nhaehnle@gmail.com> changed:

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

--- Comment #1 from Nicolai Hähnle <nhaehnle@gmail.com> ---
Hi Laurent, thanks for the report. I did some digging into the apitrace you
provided.

Long story short: The game does not properly deal with the
implementation-defined limit on the number of samplers that are available in a
fragment shader. Perhaps there is some graphics quality setting that can be
reduced to convince the game to use only shaders with fewer samplers as a
workaround.

The long story: In the provided apitrace, the artefacts first appear in
textures 10884 and 10885, which are terrain colour and normal maps. They are
rendered to around call @516614, which is a glLinkProgram call for program 658
that fails because the attached fragment shader 611 has not been compiled. It
is evident from the trace leading up to @516933 that the game intends to do
rendering using 658 precisely when the artefacts appear, because there are a
bunch of (failing) calls to query uniform locations.

Why has shader 611 not been compiled? Well, most likely there is logic in the
game that does check for implementation-defined sampler limits, because shader
611 uses 18 samplers and we only expose 16. So probably some part of the game
engine notices the limitation and doesn't even try to compile the shader, but
this problem is not propagated up to higher layers in the engine.

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

[-- Attachment #1.2: Type: text/html, Size: 3236 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-04-05 20:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-25 17:25 [Bug 94705] [radeonsi] blue ground in Company of Heroes 2 bugzilla-daemon
2016-03-25 17:28 ` bugzilla-daemon
2016-04-05 20:35 ` bugzilla-daemon [this message]
2016-04-05 20:56 ` bugzilla-daemon
2016-04-05 20:59 ` bugzilla-daemon
2016-04-05 23:08 ` bugzilla-daemon
2016-04-06  7:06 ` bugzilla-daemon
2016-04-06  7:12 ` bugzilla-daemon
2016-04-07 18:18 ` bugzilla-daemon
2016-04-07 18:19 ` bugzilla-daemon
2016-04-08  9: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-94705-502-pOcd1XIP5R@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