Resident Evil Village:

[Zulhafis]

What happened

Hi bro, I found a freezing issue in Bannerlator Ludashi v3.1.1.

Before the update, I was using Proton 10, and the game would freeze when frame generation was enabled. I then switched to Proton 11.0.3, and the game worked fine with frame generation without any freezing.

However, after updating Bannerlator to v3.1.1, the game started freezing again. When I enable frame generation, I can only play for around 10 minutes before the game freezes.

Could you please check if the latest update changed anything related to Proton, DXVK, or frame generation that might be causing this issue?

Thank you.

System

=== Bannerlator log ===
Captured: 2026-09-14_02-17-12
App: 3.1.1 (85)
Device: vivo iQOO I2220
Android: 16 (SDK 36)
Scope: Bannerlator only (system-wide capture is deliberately not offered)

From the logs

• GPU: Adreno 750
• Driver: Wrapper driver 26.0.99
• DXVK: 3.0.2-gplasync
• VKD3D: 2.9.0

Attached

• vkd3d-proton.log
• re8_dxgi.log
• re8_d3d11.log
• logcat.log
• crash_2026-08-30_02-07-00.txt
• crash_2026-08-30_02-07-14.txt
• crash_2026-08-30_02-05-44.txt
• crash_2026-08-30_02-05-45.txt
• crash_2026-08-30_02-06-58.txt

Scrubbed as they are written: e-mail addresses, auth tokens, and the signed-in Steam account name. File paths are left intact so they stay useful — give them a glance if one of your folder names identifies you. Attach the zip below — it is at Download/bannerlator/reports/Resident Evil Village-2026-09-14_02-17-12.zip.

[github-actions]

🤖 Bannerlator AI

Short answer: no — the 3.1.1 update did not change Proton, DXVK, or VKD3D. Those are components you install yourself from the in-app catalog; the update is app-side only and leaves your containers and installed components untouched. The only Proton change in 3.1.1 is the optional v7 layer rebuild, and that changed only the desktop's look (XP style), not graphics or emulation — and it's opt-in, so your Proton 11.0.3 is unchanged unless you tapped "Update layer".

Frame generation changed in three places in 3.1.1, and none matches a 10-minute freeze: two experimental LSFG Native options (capture resolution and Vulkan 1.1 compat, both off by default), and a fix that makes frame gen start faster (it used to build its shaders twice when you turned it on, freezing the picture for a few seconds at the toggle — not minutes later). With default settings the frame-gen present path is identical to 3.1.0, and there is no timer or watchdog in the frame-gen code that could freeze the game after ~10 minutes.

So the freeze is most likely the driver + frame-gen combination, not the update. Try:

1. Check which engine is selected (Win-FG Native or LSFG Native) and turn off the two new experimental switches if they're on.
2. Play with frame gen off — if the freeze disappears, it's frame gen + driver.
3. Try a Turnip driver instead of Wrapper 26.0.99.
4. In the attached crash logs, look for OUT_OF_DATE (recreating swapchain) or fence wait timed out — that signature shows whether the driver hung under the forced FIFO present mode that frame gen uses.

If you did update the Proton layer to v7, "Revert layer" in the container's ⋮ menu puts v6 back and rules it out.

Checked: docs/releases/3.1.1.md, app/src/main/cpp/winlator/VulkanRendererContext.cpp:1136, app/src/main/java/com/winlator/star/XServerDisplayActivity.java:10188

---

ℹ️ Please read — about this project

Bannerlator is a personal build — made by me (The412Banner), for my own device, my own needs, and my own use.

It's a personal continuation of the Winlator Star Bionic project (star-emu/star) after it was discontinued and archived. None of the original developers are involved except me; it stands on their work plus cherry-picked commits from across the community — all credited in the repo.

This is NOT an official or general-purpose Winlator release. It is built and tuned for my hardware and my workflow, and published as-is purely in case it happens to be useful to someone else.

• No guarantee it works on any other device, GPU, or Android version.
• No support, and no commitment to fix anything that works for me but not for you. If a feature works on my device, it isn't broken — for me, which is what this build is for.
• Bug reports / feature requests for setups I don't run may simply be closed. That's not personal; this just isn't a community-support project.
• You're free to use, modify, fork, or share it (GPL-3.0). If it doesn't work on your setup, that's expected — it wasn't built for it.

Cited from the Bannerlator codebase. For a follow-up, open a new question.