starred/shadPS4

Fork 0

mirror of https://github.com/shadps4-emu/shadPS4.git synced 2026-04-26 08:15:59 +03:00

[GH-ISSUE #1360] Why is shader compiled every time? #447

New issue

Closed

opened 2026-02-27 21:06:20 +03:00 by kerem · 7 comments

kerem commented

2026-02-27 21:06:20 +03:00

Owner

Originally created by @par274 on GitHub (Oct 12, 2024).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/1360

I don't know how the emulator works, but why does the shader have to be compiled from scratch for each entry?

In all other emulators, the shader is saved to disk after being compiled, and nothing seen in the second entry will cause a freeze.

For example, as I showed in the video, normally you should experience momentary freezes only once, but doesn't compiling shaders every time you enter put more load on RAM than necessary?

https://www.youtube.com/watch?v=u_O1QONN3Lc

Originally created by @par274 on GitHub (Oct 12, 2024). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/1360 I don't know how the emulator works, but why does the shader have to be compiled from scratch for each entry? In all other emulators, the shader is saved to disk after being compiled, and nothing seen in the second entry will cause a freeze. For example, as I showed in the video, normally you should experience momentary freezes only once, but doesn't compiling shaders every time you enter put more load on RAM than necessary? https://www.youtube.com/watch?v=u_O1QONN3Lc

kerem closed this issue

2026-02-27 21:06:20 +03:00

kerem commented

2026-02-27 21:06:21 +03:00

Author

Owner

@birthtothunder commented on GitHub (Oct 13, 2024):

There's no shader cache.

@birthtothunder commented on GitHub (Oct 13, 2024): There's no shader cache.

kerem commented

2026-02-27 21:06:21 +03:00

Author

Owner

@par274 commented on GitHub (Oct 13, 2024):

There's no shader cache.

Yes, I noticed that. I think it's a most important thing.

@par274 commented on GitHub (Oct 13, 2024): > There's no shader cache. Yes, I noticed that. I think it's a most important thing.

kerem commented

2026-02-27 21:06:21 +03:00

Author

Owner

@cuesta4 commented on GitHub (Oct 13, 2024):

Sometimes shader cache will mask problems and make it difficult to see if they've been solved. It's something usually reserved for when emulators are at a more mature state, and the highest priority becomes quality of life features.

Right now it's better to compile the shaders everytime, so we can quickly identify fixes and regressions.

@cuesta4 commented on GitHub (Oct 13, 2024): Sometimes shader cache will mask problems and make it difficult to see if they've been solved. It's something usually reserved for when emulators are at a more mature state, and the highest priority becomes quality of life features. Right now it's better to compile the shaders everytime, so we can quickly identify fixes and regressions.

kerem commented

2026-02-27 21:06:21 +03:00

Author

Owner

@wojek07 commented on GitHub (Oct 13, 2024):

However, will such feature be actually needed at some point in future? If so then, it makes sense to implement this and just disable it by default.

@wojek07 commented on GitHub (Oct 13, 2024): However, will such feature be actually needed at some point in future? If so then, it makes sense to implement this and just disable it by default.

kerem commented

2026-02-27 21:06:21 +03:00

Author

Owner

@par274 commented on GitHub (Oct 13, 2024):

Sometimes shader cache will mask problems and make it difficult to see if they've been solved. It's something usually reserved for when emulators are at a more mature state, and the highest priority becomes quality of life features.

Right now it's better to compile the shaders everytime, so we can quickly identify fixes and regressions.

There are still memory leak problems at the moment, can we say that this is the cause? If so, there may be an option to disable cache, but this feature needs to be there.

However, will such feature be actually needed at some point in future? If so then, it makes sense to implement this and just disable it by default.

Yeah, I'm on the same point as you.

@par274 commented on GitHub (Oct 13, 2024): > Sometimes shader cache will mask problems and make it difficult to see if they've been solved. It's something usually reserved for when emulators are at a more mature state, and the highest priority becomes quality of life features. > > Right now it's better to compile the shaders everytime, so we can quickly identify fixes and regressions. There are still memory leak problems at the moment, can we say that this is the cause? If so, there may be an option to disable cache, but this feature needs to be there. > However, will such feature be actually needed at some point in future? If so then, it makes sense to implement this and just disable it by default. Yeah, I'm on the same point as you.

kerem commented

2026-02-27 21:06:21 +03:00

Author

Owner

@rafael-57 commented on GitHub (Oct 13, 2024):

The emulator is very early in progress, the way shaders are handled changes very frequently with nightly builds. There are other things to do before implementing a shader cache

@rafael-57 commented on GitHub (Oct 13, 2024): The emulator is very early in progress, the way shaders are handled changes very frequently with nightly builds. There are other things to do before implementing a shader cache

kerem commented

2026-02-27 21:06:21 +03:00

Author

Owner

@Beworgen commented on GitHub (Nov 16, 2025):

Can you make the shader compiler a option so that only people that update the games compatibility need to disable it and it will show if it is disabled or not in the log?

@Beworgen commented on GitHub (Nov 16, 2025): Can you make the shader compiler a option so that only people that update the games compatibility need to disable it and it will show if it is disabled or not in the log?

kerem referenced this issue

2026-02-27 21:13:06 +03:00

[PR #447] [MERGED] core,shader_recompiler: align structures for 64-bit platforms #1567