starred/PlayCover

Fork 0

mirror of https://github.com/PlayCover/PlayCover.git synced 2026-04-26 00:05:52 +03:00

[GH-ISSUE #1734] [Bug]: Game 'Wuthering Wave' compile shader every time running the game #1107

New issue

Closed

opened 2026-03-03 19:03:51 +03:00 by kerem · 5 comments

kerem commented

2026-03-03 19:03:51 +03:00

Owner

Originally created by @visitor17 on GitHub (Nov 12, 2024).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1734

Describe the bug

Every time when I start the game, the Unreal engine wil spend some minutes to compile shader. Even if I just compile it a minute ago, it will re-compile again if I quit the game.

Steps to reproduce

runt the App, wait until it finish verifying files integrity, and the engine start compile shader

Expected behaviour

When I run the game on my Android smartphone, it only compile shader when the game install something new, which save much time loading.

Crash log

No response

What version of PlayCover are you using?

3.1.0

What version of macOS are you using?

Ventura (macOS 13)

Issue Language

Yes my issue is written in English

Originally created by @visitor17 on GitHub (Nov 12, 2024). Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1734 ### Describe the bug Every time when I start the game, the Unreal engine wil spend some minutes to compile shader. Even if I just compile it a minute ago, it will re-compile again if I quit the game. ### Steps to reproduce runt the App, wait until it finish verifying files integrity, and the engine start compile shader ### Expected behaviour When I run the game on my Android smartphone, it only compile shader when the game install something new, which save much time loading. ### Crash log _No response_ ### What version of PlayCover are you using? 3.1.0 ### What version of macOS are you using? Ventura (macOS 13) ### Issue Language - [X] Yes my issue is written in English

kerem

2026-03-03 19:03:51 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-03 19:03:52 +03:00

Author

Owner

@Ryu-ga commented on GitHub (Nov 12, 2024):

The issue of EU4-based iOS games not finding the correct path on macOS can be resolved with the nightly versions of PlayCover and PlayChain.
I think shader's write path and read path is different because of the issue.

PlayTools #168.

@Ryu-ga commented on GitHub (Nov 12, 2024): The issue of EU4-based iOS games not finding the correct path on macOS can be resolved with the nightly versions of PlayCover and PlayChain. I think shader's write path and read path is different because of the issue. [PlayTools #168](https://github.com/PlayCover/PlayTools/pull/168).

kerem commented

2026-03-03 19:03:52 +03:00

Author

Owner

@visitor17 commented on GitHub (Nov 12, 2024):

The issue of EU4-based iOS games not finding the correct path on macOS can be resolved with the nightly versions of PlayCover and PlayChain. I think shader's write path and read path is different because of the issue.

PlayTools #168.

nightly ver? I thought that glitch was solved in ver 3.1.0.

So should I refresh both Playcover and Playtool? or only Playtool is enough?

And is using those 'ln -sf' codes in terminal easier, as I don't understand how to compile raw code into new Playcover App?

@visitor17 commented on GitHub (Nov 12, 2024): > The issue of EU4-based iOS games not finding the correct path on macOS can be resolved with the nightly versions of PlayCover and PlayChain. I think shader's write path and read path is different because of the issue. > > [PlayTools #168](https://github.com/PlayCover/PlayTools/pull/168). nightly ver? I thought that glitch was solved in ver 3.1.0. So should I refresh both Playcover and Playtool? or only Playtool is enough? And is using those 'ln -sf' codes in terminal easier, as I don't understand how to compile raw code into new Playcover App?

kerem commented

2026-03-03 19:03:52 +03:00

Author

Owner

@Ryu-ga commented on GitHub (Nov 13, 2024):

nightly ver? I thought that glitch was solved in ver 3.1.0.

So should I refresh both Playcover and Playtool? or only Playtool is enough?

And is using those 'ln -sf' codes in terminal easier, as I don't understand how to compile raw code into new Playcover App?

Just download the latest nightly version from

https://github.com/PlayCover/PlayCover/actions/runs/11804411981

And remove play tools from wuwa and re-inject playtools.

@Ryu-ga commented on GitHub (Nov 13, 2024): > nightly ver? I thought that glitch was solved in ver 3.1.0. > > > > So should I refresh both Playcover and Playtool? or only Playtool is enough? > > > > And is using those 'ln -sf' codes in terminal easier, as I don't understand how to compile raw code into new Playcover App? Just download the latest nightly version from https://github.com/PlayCover/PlayCover/actions/runs/11804411981 And remove play tools from wuwa and re-inject playtools.

kerem commented

2026-03-03 19:03:52 +03:00

Author

Owner

@visitor17 commented on GitHub (Nov 24, 2024):

Still, Version 3.1.0 (928) Playcover make none help.

Game still need recompiling when re-enter.

@visitor17 commented on GitHub (Nov 24, 2024): Still, Version 3.1.0 (928) Playcover make none help. Game still need recompiling when re-enter.

kerem commented

2026-03-03 19:03:53 +03:00

Author

Owner

@Hyp3rSon1X commented on GitHub (Feb 5, 2025):

Honestly, I'm not sure if this even is a problem of Playcover.
I observe this exact same behavior on my iPhone 15 Pro Max as well (compiling shaders every time), so this might be a WuWa problem.

@Hyp3rSon1X commented on GitHub (Feb 5, 2025): Honestly, I'm not sure if this even is a problem of Playcover. I observe this exact same behavior on my iPhone 15 Pro Max as well (compiling shaders every time), so this might be a WuWa problem.