World of Warcraft - choppy in lutris 0.5.17 about lutris HOT 6 OPEN

This seems quite strange. Perhaps you could give us a debug log? To do so, run Lutris from the terminal:

lutris -d

And run the game, then give us the terminal spam that results. Might be a clue in there!

from lutris.

This seems quite strange

At this point, given the number of reports about game choppyness and overall system slowdows, it stops being strange and starts being a pattern.

@Proxido could you try disabling your iGPU in your BIOS and give it another shot?
I'm having similar issues with the Avatar game (Lutris) and The Last of Us (Steam) but they go away when my iGPU is disabled.

from lutris.

Also, since the game works in Steam, try running the game with umu (you just need to pick Proton GE in the Wine version)

from lutris.

This seems quite strange

At this point, given the number of reports about game choppyness and overall system slowdows, it stops being strange and starts being a pattern.

@Proxido could you try disabling your iGPU in your BIOS and give it another shot? I'm having similar issues with the Avatar game (Lutris) and The Last of Us (Steam) but they go away when my iGPU is disabled.

smooth_lutris_516.txt
choppy_lutris_517.txt

Please find attached output from lutris -d , the choppy run I had to cancel because the game was hanging on a loading screen.

However, I have disabled the igpu and the problem is gone :) It seems 5.17 was picking my igpu instead of main gpu although I'm 100% that I chose correct GPU under system options -> Display. I suspected it could have been a problem but I forgot about bios.

from lutris.

I've discovered that on gentoo linux it seems that 0.5.17 does not properly make use of my dedicated GPU and want to render world of warcraft with the integrated GPU, rolling it back to 0.5.16 shows I do not have this issue

from lutris.

I've found an issue with Lutris and broken Vulkan installs- where you have Vulkan installed but it can't work with your GPUs (because of, say, a bad driver). Lutris needs to fall back to lspci for these cases, and I've added code to do that.

@Proxido isn't have this problem, but perhaps your are @10leej. But you could download the master, run the bin/lutris script within, and see if that does anything for you.

from lutris.