yuzu icon indicating copy to clipboard operation
yuzu copied to clipboard

Diablo III: Eternal Collection [mainline 986] working perfect vs [early access 2947] fps slutter

Open humanana opened this issue 1 year ago • 10 comments

win 10 x64 21h2 i5 6500 1060 6gb ram32gb gpu driver 512.96

Diablo III: Eternal Collection 2.7.4 [mainline 986] working perfect vs [early access 2947] fps slutter

default config using valkun + opengl both slutter on early2947 but not the old mainline986

with the same config from mainline 986 but early 2947 start the game then you will notice fps slutter which mainline 986 did not slutter at all

could re produce 100% when switching and testing comparing between both build try to get early to test the multiplayer but find out that could not even play the game dont know what is the cause but

mainline 986 same config working perfectly just dont have multiplayer to test TTwTT

could dev look into this issuem thanks TTwTT if you prefer the vdo for comparing I'll try to record it for you to fix it TvT

humanana avatar Sep 13 '22 15:09 humanana

https://yuzu-emu.org/help/reference/log-files/ Provide logs when you can please.

G-Spawn avatar Sep 13 '22 16:09 G-Spawn

Hi @humanana There are a lot of changes between EA2947 and mainline 986.

Latest mainline is 1163, it would be nice if you could provide some feedback on latest mainline vs EA.

So devs can narrow down the issue.

As G-Spawn pointed, pls provide a log for further debug.

Thanks

pacoa-kdbg avatar Sep 13 '22 16:09 pacoa-kdbg

here are the logs

early 2947 yuzu_log.txt mainline 986 yuzu_log.txt mainline 1164 yuzu_log.txt

I test 1164 just recently compile for you also it slutter same as early 2947

I onced update to early mainline 1000 + - something not sure and need to roll back to 986 it start to unplayable from there

here are the vdo

mainline 986 [ might notice a bit slutter in the begining, I remove all shader cache and perhaps it's compiling? not sure > <'] I test mainline 986 many hours, it's fully playable and find out very long time in such case but rarely happen to make you feel unplayable ] let's say about 98-99 perfectly playable

https://youtu.be/648QN3DzkAM

mainline 1164 https://youtu.be/ZALrg90OZvM

early 2947 https://www.youtube.com/watch?v=b62IoFZ9C3w

hope it helps to track what causing it ? TTwTT

humanana avatar Sep 13 '22 17:09 humanana

ohh one more addition I test with

[ Xenoblade Chronicles: Definitive Edition ] on mainline 986 it's quite take long time like 1-2 hrs or perhaps more and it freeze then yuzu crash

but just test with early 2947 not more than 3 min it freeze and then crash right away could you look into it as well

thanks TTwTT

humanana avatar Sep 13 '22 17:09 humanana

emulation > configure > audio > output engine > sdl2

this fixed it for me all micro stutter is gone now and I gained 7-9fps

EA 2947 btw

however to start the game I have to go into task manager yuzu and put affinity from my 11 cores to only 1 core like 0 in my case, once the booting screen is gone and the game starts you can put all cores back on and it will work fine

funny thing is you only have to do this once after that the game will always boot up fine and you have to redo this only if you upgrade yuzu versions. Maybe its because I use a amd cpu ryzen 5 with a weak single core performance.

Shinrataka avatar Sep 13 '22 19:09 Shinrataka

ohh thank you @Shinrataka I set audio > output engine > sdl2

seem like it fix micro stutter as you said, maybe the auto option not choosing correctly? or something with audio function make that issue happen? > <''

I only test about 30 min I will report more once I have more time to test longer period thanks again

humanana avatar Sep 13 '22 22:09 humanana

Hi all, this is the current testing I have done

For the Diablo 3 stutter issue 1092 : audio -> auto -> no stutter audio -> cubeb -> no stutter audio -> sdl2 ->no stutter 1093: audio -> auto -> stutter audio -> cubeb -> stutter** audio -> sdl2 -> no stutter

For now, sdl2 is recomended for D3 until the root cause is found,

Thanks

pacoa-kdbg avatar Sep 14 '22 01:09 pacoa-kdbg

saw on this issue #8750 as well the issue experience is the same I face > <'

humanana avatar Sep 14 '22 09:09 humanana

played it for 4h yesterday no crash at all with sdl2 :) only problem is that I gotta turn all but 1 cpu core off to make it boot after that it works fine with all cores

Shinrataka avatar Sep 14 '22 17:09 Shinrataka