Hi! With Wine Staging+DXVK some trees trembling instead of smoothly swaying from the wind. This does not happen with WineD3D or Windows. Please, see here for more info: https://github.com/doitsujin/dxvk/issues/450
on the video on the embedded link is visible. same problem. card r290x, the driver of the message 18-18.2 git link https://mega.nz/#!Pr5nmYTQ!uGrPyzSW32-Ln60x2jUxrvtW3VH9rG2b2uTgC1iwe18
(In reply to ximik from comment #1) > on the video on the embedded link is visible. same problem. card r290x, the > driver of the message 18-18.2 git > > > link https://mega.nz/#!Pr5nmYTQ!uGrPyzSW32-Ln60x2jUxrvtW3VH9rG2b2uTgC1iwe18 It's sad, but Mesa developers ignore this bug report.
We are not ignoring, we are just busy with something else. I will have a look as soon as possible, don't worry.
(In reply to Samuel Pitoiset from comment #3) > We are not ignoring, we are just busy with something else. I will have a > look as soon as possible, don't worry. Samuel, thank you!
After installing a stable driver version, this bug is gone. maybe you help too mesa 18.1.3-1 archlinux
Really nice, thanks! Closing.
(In reply to Samuel Pitoiset from comment #6) > Really nice, thanks! Closing. Samuel, I do not agree with your decision to close this bug report. If this bug was not in Mesa 18.1, but it appeared in Mesa-git 18.2, it means that some patch in Mesa-git 18.2 was added, which led to this regression. Therefore, if this regression will not fixed, it will later become part of the Mesa 18.2 stable version. And so I think that it would be better to find the real cause of this regression instead of closing the bug report without fixing this bug. Regards. Thank you.
Yeah sorry, I took the decision too quickly... Can you upload the savegame where you recorded the video please?
(In reply to Samuel Pitoiset from comment #8) > Yeah sorry, I took the decision too quickly... Can you upload the savegame > where you recorded the video please? I already did this before I created this bug report. Please just follow the link, there are all these files.
Definitely not enough of caffeine today. Apparently, the issue is SI-specific which means I can't do anything because I don't have the hardware. It works fine on Polaris/Vega.
(In reply to Samuel Pitoiset from comment #10) > Definitely not enough of caffeine today. Apparently, the issue is > SI-specific which means I can't do anything because I don't have the > hardware. It works fine on Polaris/Vega. But, can I help you in any way? Or are we finally lost any hope?
Bisecting the issue can help.
(In reply to Samuel Pitoiset from comment #12) > Bisecting the issue can help. And what do we need to do for this?
See https://bugs.freedesktop.org/show_bug.cgi?id=107156#c5
I found out that this bug is only apparent when I compiled Mesa-git with llvm-svn installed. But this bug is completely missing when I compiled Mesa-git with installed llvm 6.0.1 (stable version) . And so what do I do? Should I open a bug report on llvm bugzilla?
No, I should be able to have a look in the next few weeks.
(In reply to Samuel Pitoiset from comment #16) > No, I should be able to have a look in the next few weeks. I guess this may not be the issue that is SI-specific which means this is apparently due to the fact that only those people who use Mesa compiled using LLVM 7 have this issue, but this issue is not present in those people who use Mesa compiled using LLVM 6. Do you have any news about some any progress on the way to fix this bug? Thank you.
Are you guys still able to reproduce that problem? I'm trying to reproduce it.
Created attachment 142402 [details] The Witcher 3 savegame file in the location where easy to reproduce this bug.
(In reply to Samuel Pitoiset from comment #18) > Are you guys still able to reproduce that problem? I'm trying to reproduce > it. With commit 16f10230 this bug unfortunately is still present.
What settings are you using?
Created attachment 142404 [details] All minimal settings
I'm having troubles to reproduce the problem on my Pitcairn card. Can you show me the output of R600_DEBUG=info glxgears ?
Created attachment 142405 [details] The output of R600_DEBUG=info glxgears (In reply to Samuel Pitoiset from comment #23) > I'm having troubles to reproduce the problem on my Pitcairn card. Can you > show me the output of R600_DEBUG=info glxgears ?
Well, you don't have the OpenGL driver installed? (ie. radeonsi)
RADV_DEBUG=info vulkaninfo please.
(In reply to Samuel Pitoiset from comment #25) > Well, you don't have the OpenGL driver installed? (ie. radeonsi) I use Mesa-git, Wine Staging+DXVK, so RadeonSI not in use.
(In reply to Samuel Pitoiset from comment #25) > Well, you don't have the OpenGL driver installed? (ie. radeonsi) But I haven't this issue with WineD3D/RadeonSI, only with DXVK/RADV.
Created attachment 142406 [details] RADV_DEBUG=info vulkaninfo (In reply to Samuel Pitoiset from comment #26) > RADV_DEBUG=info vulkaninfo please.
Well, the output doesn't help... It should look like https://hastebin.com/ujuyujobon
Created attachment 142407 [details] R600_DEBUG without the game starting A try #2
You have to run the native version of vulkaninfo, not via wine. "RADV_DEBUG=info vulkaninfo" in a new terminal should just work.
(In reply to Samuel Pitoiset from comment #32) > You have to run the native version of vulkaninfo, not via wine. > > "RADV_DEBUG=info vulkaninfo" in a new terminal should just work. This is exactly what I did this time. The fact was that I had misunderstood in the past times how it should have been done correctly. I believe that now I did everything right this time. See here: https://bugs.freedesktop.org/attachment.cgi?id=142407
Hi! I just tested it again, but this time using Mesa 19.0.3 with LLVM 8.0.0 and now it is fully fixed and works well, just like on Windows. This is similar to the fact that it was a LLVM regression that fixed now in LLVM 8, and not a Mesa bug at all. Thank you very much. GOOD LUCK!
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.