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 101978] [bisected] war thunder performance reduced by ~28%
Date: Fri, 21 Sep 2018 03:16:18 +0000	[thread overview]
Message-ID: <bug-101978-502-Vy0Nqkl1cn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101978-502@http.bugs.freedesktop.org/>


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

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

--- Comment #11 from higuita@gmx.net ---
As we can't control the installed game version (auto-update to startup), we
can't now test the older opengl4 version anymore, where this problem was found.
Before the upgrade that removed the opengl4, i got higher fps with
power_dpm_force_performance_level setting set to high. That was with kernel
4.16 or 4.17

Warthunder dropped the opengl4 engine (only used in linux) and reverted to the
opengl3 (also used in MacOS) for linux. They did this because they were making
big changed in the engine and supporting the opengl4 only for linux was a waste
of time when they are also adding vulkan support (not yet enabled by default,
but one can enable it changing the config file). This vulkan support is still
not complete (some drivers have rendering bugs, i can see some micro-freezes
sometimes), but the future looks promising.

With opengl3 in the 4.18.9 kernel, at least for me (rx480 and latest mesa),
performance increased about 20% over opengl4 (but again, comparing different
engine versions)
With Vulkan, i get always 60fps (vsync is enabled) and the GPU is using the top
sclk speed, so at least vulkan is working fine.


So i vote to close this "obsolete" or similar, as we can't test it anymore.
Also, probably next version (probably around the end of year) will release the
vulkan support for all OS.

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

[-- Attachment #1.2: Type: text/html, Size: 2278 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-21  3:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31  5:14 [Bug 101978] [bisected] war thunder performance reduced by ~28% bugzilla-daemon
2017-08-01  1:11 ` bugzilla-daemon
2017-08-01  1:20 ` bugzilla-daemon
2017-08-14 19:43 ` bugzilla-daemon
2017-08-15  1:04 ` bugzilla-daemon
2017-09-29  0:30 ` bugzilla-daemon
2017-10-22 17:21 ` bugzilla-daemon
2017-11-14  0:55 ` bugzilla-daemon
2018-01-28 23:16 ` bugzilla-daemon
2018-02-01 21:32 ` bugzilla-daemon
2018-08-13 14:19 ` bugzilla-daemon
2018-09-20  5:05 ` bugzilla-daemon
2018-09-21  3:16 ` bugzilla-daemon [this message]
2018-12-08 21:38 ` bugzilla-daemon
2018-12-10  2:18 ` 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-101978-502-Vy0Nqkl1cn@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).