From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100387] War Thunder game has visual errors, missing textures
Date: Sat, 25 Mar 2017 14:20:40 +0000 [thread overview]
Message-ID: <bug-100387-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1861 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100387
Bug ID: 100387
Summary: War Thunder game has visual errors, missing textures
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: acelists@atlas.sk
QA Contact: dri-devel@lists.freedesktop.org
Using the War Thunder game on Slackware, Mesa git custom compiled, LLVM 4.0 and
on a RV710 card (512MB video RAM) always produces visual errors. The errors are
not the same at all runs but vary between these problems, e.g. sky being black,
clouds being any color, water is some color without reflections, trees being
blue.
Plane/ground target models are mostly correct, but sometimes they are also
white.
The errors can be seen right in the hangar, but also when playing the game (in
a mission).
I have set the "Old videocard support" in the graphics options in the game.
This has improved things to the state I describe. The game client shows "ultra
low quality" in the right hand corner. I am using the low-res client (HD
textures not downloaded) and the client often prompts to download hi-res
textures which I decline.
Other than this, the game runs correctly, albeit slow on this GPU (5-15FPS).
In the console where I start the game (updater binary) there is a ton of output
like:
EE r600_shader.c:183 r600_pipe_shader_create - translation from TGSI failed !
EE r600_state_common.c:803 r600_shader_select - Failed to build shader variant
(type=1) -1
The line numbers 183 and 803 are always the same.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3258 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 reply other threads:[~2017-03-25 14:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-25 14:20 bugzilla-daemon [this message]
2017-03-25 17:07 ` [Bug 100387] War Thunder game has visual errors, missing textures bugzilla-daemon
2017-04-04 21:53 ` bugzilla-daemon
2017-05-06 0:52 ` bugzilla-daemon
2017-06-19 21:00 ` bugzilla-daemon
2017-07-16 21:42 ` bugzilla-daemon
2017-07-30 20:55 ` bugzilla-daemon
2017-09-07 4:34 ` bugzilla-daemon
2017-09-07 4:40 ` bugzilla-daemon
2017-09-07 4:45 ` bugzilla-daemon
2017-09-07 21:03 ` bugzilla-daemon
2017-09-08 9:45 ` bugzilla-daemon
2017-09-08 17:32 ` bugzilla-daemon
2017-09-08 18:22 ` bugzilla-daemon
2017-09-08 20:45 ` bugzilla-daemon
2017-09-09 4:03 ` bugzilla-daemon
2017-09-17 16:34 ` bugzilla-daemon
2017-09-17 16:55 ` bugzilla-daemon
2017-11-25 7:43 ` bugzilla-daemon
2017-11-25 8:00 ` bugzilla-daemon
2017-11-27 18:52 ` bugzilla-daemon
2018-02-17 13:14 ` bugzilla-daemon
2018-02-23 6:13 ` bugzilla-daemon
2019-09-18 19:23 ` 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-100387-502@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).