Yuzu: Crash while loading shader cache for Pokemon Let's Go Eevee

Created on 13 Jul 2019  路  6Comments  路  Source: yuzu-emu/yuzu

  • Canary 2474

Loading the disk shader cache can still crash yuzu at a specific shader. I got this one by going through the Elite 4 and using all of my team's moves.

yuzu_log.txt
savedata.zip

bug gpu-issue

Most helpful comment

@sakshatshinde That's another thing separate from this issue and works as intended. You were trying to use an outdated cache that got incompatible after the new texture cache got implemented.

All 6 comments

I have the same issue. When I add the shader cache yuzu just crashes and deletes the file from the transferable folder. It runs fine on the next boot when it creates it's own new shader cache file.

@sakshatshinde That's another thing separate from this issue and works as intended. You were trying to use an outdated cache that got incompatible after the new texture cache got implemented.

@Kewlan thanks for the info!

@Kewlan, do you know of a shader cache that鈥檚 not outdated? I鈥檓 able to run let鈥檚 go eevee at 30fps but without the shader cache it鈥檚 around 20 with stuttering in the more intense areas.

I still crash at launch on specific shaders in Canary 2602. I built the cache myself in Canary 2602 and I haven't updated or used other versions. Interestingly, I can sometimes get past shader 630, but not past 1319-not that the numbers mean anything other than to indicate an interesting issue.

Also interesting is the fact that the first time this "getting stuck" happened, I deleted the file in the precompiled folder and relaunched about 5 times, and I eventually loaded with shaders. The second time, I copied the shader file from the transferable folder into the precompiled folder and relaunched about 10 times and it finally loaded with shaders.

Because the start of this issue would be while playing the game, but not noticed until you load the shader cache when restarting the game it was hard to test. But it seems now that no one has had it happen for a while, including myself, so it's likely it has been fixed.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ShalokShalom picture ShalokShalom  路  6Comments

P
bukyapavankumar picture bukyapavankumar  路  4Comments

CptFoda-se picture CptFoda-se  路  3Comments

AuracleTech picture AuracleTech  路  3Comments

Rayz320 picture Rayz320  路  4Comments