This is a real, developer-acknowledged bug. It was reported on Proton, Windows 10, Windows 11 and macOS; it is not justified to label it exclusively a Linux/Proton issue.
How to recognise the specific bug
The original report described this order of events:
- The player started the Casino tutorial for the first time.
- Case 1 completed normally.
- Case 2 appeared, but the player could no longer interact with the game.
- The image looked dimmed or greyed out, much like a paused screen, and the expected text was missing.
The original poster mentioned Proton 11.0-2, but other players in the same Steam thread independently reported the same symptoms on Windows 10/11 and macOS. The developer’s confirmed solution is a game update, not a Proton-specific launch flag.
Fix: get the developer’s corrected build
Step 1 — Update Dupery
In your Steam Library, open Dupery’s game entry and allow any available update to finish. The developer confirmed the Casino tutorial bug was fixed in v1.0.8. A later build such as v1.0.9 should include that fix unless a new regression has occurred; we have not reproduced the issue on every platform or patch.
Do not assume that merely having started Steam means a pending game download has installed. Check Steam’s download status if an update is waiting.
Step 2 — Restart Steam
If you still see the greyed-out case-2 screen after the update, fully exit the Steam application, then start it again and reopen Dupery. Restarting Steam is a workaround specifically suggested by the developer in the affected thread, rather than an invented troubleshooting ritual.
Step 3 — Verify the installed game files
The developer also recommends Steam file verification if the updated version still seems to show the old problem:
- In the Steam Library, right-click Dupery and open Properties.
- Open Installed Files (the exact label may vary across Steam client versions).
- Choose Verify integrity of game files and let Steam finish.
- Relaunch Dupery and retry the same Casino tutorial transition.
This compares your local installation with the files Steam expects to be installed. It is not a guarantee that an unrelated save-data issue will be repaired.
Still freezing after v1.0.8 or newer?
If the bug still occurs after those steps, treat it as a possible remaining case or regression, not as proof that the developer never fixed the original defect. Keep the report focused on facts another person can reproduce:
- The exact Dupery version/build and platform (Windows 10/11, macOS, Linux/Proton).
- On Linux, the Proton version used (the original report mentioned 11.0-2).
- Whether case 1 finishes normally and case 2 immediately freezes.
- Whether text is missing, the screen is greyed out, or inputs fail.
- Whether the problem persists after restarting Steam and verifying files.
- An image or short recording of the transition, if you can capture it lawfully and safely.
Reply in the original Casino tutorial bug discussion or use the game’s official issue-reporting route. Do not erase saves, delete Proton prefixes, disable operating-system security controls or force experimental launch flags based on this guide: none of those destructive changes was part of the developer’s fix.
Is this the same as the October 19 Casino Codex fix?
No. The separate v1.0.7 patch note says the Poker Face quirk should no longer appear twice in the Casino codex. That is a codex/data display issue, not the tutorial’s case-2 grey-screen freeze. The October 20 v1.0.9 patch note lists other fixes, but the developer’s direct forum reply identifies v1.0.8 as the relevant Casino tutorial fix.
Avoid sending players to the wrong patch because both notes contain the word “Casino.”
FAQ
Why does Dupery stop responding on Casino tutorial case 2?
Players reported an unresponsive, dimmed screen after the first case. The developer confirmed this bug was addressed in v1.0.8. The public reply does not explain its internal code cause.
Is this only a Proton issue?
No. The forum records matching reports from Windows 10, Windows 11 and macOS users as well as the initial Proton user.
What should I do if I already updated?
Follow the developer’s two stated checks: restart Steam and verify game file integrity. If it still happens, report the exact build and steps to reproduce.
Should I delete my save to fix it?
No evidence supports that action for this particular bug. Avoid making irreversible save changes based on an unrelated troubleshooting suggestion.
Does v1.0.9 make this guide obsolete?
No: v1.0.9 may be the more recent patch, but v1.0.8 is the developer-confirmed minimum fix for this exact tutorial issue. The guide stays useful for anyone on an older or incompletely updated installation.
Sources and disclosure
- Steam discussion: “casino tutorial bug” – original case-2 symptoms; 14 player replies spanning Proton, Windows and macOS; direct reply from developer Theorist of Wind confirming the v1.0.8 fix and recommending a Steam restart or file verification. Read October 21, 2026.
- Dupery official Steam community – patch notes and discussion index, including v1.0.7 Casino codex change.
- Dupery v1.0.9 patch notes – later, distinct fixes, October 20, 2026.
- Existing Dupery evidence notebook hub – related game, not a duplicate of this technical issue.
GGClue is an independent, unofficial fan site. We checked the named Steam developer reply and player reports but did not independently test the installed game on all platforms. Last checked October 21, 2026.
Casino tutorial case two: fixed build versus a different freeze
The Dupery developer’s thread confirms a specific Casino tutorial progression freeze after the first case, fixed in v1.0.8. The recognizable state is that the second case starts with a greyed-out screen or no new text and player input stops advancing it. That differs from an unrelated Casino Codex issue the developer discussed separately, and it is not a general instruction to skip the entire tutorial.
Check the installed version first, then load through the normal menu and try entering the second case again on v1.0.8 or a later version. Success: case two actually displays the expected text/choices and accepts an action. A splash screen loading or a developer changelog existing is not enough. If a save remains stuck, record the point at which the second case stops and preserve any surviving progress; the developer did not provide a proven mass-repair for all older frozen slots.