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 107694] [wine] RAGE: texture problems
Date: Mon, 24 Sep 2018 21:16:30 +0000	[thread overview]
Message-ID: <bug-107694-502-8JRt2fumww@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107694-502@http.bugs.freedesktop.org/>


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

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

--- Comment #8 from James B <lejimster@gmail.com> ---
All tests performed with same settings.

- Rage 32-bit on Windows 10: Works perfect out of the box no performance
issues, no issue with the virtual textures, no texture pop-in bug. I noticed
the player shadow wasn't rendered correctly, but everything else is fine.
Rage.exe RAM usage ~1,370MB on the Wasteland map.

- Rage 32-bit on Ubuntu w/ 18.20 Pro drivers: I experience good performance out
of the box but the virtual textures bug is present although very minor.  Can be
totally cured by setting "jobs_numThreads 1", texture pop in bug still
persists.
Rage.exe RAM usage ~780MB on the Wasteland map.  

- Rage 32-bit on Arch w/ latest mesa-git:  Massive issue with virtual textures
unless you set "jobs_numThreads 1" which reduces but doesn't fix the issue,
frame rate dips to 30-40fps in certain areas of the wasteland and the "texture
pop" is there regardless even if you enabled the texture cache, set the maxPPF
etc.
Rage.exe RAM usage ~730MB on the Wasteland map.

http://renderingpipeline.com/2012/03/megatextures-in-rage/

Adding "+com_allowconsole 1" to the launch options using "toggle
vt_showPageNumbers; vt_restart" you can see the wrong mipmap level and texture
numbers are being loaded for some of the tiles.

I'm wondering if somebody at AMD would have access to the changelogs for the
proprietary drivers back when the Rage patches were first introduced, it would
atleast point you in the right direction.

Heres a video I made comparing 32/64-bit versions on my system:
https://www.youtube.com/watch?v=EUwq4dbnFkA

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

[-- Attachment #1.2: Type: text/html, Size: 2694 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:[~2018-09-24 21:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-26 18:58 [Bug 107694] [wine] RAGE: texture problems bugzilla-daemon
2018-08-31  1:24 ` 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 [this message]
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-8JRt2fumww@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