From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102962] GPU crash running Overwatch in wine-staging
Date: Mon, 10 Sep 2018 03:36:19 +0000 [thread overview]
Message-ID: <bug-102962-502-h8342V9Jm9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102962-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1857 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102962
--- Comment #15 from Tobias Auerochs <tobi291019@gmail.com> ---
(In reply to Timothy Arceri from comment #13)
> (In reply to Tobias Auerochs from comment #12)
> > (In reply to Timothy Arceri from comment #11)
> > > (In reply to gloriouseggroll from comment #9)
> > > > Created attachment 138466 [details]
> > > > broken colors with mesa override
> > > >
> > > > This was originally able to be resolved using
> > > > MESA_GL_VERSION_OVERRIDE=4.0COMPAT, however commit
> > > > 72de747c6a6cdd0be84a24932a4452f453861dbe broke that functionality, so that
> > > > MESA-GL_VERSION_OVERRIDE no longer renders properly, at least on my system.
> > > > See attached.
> > >
> > > radeonsi now has compat 4.4 enabled by default (in git and upcoming 18.2
> > > release). Does the game now work for you with a recent Mesa from git?
> >
> > Tried launching the game with mesa-git 103535.88e56804a7 (unofficial Arch
> > repo), rendering in menus (including backgrounds) worked correctly, however
> > the system still hangs the same way as before (e.g. when selecting Symmetra).
>
> Picked the game up as part of Humble bundle, I seem to be able to select
> Symmetra without any freeze. Is this still happening for you?
Tested using mesa 18.2.0 (Arch testing repository) without any mesa overrides
and still froze (on second attempt selection worked, but right click shot still
froze).
Specifically I was also using wine-staging 3.15, llvm 6.0.1 and a customized
linux 4.18.3 kernel, maybe newer llvm yields better results (have not gotten
around to testing that).
Interestingly I am able to run the game perfectly stable when dxvk is installed
(and radv), aside from the expected poor-ish performance.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3237 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-09-10 3:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 15:05 [Bug 102962] GPU crash running Overwatch in wine-staging bugzilla-daemon
2017-09-24 22:11 ` bugzilla-daemon
2017-09-24 22:51 ` bugzilla-daemon
2017-10-21 4:40 ` bugzilla-daemon
2017-11-26 17:20 ` bugzilla-daemon
2017-11-27 12:33 ` bugzilla-daemon
2017-11-27 12:35 ` bugzilla-daemon
2017-12-06 21:49 ` bugzilla-daemon
2017-12-06 22:17 ` bugzilla-daemon
2018-03-31 17:36 ` bugzilla-daemon
2018-06-22 17:20 ` bugzilla-daemon
2018-07-18 7:18 ` bugzilla-daemon
2018-07-18 18:02 ` bugzilla-daemon
2018-09-08 10:03 ` bugzilla-daemon
2018-09-09 22:58 ` bugzilla-daemon
2018-09-10 3:36 ` bugzilla-daemon [this message]
2018-09-19 22:08 ` bugzilla-daemon
2019-09-25 18:00 ` 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-102962-502-h8342V9Jm9@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