Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The video files might actually be 4K - I haven't dug into the game's asset archives, but at the very least, opening resources.resource in VLC plays back a 9-second, 30FPS, H.264 video file with a resolution of 3840x2160, although I don't know if this particular file is actually used in-game or if all the other videos are held to the same standard.
For some baffling reason, the PC build of the game is built for 32-bit Windows. I have absolutely no idea how this came to be, beyond general ignorance; neither the PS4 or PS5 support 32-bit applications, Microsoft themselves discontinued new 32-bit builds of Windows over two years ago, and anyone with the minimum recommended 8GB of RAM is also running 64-bit Windows (or at least, I strongly hope they are).
At 1440p with Proton Experimental, I only get 2-4 seconds of choppy cutscene playback before the game crashes. with Proton logs showing failed memory allocation. Trying to force large-address awareness (which I had assumed was still the default on Proton) causes the game to fail to launch entirely, as gmem tries and fails to allocate larger chunks of memory at startup. I'm hoping the game is doing a good job freeing up memory during play, or at least handling its existing memory pool well, and that I'm not going to run into the same issues just by playing longer at lower resolutions.
I suspect this boils down to differences in memory allocation and video playback solutions between actual Windows and Proton/Linux; I doubt this issue actually occurs on Windows or it would've been noticed by now. Regardless, 32-bit binaries and operations that require large memory allocations (like UHD video decoding) are really not a good mix.