Dolphin, the GameCube and Wii emulator - Forums

I have reported this over at Guru3d forums but I thought I would send a heads up in case this isn't fixed by the
time they merge changes into the official driver.

Not seeing any crash here with 397.40. Maybe try deleting your shader cache files? (Documents\Dolphin Emulator\Cache\Shaders\*)

Would that actually do anything if nvidia keeps a global cache?

(05-03-2018, 01:40 PM)Stenzek Wrote: [ -> ]Not seeing any crash here with 397.40. Maybe try deleting your shader cache files? (Documents\Dolphin Emulator\Cache\Shaders\*)

No crash. Just severe rendering bugs in Rouge Squadron 2.

I'll retry with cleared cache but I thought that cache is rebuilt when you change builds anyway?

Not anymore for the most part.

(05-04-2018, 02:44 PM)nbohr1more Wrote: [ -> ]No crash. Just severe rendering bugs in Rouge Squadron 2.

I'll retry with cleared cache but I thought that cache is rebuilt when you change builds anyway?

Clearing shader cache fixed the issue.

397.76 Vulkan beta (newer than OP) confirmed working.

The driver uninstaller should always clean out such caches, but the users themselfs should also learn(about time) that convenience features don't come for free.

Therefore you need to keep cleaning shader cache more often, most obviously when reinstalling drivers or programs.

To make it easier you can use batch scripts on windows like this:

(05-21-2018, 08:37 PM)Renazor Wrote: [ -> ]The driver uninstaller should always clean out such caches, but the users themselfs should also learn(about time) that convenience features don't come for free.

Therefore you need to keep cleaning shader cache more often, most obviously when reinstalling drivers or programs.

To make it easier you can use batch scripts on windows like this:

Code:

@echo off
echo.
echo.
echo ***** AMD DXCache Cleanup *****
echo.
echo.
set folder="C:\Users\USERNAME\AppData\Local\AMD\DxCache"
echo Selected folder is %folder% - press any key if ok
echo.
explorer %folder%
pause
echo.
cd /d %folder%
for /F "delims=" %%i in ('dir /b') do (rmdir "%%i" /s/q || del "%%i" /s/q)
echo.
timeout 5

Code:

@echo off
echo.
echo.
echo ***** AMD GLCache Cleanup *****
echo.
echo.
set folder="C:\Users\USERNAME\AppData\Local\AMD\GLCache"
echo Selected folder is %folder% - press any key if ok
echo.
explorer %folder%
pause
echo.
cd /d %folder%
for /F "delims=" %%i in ('dir /b') do (rmdir "%%i" /s/q || del "%%i" /s/q)
echo.
timeout 5

You really have no idea what you're talking about do you? You make posts that are uninformed basically claiming you reinvented the wheel to be better without understanding why choices have been made in the first place and have made issues on the bugtracker with a "solution" that is absolutely ludicrous. This "solution" is also one of the former and actually has absolutely nothing to do with the issue at hand, which was that DOLPHIN's shadercache was broken somehow. You are now developing "fixes" that are not needed at all, you know what you should do? Put that time into actually making Dolphin better by creating PR's with actual fixes to issues. That is way more useful.

And users do not have to learn anything, if something is unintuitive then it is a problem on the developers side, not the users side.
If something breaks because of updates, it is not the user's fault, it's the developer that made the update his fault.

I just missed that it was dolphin's shader cache in this case, it's just one more folder/script to add to the collection.

Doesn't really affect my point, because I was talking about the standard procedure that should have been done since forever by GPU vendors, how can something as obvious and frequent as this get past their internal testing, yes shader cache glitches don't happen only to dolphin, it's the big industry that's lacking in some areas and it's sort of their responsibility and they should have explained through the developer channels it would also reach wider familiarity and thus into dolphin. I did mean for all such (shader) caches, the dolphins and the drivers. I do this every time, oh, I just happen to not update the driver every week, I do it manually a couple of times a year, zero problems. Unless someone's trying to purposelly beta-test the newest and latest, which is what this thread is not about, it looks like a standard user support question.

So if it was Dolphin's cache fault this time, a simple driver version check could be implemented at boot, if it's different than last boot, cleans out all the shaders.

That's fine that you do that without issue, but please don't go recommending that to other users. It is a very bad idea.