All of lore.kernel.org
 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: Tue, 07 May 2019 08:37:32 +0000	[thread overview]
Message-ID: <bug-108893-502-Utg8AKpMGH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108893-502@http.bugs.freedesktop.org/>


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

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

--- Comment #20 from supercoolemail@seznam.cz ---
(In reply to Timothy Arceri from comment #19)
> I installed the game via Proton. Seems it is still very buggy in wine. I had
> to follow the instructions here [1] to get it to load without crashing or
> constantly changing the screen between windowed and fullscreen. Once I got
> it working the menu was working fine, no lag.
SystemPack for Gothic fixes everything except crash with music enabled, for
which native dmusic helps.
> I'm suspecting you are either experiencing a wine bug or you have some bad
> settings somewhere rather than a Mesa bug.
But how does LIBGL_ALWAYS_SOFTWARE=1 (with llvmpipe) help with laggy menu and
why it sometimes give more FPS than radeonsi?

I don't have any relevant environment variables set, and only X configuration I
have is

Section "Device"
        Identifier "AMDgpu"
        Driver "amdgpu"
        Option "VariableRefresh" "true"
EndSection

but laggy menu was there before VRR support arrived.

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

[-- Attachment #1.2: Type: text/html, Size: 2096 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-05-07  8:37 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
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 [this message]
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-Utg8AKpMGH@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.