From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108194] Civilization VI - Animated leader characters small black squares artifacts
Date: Thu, 01 Nov 2018 11:54:25 +0000 [thread overview]
Message-ID: <bug-108194-502-g8eVbB2Etu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108194-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1788 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108194
--- Comment #4 from Hadrien Nilsson <freedesktop@psydk.org> ---
I'm not sure for bug 104602 as everything else renders correctly.
---------------
I installed a fresh version of Ubuntu 18.04 on a specific disk and added padoka
unstable ppa for mesa. I got this version:
1:18.3~git181021202700.2d235d6~b~padoka0
And the bug is still present. I also installed Ubuntu 18.10 (kernel 4.18), used
the stock mesa (18.2.2), and the bug was there too.
---------------
I have two concerns about apitrace:
1. the apitrace file will be full of copyrighted assets. Isn't there a legal
risk to share such a file on the Internet?
2. Civilization is a huge game and I'm afraid the apitrace file will be huge
too (I need to reach the Leader screen before stopping the recording). What is
the best way to share huge apitrace files with Mesa developers?
---------------
Maybe I could also enable some kind of error logging, or a dump of compiled
shaders? By the way, the rendering level for Leaders is set to "low".
I'm back on my daily installation, with Mesa 18.2.3. In case in can help, here
are my LLVM versions:
ii libllvm6.0:amd64 1:6.0-1ubuntu2 amd64 Modular
compiler and toolchain technologies, runtime library
ii libllvm6.0:i386 1:6.0-1ubuntu2 i386 Modular
compiler and toolchain technologies, runtime library
ii libllvm7:amd64 1:7-2~oibaf~b amd64 Modular
compiler and toolchain technologies, runtime library
ii libllvm7:i386 1:7-2~oibaf~b i386 Modular
compiler and toolchain technologies, runtime library
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2833 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:[~2018-11-01 11:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 5:33 [Bug 108194] Civilization VI - Animated leader characters small black squares artifacts bugzilla-daemon
2018-10-13 21:48 ` bugzilla-daemon
2018-11-01 0:48 ` bugzilla-daemon
2018-11-01 6:48 ` bugzilla-daemon
2018-11-01 11:54 ` bugzilla-daemon [this message]
2019-02-12 12:18 ` bugzilla-daemon
2019-02-12 12:23 ` bugzilla-daemon
2019-02-12 16:26 ` bugzilla-daemon
2019-02-12 18:19 ` bugzilla-daemon
2019-08-27 23:57 ` bugzilla-daemon
2019-09-25 18:09 ` 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-108194-502-g8eVbB2Etu@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