mirror of
https://github.com/PlayCover/PlayCover.git
synced 2026-04-27 08:45:50 +03:00
[GH-ISSUE #1889] [Bug]: Zenless Zone Zero Cutscenes Pixelated #1236
Labels
No labels
UI
app-support
bug
bug
documentation
duplicate
enhancement
game-support
good first issue
help wanted / caution
inactive
invalid
macos-beta
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/PlayCover#1236
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @stefanos-git on GitHub (Jun 6, 2025).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1889
Describe the bug
Whenever i see a cutscene in zzz everything looks very low quality and pixelated. it's been line that for a long time now. my graphics are at max settings, theres not really a setting to adjust cutscene quality, so i set the resolution to 4k in playcover settings. it still looks like a 720p video though. i wonder if anyone knows how to fix this. i asked chat gpt and it asked me to edit config files to increase the resolutions. i dont really know a lot about all this i hope someone can help
Steps to reproduce
Open zenless zone zero and play the main storyline until you see a cutscene, here are the settings i used:
Expected behaviour
low quality cutscenes.
Crash log
What version of PlayCover are you using?
3.1.0
What version of macOS are you using?
Sonoma (macOS 14)
Issue Language
@stefanos-git commented on GitHub (Jun 6, 2025):
e
i wonder if you guys can see it from this image, but its all washed out. everything is pixelated.
@stefanos-git commented on GitHub (Jun 6, 2025):
to give you an idea, this is what the actual game looks like, no pixelated-ness, everything is crispy clear
@stefanos-git commented on GitHub (Jun 9, 2025):
I contacted the devs via their customer support email, so far all they've told me to is to verify file integrity or lower graphics, nothing of actual help. they asked me for a comparison video so i sacrificed my story experience just to show them how pixelated the cutscenes look compared to the cutscenes from older quests which were crispy clear
@entisocial commented on GitHub (Jun 10, 2025):
This is not a bug, we are using the mobile versions of the games, the mobile versions of the games use videos (not gameplay) that are compressed to oblivion, so the videos for cinematics like that are pixelated (this is also the reason why Hoyo uploads such videos in full quality on the YouTube channels).
@stefanos-git commented on GitHub (Jun 26, 2025):
no. that is just blatant misinformation. all the previous cutscenes are insanely crispy and high quality even when viewed through playcover, you can view old cutscenes in the "video archive" section of the game. it's only the new patch's cutscenes that have this problem, hence the reason i posted this bug in the first place. if it was always like that i won't be here reporting it.
@entisocial commented on GitHub (Jun 26, 2025):
You not understanding the information doesn't make it misinformation. If you load up the iOS apps on any iOS device or any iPadOS device, and replay the pre-rendered videos (which you can do by revisiting the quests in the archive section at Random Play) you'll see that the videos are exactly like that. The Playcover team can fix bugs for Playcover, but it cannot fix the content of the ZZZ package delivered by Hoyoverse. Yes the last pre-rendered videos were pixelated but don't complain to Playcover, complain to Hoyoverse.
@stefanos-git commented on GitHub (Jun 27, 2025):
you claiming all pre rendered cutscenes are pixelated when you play the game on playcover is infact misinformation, that doesn't make me wrong or make you right. i've reached out to hoyoverse and provided gameplay footage comparing pre rendered cutscenes from old patches to new ones to show them the issue. after exchanging information back and forth for about 4 days they said they're working on it, but knowing hoyoverse i doubt they'll immediately fix it, they've released a few hot fix updates but none of them really helped me with my issue. i just posted this bug here because other than hoyoverse there's only this place where i can talk about this or find someone whose had this issue before me or find someone who knows of a fix to this.
@entisocial commented on GitHub (Jun 27, 2025):
Ok then best of luck 😂