All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 74062] New: Artifacts in 3D games.
Date: Sun, 26 Jan 2014 01:06:14 +0000	[thread overview]
Message-ID: <bug-74062-8800@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 74062
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: Artifacts in 3D games.
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: mbarrera-KK0ffGbhmjU@public.gmane.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: 10.0
         Component: Drivers/DRI/nouveau
           Product: Mesa

Moving artifacts are present in the rendering of 3D games such as OpenArena or
Minetest/Freeminer, happens in glxgears too. However, there is no issue when I
use compiz. In blender, the artifacts are visible only “inside” 3d elements.

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2014-01-26  1:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26  1:06 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-74062-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-01-26  1:10   ` [Bug 74062] Artifacts in 3D games bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-26  1:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-27  4:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-27 22:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-27 22:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-27 22:44   ` [Bug 74062] [NVE4] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-27 22:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-27 23:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08  2:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-15 15:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-21 16:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-31  2:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-31  3:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-31 18:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-12  7:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-19  1:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-74062-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.