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 108893] Slow redrawing of menu in Gothic 2 under wine
Date: Fri, 03 May 2019 22:10:48 +0000	[thread overview]
Message-ID: <bug-108893-502-AeTnOgvCyn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108893-502@http.bugs.freedesktop.org/>


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

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

--- Comment #12 from andrew.m.mcmahon@gmail.com ---
(In reply to Michel Dänzer from comment #8)
> The video shows very low frame-rate and GPU load in the menu, but high CPU
> load. Maybe there's a CPU bottleneck which affects the reporter even more
> badly. A CPU profile from sysprof or perf might give a clue.
The heavy CPU usage in that particular video is entirely down to
SimpleScreenRecorder. When I'm running the game and NOT recording the screen at
the same time, CPU usage is around 30-50%:
https://imgur.com/a/AlhVLZp

That doesn't seem abnormal; the Phenom II is ancient plus it's going through
Wine. I also assume that the main menu ~10 fps cap is a quirk of the game but
perhaps I'm wrong?
https://pcgamingwiki.com/wiki/Gothic_II#Low_frame_rate_in_fullscreen_mode

I've compiled Mesa (git-8987152ac1) inside an amd64 & i386 chroot (debootstrap) 
Adding --buildtype=debug into my usual script:
https://pastebin.com/6uP6d7kL

I've done two recordings with sysprof:
- A 1 minute recording starting once the game reaches the main menu
- A 5 minute recording starting the game, running around in the starting area
and then exiting the game

Hopefully those files are of use:
https://drive.google.com/file/d/16s2OfDKIAhbnqrs8gwWicmP7RaJw28L-/view?usp=sharing

Just out of interest there's an unofficial D3D11 renderer plus an unfinished
open source remake - love to see the latter finished:
https://github.com/ataulien/GD3D11
https://github.com/REGoth-project/REGoth

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

[-- Attachment #1.2: Type: text/html, Size: 2885 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-03 22:10 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 [this message]
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-AeTnOgvCyn@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