From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102709] War Thunder crashes after logging in to the game. (GL_INVALID_ENUM)
Date: Sat, 12 May 2018 16:02:38 +0000 [thread overview]
Message-ID: <bug-102709-502-25bWCNIR4H@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102709-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 664 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102709
--- Comment #2 from Vitalii <shpalikvitalik@gmail.com> ---
(In reply to Samuel Pitoiset from comment #1)
> Well, War Thunder doesn't check that GL_EXT_texture_compression_s3tc is
> exposed before using those compressed formats.
>
> Though, if you have libtxc_dxtn installed on your system the extension
> should be enabled, can you check?
I have the same problem with war thunder, but my driver crashes and only hard
reboots help. I can not find the logs and I do not know how to inspect it.
driver r600 padeon HD7600
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1566 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-05-12 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 18:11 [Bug 102709] War Thunder crashes after logging in to the game. (GL_INVALID_ENUM) bugzilla-daemon
2017-09-14 16:04 ` bugzilla-daemon
2018-05-12 16:02 ` bugzilla-daemon [this message]
2018-05-12 16:05 ` bugzilla-daemon
2019-09-18 19:24 ` 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-102709-502-25bWCNIR4H@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