dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108893] Slow redrawing of menu in Gothic 2 under wine
Date: Sat, 27 Apr 2019 09:20:59 +0000	[thread overview]
Message-ID: <bug-108893-502-0RVPoe1vPU@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108893-502@http.bugs.freedesktop.org/>


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

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

supercoolemail@seznam.cz changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|18.3                        |19.0
         Resolution|INVALID                     |---
             Status|RESOLVED                    |REOPENED

--- Comment #4 from supercoolemail@seznam.cz ---
Sigh, this is actually real problem. Maybe now it's different problem but
behavior is exactly the same. 
With LIBGL_ALWAYS_SOFTWARE=1 redrawing is instant, otherwise moving to
different items of same menu takes 5-6 seconds and going to different menu
takes even longer.

Might be related: performance in game is very bad. I get 3-4 FPS with
LIBGL_ALWAYS_SOFTWARE=1 in one place and only 8 FPS without. However, when I
pin game to single core, then I get 1 FPS without LIBGL_ALWAYS_SOFTWARE=1 but
it won't even past loadscreen with it.
This is not only game that suffers from low FPS due to "fake" CPU bottleneck.
The other is Sacred, which also happens to use Direct3D/DDraw, runs better with
LIBGL_ALWAYS_SOFTWARE=1 than without. Without it, I get around 5 FPS in one
city and 100 % one core usage, with it it is at least playable (Gallium HUD
does not work with LIBGL_ALWAYS_SOFTWARE=1, so I don't know numbers).

Hardware: Ryzen 7 1700, RX 580

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

[-- Attachment #1.2: Type: text/html, Size: 3038 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

  parent reply	other threads:[~2019-04-27  9:20 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 [this message]
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
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-0RVPoe1vPU@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).