From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105282] Divinity: Original Sin Enhanced Edition blocky and jagged shadows.
Date: Mon, 05 Aug 2019 05:36:34 +0000 [thread overview]
Message-ID: <bug-105282-502-GBsbWxFToz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105282-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 964 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105282
Timothy Arceri <t_arceri@yahoo.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #3 from Timothy Arceri <t_arceri@yahoo.com.au> ---
Should be fixed by:
commit 3c9144f9e5888e9a31886b64168f63e991da01d0
Author: Timothy Arceri <tarceri@itsqueeze.com>
Date: Fri Aug 2 10:05:20 2019 +1000
drirc: Add discard workaround for Divinity: Original Sin EE
This adds an additional work around for the game to fix the blocky
shadows as reported in bug 105282
Acked-by: Eric Engestrom <eric.engestrom@intel.com>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105282
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3038 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
prev parent reply other threads:[~2019-08-05 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 23:55 [Bug 105282] Divinity: Original Sin Enhanced Edition blocky and jagged shadows bugzilla-daemon
2018-02-27 23:56 ` bugzilla-daemon
2018-02-27 23:57 ` bugzilla-daemon
2019-08-05 5:36 ` bugzilla-daemon [this message]
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-105282-502-GBsbWxFToz@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).