From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 49295] New: artifacts in prboom on NV86
Date: Mon, 30 Apr 2012 08:27:48 +0000 [thread overview]
Message-ID: <bug-49295-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=49295
Bug #: 49295
Summary: artifacts in prboom on NV86
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: svenjoac-Mmb7MZpHnFY@public.gmane.org
Created attachment 60784
--> https://bugs.freedesktop.org/attachment.cgi?id=60784
Doom 1, Episode 1, Map 4 under prboom 2.5.0
Under prboom 2.5.0 with OpenGL renderer, I'm seeing bad artifacts:
- Walls are very bright, sometimes transparent. In some cases,
the texture disappears completely and is replaced by a solid color.
- A "hall of mirrors effect" as described in
http://doomwiki.org/wiki/Hall_of_mirrors_effect.
I'm attaching a screenshot from Doom 1, Episode 1, Map 4 shortly after the
start.
There are no error messages in the kernel logs, and other 3D games (including
doomsday, another Doom source port) are unaffected.
Hardware is a GeForce 8500 GT, software stack as follows:
Mesa from git commit 4c15a77f27
Kernel 3.4.0-rc5
Libdrm from git commit 754655c795
Nouveau DDX from git commit 174f170720
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-04-30 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 8:27 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-49295-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-08-25 17:39 ` [Bug 49295] [NV50 gallium] artifacts in prboom on NV86 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 18:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 18:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 19:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 8:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:38 ` 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-49295-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox