From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109331] Empire Total War - Graphical Corruption
Date: Sun, 13 Jan 2019 13:53:27 +0000 [thread overview]
Message-ID: <bug-109331-502-OA2aQyXHzq@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109331-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 856 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109331
--- Comment #6 from andrew.m.mcmahon@gmail.com ---
One last comment before I leave it to the experts.
Another bug report with Unity 18.04:
https://steamcommunity.com/app/10500/discussions/0/3441214221460524307/
If anyone wants to go above and beyond the call of duty then I've uploaded some
traces for Medieval 2 here:
https://drive.google.com/open?id=17LUb2EsS3oqYjEyZ-yxIB_C_DBnS0Wz8
I've used the same trick of disabling/enabling PBO surfaces.
Finally what exactly are PBO surfaces? Do I need them? What's the penalty for
not using them?
The game seems to trace faster with them off than on.
Are the Linux ports by Feral a bit wonky and/or prone to strange behaviour - or
are they generally decent?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1780 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
next prev parent reply other threads:[~2019-01-13 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 15:04 [Bug 109331] Empire Total War - Graphical Corruption bugzilla-daemon
2019-01-12 15:05 ` bugzilla-daemon
2019-01-13 12:39 ` bugzilla-daemon
2019-01-13 12:40 ` bugzilla-daemon
2019-01-13 12:41 ` bugzilla-daemon
2019-01-13 13:12 ` bugzilla-daemon
2019-01-13 13:53 ` bugzilla-daemon [this message]
2019-01-13 16:35 ` bugzilla-daemon
2019-01-16 20:40 ` bugzilla-daemon
2019-03-06 19:27 ` 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-109331-502-OA2aQyXHzq@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