Summary: | Blood Effects corrupt graphics in Total War: Warhammer | ||
---|---|---|---|
Product: | Mesa | Reporter: | siyia <eutychios23> |
Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED INVALID | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | normal | ||
Priority: | medium | ||
Version: | 17.0 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 77449 | ||
Attachments: |
blood bug
Blood Bug Marked it is here!!! blood effects options in menu no blood effects option (v 1.5) apitrace of TW warhammer attachment-1184-0.html attachment-13435-0.html attachment-14347-0.html |
Description
siyia
2016-12-18 05:19:38 UTC
Created attachment 128596 [details]
blood bug
this bug also persists with current mesa 13.1-git.
The issue doesn't seem obvious to me. Can you explain? Or take a new screenshot? Thanks! lol can't you see red and green blocks of color within the units that are getting attacked in my screenshot when i have blood effects enabled?i cannot post a new screenshot because i ll have to reinstall the game now. look at my selected units in the screenshot it's obvious ok wait mayby i ll edit the screenshot to pinpoint the problem Created attachment 129074 [details]
Blood Bug Marked
i marked the graphical corruption in red color shaped circles.
Okay, it's obvious now, thanks! Can't be reproduced with latest Mesa/LLVM git after few minutes of test with different graphics parameters. Could be similar to https://bugs.freedesktop.org/show_bug.cgi?id=98743 (which has been fixed between LLVM 3.9 and LLVM 4.0). Please re-open if you still have the issue with next Mesa/LLVM. did u enable blood effects in options and the bug didn't happen?the mesa 13.1-git had llvm 4.0 when i tried it but it was on december 20 maybe it is fixed we'll see. Created attachment 129261 [details]
it is here!!!
blood bug persists with latest mesa 17.1.0-git and llvm 5.0 on amd oland gpu
Which version of Total War: Warhammer? 1.40 u think it's version related? steps to reproduce 1)tick blood effects in graphics options 2)create custom battle 3)engage the enemy My version 1.5, can you try upgrading? I don't see that "blood effects" options. Last time I tried to reproduce the issue, I used many different graphics options without success. lol start the game ---->in the game menu choose options ----->graphics------>advanced----->then tick the blood effects and press accept changes. Finally try and play a custom battle. when you open the graphics menu on the right side it has some options that can be ticked for example vsync,blood effects is one of them. Created attachment 129352 [details]
blood effects options in menu
posted a screenshot of the graphics options with blood effect just tick it in ur game and test it Created attachment 129356 [details]
no blood effects option (v 1.5)
(In reply to Samuel Pitoiset from comment #19) > Created attachment 129356 [details] > no blood effects option (v 1.5) Maybe you need the Blood DLC? (just wild guess) http://store.steampowered.com/app/404011/ (In reply to Gregor Münch from comment #20) > (In reply to Samuel Pitoiset from comment #19) > > Created attachment 129356 [details] > > no blood effects option (v 1.5) > > Maybe you need the Blood DLC? (just wild guess) > http://store.steampowered.com/app/404011/ If you have the blood dlc,can you reproduce the bug Gregor Münch? (In reply to siyia from comment #21) > > If you have the blood dlc,can you reproduce the bug Gregor Münch? I dont have the game at all. I assume you have to have this DLC to actually see this checkbox. The question is, do you have this DLC? If so, Samuel needs to have it too when he wants to reproduce. yes i do lol sorry for not checking that I do have the blood dlc now. Unfortunately, after trying few minutes I can't reproduce the issue with latest mesa/LLVM. Maybe it's on my side but I don't really have much time to investigate into that issue. Sorry. However, if you can record an apitrace which reproduces the issue, that would be awesome and really easier for us. https://github.com/apitrace/apitrace Thanks in advancce. This is what it spams when the bug happens apitrace: warning: glNamedBufferStorage: MAP_NOTIFY_EXPLICIT_BIT_VMWX set w/o MAP_PERSISTENT_BIT Can you upload the trace somewhere? (In reply to Samuel Pitoiset from comment #26) > Can you upload the trace somewhere? will try Created attachment 129669 [details]
apitrace of TW warhammer
bug happens also with latest mesa stable independently of llvm version.
Comment on attachment 129669 [details]
apitrace of TW warhammer
That's just the apitrace terminal output. "The trace" refers to the "/home/siyia/Native/Total War WARHAMMER/bin/TotalWarhammer.2.trace" file generated by it. Note that it's likely too large to be attached here directly.
lol thatgs 10 GB!!! ok not 10 but around 3GB xz -9 <filename> should help. ok but do you have a fileserver where i can upload it? You can use this link: https://www.dropbox.com/request/mk4YGOBOp4oqX0TKciu7 When you're done uploading the trace I'll post the link to the trace in this bug report. Thanks! Created attachment 129904 [details] attachment-1184-0.html ipload fails at 51% the file is 2.3gb is there an upload limit? On 02/24/2017 12:32 AM, bugzilla-daemon@freedesktop.org wrote: > > *Comment # 34 <https://bugs.freedesktop.org/show_bug.cgi?id=99136#c34> > on bug 99136 <https://bugs.freedesktop.org/show_bug.cgi?id=99136> from > Pierre-Loup A. Griffais <mailto:pgriffais@valvesoftware.com> * > You can use this link: > > https://www.dropbox.com/request/mk4YGOBOp4oqX0TKciu7 > > When you're done uploading the trace I'll post the link to the trace in this > bug report. Thanks! > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. > need bigger upload limit than 2gb compressed file is 2.3gb. Not sure but this might help for your issue. https://cgit.freedesktop.org/mesa/mesa/commit/?id=7751ed39e40e08e5aa0633d018c9f25ad17f9bb0 Let me know if you get a chance to try. Created attachment 130321 [details] attachment-13435-0.html ok i see your patch is included in mesa 17.0.2, when mesa 17.02 lands on my distro i will check if the issue is resolved. On 03/15/2017 03:56 PM, bugzilla-daemon@freedesktop.org wrote: > > *Comment # 37 <https://bugs.freedesktop.org/show_bug.cgi?id=99136#c37> > on bug 99136 <https://bugs.freedesktop.org/show_bug.cgi?id=99136> from > Samuel Pitoiset <mailto:samuel.pitoiset@gmail.com> * > Not sure but this might help for your issue. > > https://cgit.freedesktop.org/mesa/mesa/commit/?id=7751ed39e40e08e5aa0633d018c9f25ad17f9bb0 > > Let me know if you get a chance to try. > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. > Created attachment 130708 [details] attachment-14347-0.html problem persists with mesa 17.02 and llvm 3.9.1 On 15/03/2017 03:56 μμ, bugzilla-daemon@freedesktop.org wrote: > > *Comment # 37 <https://bugs.freedesktop.org/show_bug.cgi?id=99136#c37> > on bug 99136 <https://bugs.freedesktop.org/show_bug.cgi?id=99136> from > Samuel Pitoiset <mailto:samuel.pitoiset@gmail.com> * > Not sure but this might help for your issue. > > https://cgit.freedesktop.org/mesa/mesa/commit/?id=7751ed39e40e08e5aa0633d018c9f25ad17f9bb0 > > Let me know if you get a chance to try. > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. > I cant reproduce with Blood DLC on my Radeon HD 7970. Still an issue? Maybe its specific a problem with Oland chips. its not mesa bug its known bug in cracked release by razor1911 (In reply to Alexandr Zelinsky from comment #41) > its not mesa bug > its known bug in cracked release by razor1911 Closing without a fix because we refuse to support cracked games. Feel free to re-open the bug if you encounter this issue on a legal version of the game. Thanks. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.