vasupfruit.blogg.se - Cemu 1.7.5 botw shader cache

Cemu 1.7.5 botw shader cache update#

I was under the impression that all BotW shaders compile fine.Can a shader cause error on another shader? Or they are independent? The error seems to come from inside the cache. when loading my own shader cache with the same graphic packs I get no errors.Any graphic packs active? The compile errors can come from graphic pack shaders as well.You should be able to find the shaders in transferable cache based on the name from log.So when searching the table I should find a shader with that number. Every time I load the cache, I get the errors.

Cemu 1.7.5 botw shader cache update#

And there is always the chance that shader errors go away with a Cemu update.

Then you'd get stutter for shaders with compile errors.

Anyway, shouldn't the shaders with errors be in the cache?

ok, I will give up this remove error idea.

Same shader will always cause a compile error.

That random part can't however be causing the compile errors.

I told you that the entire renderstate is dumped into the shader cache, even stuff that isn't used for shader decompilation (some of that renderstate data is almost random)(edited).

How deterministic are them? They will be added exactly the same? Last conversation I got the impression that the shader state could play a part on this, since the same shaders being added aren't binary equal.

Whats the point of removing shaders with compile error? They will be added again next time Cemu encounters them in the game.

Request for adding of the ability to remove shaders by hash or offset to enable removing shaders with link or compile errors.

However some of the errors don't have a corresponding key in the cache. I'm parsing the log.txt for lines that match Link error in shader 0086e7ebadb97735 and trying to find that number in the cache table name1.

I'm creating a tool to remove shaders from the shader cache based on compilation errors written to log.txt when loading the cache.