04-29-2016, 04:45 AM
Pages: 1 2
04-29-2016, 07:19 AM
Yep. We only support automatic builds for that particular version of ubuntu listed.
https://wiki.dolphin-emu.org/index.php?title=Building_Dolphin_on_Linux#15.04_and_15.10
There's also a PPA option, but I don't recommend that because updating Dolphin invalidates your shader cache, Dolphin updates a lot.
https://wiki.dolphin-emu.org/index.php?title=Building_Dolphin_on_Linux#15.04_and_15.10
There's also a PPA option, but I don't recommend that because updating Dolphin invalidates your shader cache, Dolphin updates a lot.
04-30-2016, 08:30 AM
a slightly related question, does updating Dolphin always invalidate the shader cache or only when there's a graphics related change?
04-30-2016, 09:31 AM
Always as far as I know.
04-30-2016, 09:48 AM
Ouch, I didn't know this. Thought it was similar to save states which usually are compatible between versions. Thanks for the advice!
04-30-2016, 12:11 PM
Save states are not compatible between versions as far as I know either.
04-30-2016, 01:52 PM
Err, no. Similar to save states where there's a "state revision" number that gets increased whenever a change into save state system is made, there's a "shader cache" revision too. On Dolphin side, the shader cache should be invalidated when this number is increased (and whenever a change that affects shaders are made, the revision is increased too -- just like with save states). However, there are other factors that can invalidate the cache, such as GPU drivers updates and in some rare cases, even OS updates...
In other words, save states and shader cache can be shared between different versions as long as they're from the same "internal revision".
In other words, save states and shader cache can be shared between different versions as long as they're from the same "internal revision".
04-30-2016, 02:00 PM
I believe those numbers are linked to the build revision.
04-30-2016, 04:02 PM
From a quick lookup, the last time save state code was changed was in PR #3782. Theoretically, any version built after PR #3782 merge should be able to "share" their save states. I already saw something similar for Shader Cache a while ago, but I didn't find the relevant code (too lazy to do a in-depth search ATM)...
04-30-2016, 07:33 PM
(04-30-2016, 01:52 PM)Jhonn Wrote: [ -> ]Err, no. Similar to save states where there's a "state revision" number that gets increased whenever a change into save state system is made, there's a "shader cache" revision too. On Dolphin side, the shader cache should be invalidated when this number is increased (and whenever a change that affects shaders are made, the revision is increased too -- just like with save states). However, there are other factors that can invalidate the cache, such as GPU drivers updates and in some rare cases, even OS updates...
This is true, except the shader cache revision is automatically changed for every revision of Dolphin, so you can never share the shader cache between different versions of Dolphin like you sometimes can with savestates. (I think Ishiiruka does it differently, though.)
Pages: 1 2