Nouveau - Jun 2016 - [Bug 96391] New: Payday: The Heist has rendering issues when anti-aliasing enabled

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

            Bug ID: 96391
           Summary: Payday: The Heist has rendering issues when
                    anti-aliasing enabled
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: gyebro69 at gmail.com
        QA Contact: nouveau at lists.freedesktop.org

Created attachment 124335
  --> https://bugs.freedesktop.org/attachment.cgi?id=124335&action=edit
screenshot, comparison (nouveau vs. nvidia, AA enabled)

When I launch Payday: The Heist in Wine, everything looks fine in the menus.
The problem arises when I start a mission: the loading screen becomes way too
dark so hardly anything can be seen. When the actual mission is loaded the
screen looks as if it was rendered with some special effect applied. 
I'm attaching a screenshot here to demonstrate what the game looks like with
nouveau and nvidia 340.xx

If I disable in-game anti-aliasing then the game renders properly, except for
the loading screen which still remains so dark (maybe the game always uses AA
on the loading screen, or it is a different issue).

If I start the game with the software renderer (LIBGL_ALWAYS_SOFTWARE=1) then
both the loading screen and the actual game are rendered properly.

Trace created with apitrace (uncompressed 185M):
https://drive.google.com/open?id=0B-tTbLKBl-tOOG9fNklaYzZUekE

Fedora 23 32-bit
Linux kernel: 4.6
Libdrm 2.4.68
OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NV92
OpenGL core profile version string: 3.3 (Core Profile) Mesa 12.1.0-devel
(git-fd6bbc2)
OpenGL core profile shading language version string: 3.30

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160605/8535366d/attachment-0001.html>

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

--- Comment #1 from Ilia Mirkin <imirkin at alum.mit.edu> ---
Reproduces on GT215 but not GK208. Kinda looks like one of those control flow
fail situations, or potentially one of the "loop stopped running"
situations
that I never figured out. NV50_PROG_OPTIMIZE=0 had no effect, which it usually
would in those situations (not to fix it, but just to alter how things look).
Interesting.

I *am* aware of an issue in using glReadPixels()/glDrawPixels() with a MSAA
winsys framebuffer, but ... let's hope they don't do that. And those
issues
would be the same on the GK208.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160605/56697245/attachment.html>

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

--- Comment #2 from Ilia Mirkin <imirkin at alum.mit.edu> ---
Some draw calls that show differences (retracediff.py is *awesome*).

118175
118182
134311
134322
138829

I looked at the shader ... doesn't do anything fancy. Very odd. I suspect
some
sort of resource management failure =/

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160605/32fac2e2/attachment.html>

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

--- Comment #3 from Ilia Mirkin <imirkin at alum.mit.edu> ---
OTOH every time we use program 90, there's a failure. Coincidence?

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160605/9c6357d8/attachment.html>

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

GitLab Migration User <gitlab-migration at fdo.invalid> changed:

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

--- Comment #4 from GitLab Migration User <gitlab-migration at
fdo.invalid> ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1105.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190918/0222d758/attachment.html>