From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108893] Slow redrawing of menu in Gothic 2 under wine
Date: Fri, 03 May 2019 23:50:25 +0000 [thread overview]
Message-ID: <bug-108893-502-xfNrQmsgrE@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108893-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 977 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108893
--- Comment #13 from supercoolemail@seznam.cz ---
You are lucky. I have this:
https://imgur.com/a/YTDyAXv
Notice, that this is with vastly limited object rendering distance, which makes
fights rather difficult - I can't even see who is shooting at me with a bow.
And there are places like forests that cause massive FPS drops. With higher
object rendering distance I get around 15 FPS, but dropping below that in city
and farms.
Then there is that problem with software rendering giving better performance
than RX 580. That does not seem right to me (and is main reason why I report
this here and not to wine).
And that I have to wait 5 seconds after each menu action to see what is
highlighted or shown. It takes even more time in more complex menus, such as
keybiding. And this is workaroundable by LIBGL_ALWAYS_SOFTWARE=1.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1805 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-03 23:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 8:53 [Bug 108893] Slow redrawing of menu in Gothic 2 under wine bugzilla-daemon
2019-02-04 16:41 ` bugzilla-daemon
2019-02-04 16:41 ` bugzilla-daemon
2019-02-04 16:46 ` bugzilla-daemon
2019-02-04 16:50 ` bugzilla-daemon
2019-02-04 16:51 ` bugzilla-daemon
2019-04-27 9:20 ` bugzilla-daemon
2019-04-27 9:35 ` bugzilla-daemon
2019-04-29 14:04 ` bugzilla-daemon
2019-05-03 4:28 ` bugzilla-daemon
2019-05-03 7:31 ` bugzilla-daemon
2019-05-03 16:17 ` bugzilla-daemon
2019-05-03 16:32 ` bugzilla-daemon
2019-05-03 17:06 ` bugzilla-daemon
2019-05-03 22:10 ` bugzilla-daemon
2019-05-03 23:50 ` bugzilla-daemon [this message]
2019-05-04 11:07 ` bugzilla-daemon
2019-05-05 20:20 ` bugzilla-daemon
2019-05-06 8:47 ` bugzilla-daemon
2019-05-06 10:00 ` bugzilla-daemon
2019-05-06 10:01 ` bugzilla-daemon
2019-05-07 1:35 ` bugzilla-daemon
2019-05-07 8:37 ` bugzilla-daemon
2019-09-25 18:31 ` 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-108893-502-xfNrQmsgrE@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