From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107694] [wine] RAGE: texture problems
Date: Sun, 26 Aug 2018 18:58:22 +0000 [thread overview]
Message-ID: <bug-107694-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1912 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107694
Bug ID: 107694
Summary: [wine] RAGE: texture problems
Product: Mesa
Version: 18.2
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: sa@whiz.se
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 141292
--> https://bugs.freedesktop.org/attachment.cgi?id=141292&action=edit
screenshot of bug in RAGE
The game RAGE starts and runs, but have some quite severe texture problems. See
attached screenshot. The problem is especially bad when loading new areas.
Settings these options in default.cfg minimizes but doesn't get rid of the bug
fully:
jobs_numThreads 1
vt_maxPPF 128
as suggested in https://store.steampowered.com/news/6464/
This bug looks quite a lot like one that plagued the Windows drivers (ATI
Performance) back when the game was released:
https://www.youtube.com/watch?v=z-yl6pDFgtw
I have seen video of RAGE rendering fine with radeonsi
(https://www.youtube.com/watch?v=OgqgNrN16KM) so I tried jumping back quite a
few Mesa releases* to see if there was a regression somewhere, but AFAICT it is
still there as far back as 11.2.2.
I'm guessing the bug happened as a change from radeon to amdgpu on the kernel
side?
* Using a hack for Wine to skip the check for a compat profile.
System environment:
-- system architecture: 64-bit
-- Linux distribution: Debian unstable
-- GPU: TONGA
-- Model: Asus Strix R9 285 2GB
-- Display connector: DVI
-- xf86-video-amdgpu: 18.0.1
-- xserver: 1.20.1
-- mesa: 18.2.0~rc4
-- drm: 2.4.93
-- kernel: 4.17
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3580 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 reply other threads:[~2018-08-26 18:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 18:58 bugzilla-daemon [this message]
2018-08-31 1:24 ` [Bug 107694] [wine] RAGE: texture problems bugzilla-daemon
2018-08-31 13:42 ` bugzilla-daemon
2018-08-31 15:23 ` bugzilla-daemon
2018-09-20 1:01 ` bugzilla-daemon
2018-09-20 8:40 ` bugzilla-daemon
2018-09-20 10:31 ` bugzilla-daemon
2018-09-20 10:49 ` bugzilla-daemon
2018-09-24 21:16 ` bugzilla-daemon
2019-01-06 13:50 ` bugzilla-daemon
2019-01-06 13:54 ` bugzilla-daemon
2019-07-15 12:32 ` bugzilla-daemon
2019-09-25 18:09 ` 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-107694-502@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;
as well as URLs for NNTP newsgroup(s).