8k screenshot crashes CoI silently (no logs)

Game crashes to desktop without writing to logs when trying to take an 8K screenshot.

No crash with Native, 1080p, 2K, or 4K, only crashes with 8K.

No Mafi/CoI folder in LocalLow/Temp, so no crashlog there.

On Arch Linux using latest Proton-GE

Note that when this happens, nothing new is written to the logs - I checked the logs before and after the crash, and no change. Have tested this a number of times, and it is very easily reproducable.

Did you try --flush-after-each-log and --full-flush-logs?

Does it also happens without mods?

Not yet..

Added the commandline arguments. Renamed mods folder to Mods.bak and started a new game on New Haven with all defaults. F11, pressed C to 8K and P - CoI vanishes silently.
Still nothing in Roaming/Temp (empty folder)

Let me test it on the desktop.

And it doesn't crash on the desktop. (still no usable logs)

I have similar problem on 2K it kills the screenshoting application, on desktop it works normally.

Started to appear after update to 596 which have nothing that touch this.

Mod for Day&Night cycles, that was first suspicion, is disabled and even I did restart computer fully.

Did you try @jemsterr [discord] to use non-fullscreen mode (borderless or window)?
For my problem it is working.

I believe it is windowed.. Will check.

It switched without my consent, but also by misstouch 😄

Yeah, definitely windowed..

Let me try in an X11 session just to see something.

Nope still crashes.

But only on my laptop.

30:[Sat May 30 02:23:07 2026] x86/PAT: UnityGfxDeviceW:3363 freeing invalid memtype [mem 0x00000000-0x00000fff]
31:[Sat May 30 02:23:07 2026] x86/PAT: UnityGfxDeviceW:3363 freeing invalid memtype [mem 0x00000000-0x00000fff]
32:[Sat May 30 02:23:07 2026] x86/PAT: UnityGfxDeviceW:3363 freeing invalid memtype [mem 0x00000000-0x00000fff]

I see you have something else than Windows 😉
I do not know who was it, but there was a player who had some issue with falling, when terrain moved on Linux.
Is possible that there is something, that causes similar issue.

That was me! :)

It seems like it's Nvidia drivers again.

It seems like it's running out of VRAM, even though it's only half used.. Workaround is just to take 4K screenshots and wait until I can get to the desktop to take the 8K one if I really need to.

Updating to NVIDIA driver 610 didn't fix it.